Before I start, I just want to acknowledge that this is an odd ball question and may or may not be applicable to this group.
I am in the process of converting to Jenkins from Hudson, so I currently have two master nodes, one for each version. I also have 26 slaves. Right now they are in use by the Hudson master. These are my production environment and are in use, pretty much every day. I would like to test the Jenkins master against the slave nodes but there can only be one and only one job running on a slave node at any time. My production environment will remain Hudson until I can be assured that Jenkins is up and running correctly. So here's the odd-ball question: is there a way to have the Jenkins master (or Hudson master) respect the one-and-only-one job per slave constraint? For concreteness, here's a test scenario: 1) Hudson master kicks off a job on slave tm22 2) Jenkins master wants to kick off a job on slave tm22 but holds off until the current (Hudson) job on tm22 completes. 3) Jenkins detects the job is complete and triggers a job on tm22 4) and Hudson master does the same thing: it waits till the current job on tm22 finishes and then triggers it's own job. Thanks for your patience and help, John -- 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.
