On Thu, Mar 14, 2013 at 4:39 PM, Martin Ba <[email protected]> wrote:
>
> But "tying" a job to a certain node doesn't really sound like what happened.
>
> We have:
> * Node B says: "Leave this machine for tied jobs"
> * Job X says: I don't care where I'm run, just not on master (`!master`)
> * Job Y says: Only run this job on Nodes A and B (`A && B` for example)
>
> I think it's a little bit surprising that both X and Y will run on Node B,
> don't you think?
A pattern match is a pattern match. Both patterns match. Not surprising.
> The PROBLEM here is also that this restricts inserting "test-nodes" into a
> Jenkins instance that only run a very limited set of jobs.
No, the problem is specifying a patten match that includes them.
> As soon as any other job has a blanket (!master) set, it'll get run on these
> test nodes too.
So don't give that to jobs if you don't mean it.
> I guess one workaround could be (haven't tried yet) to add a dummy label to
> all nodes so that restrictions could be phrased as `dummmy && !master`)
You can give multiple labels. Why not just add one you can target
directly on the nodes where you want the jobs to go?
--
Les Mikesell
[email protected]
--
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.
