On Thu, Sep 26, 2013 at 12:01 PM, Tânia Magalhães
<taniamagalh...@gmail.com> wrote:
> Yes, of course there is a logic behind my needs...
> I just think that it is useless explain the all process here.
By 'logic' I meant some external program driving/controlling the
choice of the build node at any particular time. If there is such a
program that knows when and where to do the build (or you can write
one, based on your logic), you should be able to use the NodeLabel
Parameter plugin so that you can parameterize the node to build on,
and then pass that parameter when you request a build through the rest
API.
> What I need is what I described above.
> Any ideas?
> So far I was not able to do it...
Another option would be to also use the 'build flow' plugin and have a
controlling job invoke the real job with the node parameter based on
something it can determine with its somewhat restricted groovy syntax.
Or use a similar controlling job with a system groovy build step to
do the same thing but with unrestricted access to all of jenkin's
objects. The examples on the groovy plugin page shows how to
retrieve system properties and trigger another build.
> To remind, I am running jenkins on windows.
Groovy is very portable - the OS shouldn't matter.
--
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.
