On Tue, Oct 1, 2013 at 12:14 PM, Ruslan Zasukhin
<ruslan_zasuk...@valentina-db.com> wrote:
>
> 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?
Add the groovy and build flow plugins. Build flow provides a simple
language that should be able to orchestrate exactly the steps you want
with the ability to do some in parallel and react to failures. If
that language turns out to be too limited, use a system groovy build
step in a master job to do the same things (running other jobs) but
with full access to jenkins internals.
> I believe that TEAM of Jenkins, knows about such cases.
> But on some reason do not implement this.
> This is what I try understand. Why ?
You weren't very clear about why this would not work with the mac
build as the initial job, kicking off a matrix for the rest. Or maybe
even just a matrix with the touchstone build on the mac but I'm not
sure you can access those build results with copy-artifact, etc. until
the whole job completes. In any case I think you have to explain why
having separate jobs to control what you want done on separate
machines is a problem before anyone could answer your philosophical
question. There's not really a limit to the number of jobs you can
configure and if you create them as a copy of an existing job it is
not much harder than making another build step.
--
Les Mikesell
lesmikes...@gmail.com
--
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-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
