On Sunday, December 11, 2016 at 1:05:19 PM UTC-8, Rachel Moreno wrote: > > Hi David, > > I don't know if I've understood what you really need, but please, take a > look at: > > - https://wiki.jenkins-ci.org/display/JENKINS/SCP+plugin > - https://wiki.jenkins-ci.org/display/JENKINS/Publish+Over+SSH+Plugin > > For example, if you have a user/password you can choose "Use password > authentication" to configure access to remote location and then sending > files. >
Yes, I've seen those two plugins, but I don't understand how I would use either of these from a pipeline job. On Friday, December 9, 2016 at 11:57:00 PM UTC+1, David Karr wrote: > > This mostly isn't a Jenkins question, but I would think many people here > would have to deal with this kind of situation. > > I have a Jenkins pipeline job that produces a javadoc jar (among other > products). I'm going to need to deploy that content into a directory tree > on a remote box (using some variation of "scp", I assume), where the > directory is owned by a particular non-root user, and this directory is a > mapped volume to a Docker container running an apache instance. > > I do have a "mechanical id" (you might call it a service account) that I > use for automation tasks in bitbucket and jenkins. It presently isn't able > to log into my javadoc box, but I have root rights on the box, so I could > modify that. > > I imagine I'll need to create an ssh key to use for this. Does that make > sense here? > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/140cfb7a-bbaf-4172-84b2-c98ae4dace58%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
