canmove, Confirmed users
1,394
edits
ReleaseEngineering/Applications/Slavealloc: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/Applications/Slavealloc (view source)
Revision as of 21:25, 25 March 2011
, 25 March 2011→Staging
No edit summary |
|||
| Line 68: | Line 68: | ||
'''NOTE:''' ''all'' slaves are configured use the production allocator. Allocations from the staging allocator will need to be simulated by hand (<tt>runslave.py</tt> has an command-line option to set the allocator URL). This is done to allow us, as a group, to move slaves between staging and production using a single slave allocator. | '''NOTE:''' ''all'' slaves are configured use the production allocator. Allocations from the staging allocator will need to be simulated by hand (<tt>runslave.py</tt> has an command-line option to set the allocator URL). This is done to allow us, as a group, to move slaves between staging and production using a single slave allocator. | ||
The [http://hg.mozilla.org/build/tools/file/tip/lib/python/slavealloc/contrib/prod-db-to-staging.sh prod-db-to-staging.sh] script will copy the production db to staging for use when staging new changes. | |||
== Development == | == Development == | ||