Ruslan Zasukhin (2013-10-01 19:14):
On 10/1/13 2:30 PM, "Maciej Jaros" <[email protected]> wrote:
You didn't mention any dependcies between compliations so why do you want
them sequentially? The procces will be faster if they are paralel.
I did.
1) I have few times underline need of sequential ORDER of that scripts.
Note below: " which should go one by one:"
Note below comment to package_mac
=================================
Before we have start try Jenkins, we have automate builds of allow products
into the next 7 scripts, which should go one by one:
1) compile_mac
2) compile_win
3) compile_lin
4) package_mac -- must be first, because it builds
special REALbasic plugin
using DLLs from 3OS
RESULT file will go to Win and Linux
5) package_win
6) package_lin
7) put_on_ftp_all_archives
===================================
If you really want to you can run wget on jenkins installations that are on
different machines and wait for results. Or if you want to have a single job
just send files to be compiled over SSH and then get resulting files over SSH.
It's just like running local shell, but running SSH on Windows might be
difficult.
Yes, SSH way is clear.
Guys, please understand me correctly.
I DO NOT ASK how to solve task. I see variants.
I try discuss why Jenkins -- so mature, many years in development, 85Mb
installer only SOFTWARE, do not allow me such simple case?
But it does allow you to that. It just allows you to use many solutions
to do that. Jenkins is a very universal tool.
Another one would be to use Parameterized Trigger Plugin
<https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin>
and e.g. make "complie_*" separate jobs. Then with help of Copy Artifact
Plugin
<https://wiki.jenkins-ci.org/display/JENKINS/Copy+Artifact+Plugin>
aggregate the results of those builds and package them. Npte that
Parameterized Trigger Plugin
<https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin>
runs thing sequentially. For example we have a build that downloads
translations from a test server in the process of deploying new version
to the test server. The download of translations is done with tools
aggregated from previous build of the deployment job (to match the
version that is deployed). So the main job is not successful until the
sub-job is successful and main job waits for the sub-job to finish. You
can also run the sub-job separately when needed.
Also note that you can use views to group jobs and set a default view
with most used jobs.
So I would say it is magic ;-), but you need some plugins to achieve that.
Regards,
Nux.
--
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].
For more options, visit https://groups.google.com/groups/opt_out.
