On Fri, Mar 29, 2013 at 4:18 AM, Martin Ba <0xcdcdc...@gmx.at> wrote:
> Is there anything to allow for executors (instead of whole nodes) to be
> labeled?
>
> I know there's the workaround to just have the same machine run a second
> node, but that really does feel awkward.
>
> I'd want to use labeled executors to include Jobs from other Jobs with
> [Trigger/call builds on other projects: Block until the triggered projects
> finish their builds] where currently the blocking, not-doing-anything-job is
> eating a full executor while it's waiting for the other job to finish.
>
> Even better would be to allow the blocking downstream job to run on the same
> executor as the waiting job.
If you want that kind of control, I'd probably use virtual machines to
use the host's capacity instead of multiple executors - so jenkins
would just see different nodes. I haven't tried it but a slightly
less drastic approach would be to start 2 (or more) slave instances on
the same host with different user ids/locations. That should be
possible with at least some of the start-up methods and again jenkins
would see different nodes and thus work with all the directives and
plugins that control access and concurrency.
--
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.
