Doubts about Publish Over SSH Plugin

[Erick Macedo]

Hi,

Publish plugin installed SSH in jenkins to perform deploy the artifacts generated by the maven on a linux server with wildfly.

In SSH Server Name added the server and test the connection is ok.

The problem is in session with field Transfers Source files, these files are as to which path? the .m2 maven?

Well I have two jobs, one to generate the war to include the war in .m2 and to deploy, the latter which can utilize the plugin to deploy.

Jobs is automated so that when the build job is finished the deploy job begins.

Someone uses this plugin to help me?

thank you

[Richard Bywater]

The path of files to transfer is relative to the workspace. Usually you'd transfer over an artifact either created by the job or brought in via something like the Copy Artifacts plugin.

Richard

--
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 jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/f7e304b6-7a71-4493-9ac6-2016842ae1f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Erick Macedo]

First thanks for the help Richard

As I have two jobs one to build and another to deploy,

I should use the plugin "Copy Artifacts plugin" to get the war of

workspace "build" and transfer to the workspace "deploy"?

graciously

Erick Macedo

[Richard Bywater]

Hi Erick

There's probably many other ways as well, but what you describe is how we currently do a lot of our deploys so it'd be worth giving it a try and seeing if it fits in with your processes.

Cheers
Richard

--

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 jenkinsci-use...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c3698de8-543e-40b1-9c25-d7c60876e9b6%40googlegroups.com.

[Erick Macedo]

Hi,

I configured this way and it worked,

Another question, as you usually split between the build environment (Stage, test, production)?

Create a build for each environment? or a single build and different parameters?

Em sexta-feira, 24 de abril de 2015 17:55:21 UTC-3, Erick Macedo escreveu:

[Maciej Jaros]

Erick Macedo (2015-04-27 22:54):

Hi,

I configured this way and it worked,

Another question, as you usually split between the build environment (Stage, test, production)?

Create a build for each environment? or a single build and different parameters?

You should have separte builds for several reasons:

1. Copy artifact plugin copies latest build from given job.
2. For alfa/test builds you might want to do full unit and integration tests and Jenkins will show you charts with failing tests and such. For production builds you can assume those tests already pass and make build proccess faster (or run different tests depeneding on your needs).
   
3. Stage and production builds might use code from different tags/branches... And Jenkins will show changes nicely if you let it pull changes from single branch in a single job.

In other words the build process will most likely be different and it will be much easier to observe it in separate jobs.

Regards,
Nux.