On Thu, Mar 14, 2013 at 3:30 PM, Martin Ba <0xcdcdc...@gmx.at> wrote:
> I'd say this is not intended:
>
> I have a node that has "Leave this machine for tied jobs only" set.
>
> It started to run a Job that certainly did not explicitly set this node.
> However, this Job had "Restrict where this project can be run" set to:
>
> !master
>
> So, yes, this expression includes this node, but it certainly is unexpected!
>
> Should this be fixed? I'm running Jenkins 1.420
Why wouldn't you expect a job to run on a node that matches the label
where you told it to run? That sounds exactly like expect behavior -
and that is exactly how you get those 'tied jobs'.
--
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.
