Bugzilla – Full Text Bug Listing
| Summary: | multiple slaves listed instead of just build2 and master | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Community | Reporter: | Kim Moir <kim.moir> | ||||
| Component: | CI-Jenkins | Assignee: | CI Admin Inbox <ci.admin-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | d_a_carver | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | 315643 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
(In reply to comment #0) > Created an attachment (id=168737) [details] > screen shot > > When looking at hudson, it appears there are many other slaves listed other > than build2 and master. Just wondering why? I'll attach a screen shot. These are the labels that have been created for the various build nodes. Master has a bunch of labels that somebody created, as well as the Slave node itself. If Slaves are grouped together with the same labels, then if you want your builds to run on a particular configuration, but did not care which machine it actually ran on, you can Tie your build to one of the available configurations. We probably need to make the number of labels a bit smaller and more specific to help provide meaning. You can also tie your build by the Node name of the build machine as well. Yes, I thought they must have been labels. I agree, it would make sense to limit the number of labels to reduce confusion. I think we're good here. If not, then I don't know what to do. |
Created attachment 168737 [details] screen shot When looking at hudson, it appears there are many other slaves listed other than build2 and master. Just wondering why? I'll attach a screen shot.