Created attachment 533774 [details] [diff] [review] staging_cofig.py - allow all slaves It is not the first time that I have needed to move a slaves from production into staging because the staging were wedged or even try to use the slave#10 from preproduction. The problem I would face is that it would take me some time to notice that the slave was not being able to take jobs.
I thought we were getting rid of staging? And that development systems would use the same *_config.py as preproduction (which includes all slaves)?
Comment on attachment 533774 [details] [diff] [review] staging_cofig.py - allow all slaves Patch is fine, but I think Dustin is right in comment 1.
Should we remove the staging files so we don't use them?
As much as I would love to get to this there's much assigned to me at the moment. Putting it into the future.
Do we still want to do away with staging? Does that mean we'd be relying on preproduction to test release changes?
This was for the sake of being able to move a slave to preproduction and test that is good to be put back in production. What I do instead is to put them in my own testing master and then be happy about it when it takes jobs appropriately.