658374 - Allow moving rev3 machines from production to staging/preproduction if it is needed

Status: RESOLVED WONTFIX

(Infrastructure & Operations Graveyard :: CIDuty, task)

Description

[Armen [:armenzg]]

Attachment: 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.

Comment 1

[Dustin J. Mitchell [:dustin] (he/him)]

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 2

[Chris Cooper [:coop] (he/him)]

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.

Comment 3

[Armen [:armenzg]]

Should we remove the staging files so we don't use them?

Comment 4

[Armen [:armenzg]]

As much as I would love to get to this there's much assigned to me at the moment.
Putting it into the future.

Comment 5

[Chris Cooper [:coop] (he/him)]

Do we still want to do away with staging? Does that mean we'd be relying on preproduction to test release changes?

Comment 6

[Armen [:armenzg]]

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.