Confirmed users
39
edits
CIDuty/How To/QuarantineMultipleInstances: Difference between revisions
CIDuty/How To/QuarantineMultipleInstances (view source)
Revision as of 04:38, 1 June 2018
, 1 June 2018small typo
(Aligned the text) |
m (small typo) |
||
| Line 10: | Line 10: | ||
# In our case we needed to un-quarantine t-yosemite-r7-070 and t-yosemite-r7-{075..156} so the command looked like this : | # In our case we needed to un-quarantine t-yosemite-r7-070 and t-yosemite-r7-{075..156} so the command looked like this : | ||
# for i in t-yosemite-r7-070 t-yosemite-r7-{075..156}; do echo $i; quarantine_tc.py --enable -p releng-hardware -w gecko-t-osx-1010 -g mdc2 ${i}; done | # for i in t-yosemite-r7-070 t-yosemite-r7-{075..156}; do echo $i; quarantine_tc.py --enable -p releng-hardware -w gecko-t-osx-1010 -g mdc2 ${i}; done | ||
# What happens? We go through worker 070 and every worker from 075 till 156 and for each of them we run the python file we saved locally. With the proper arguments. | # What happens? We go through worker 070 and every worker from 075 till 156 and for each of them we run the script from the python file we saved locally. With the proper arguments. | ||