Confirmed users
1,351
edits
Release:Release Automation on Mercurial:Documentation: Difference between revisions
Jump to navigation
Jump to search
Release:Release Automation on Mercurial:Documentation (view source)
Revision as of 18:53, 29 March 2012
, 29 March 2012specify which config files to use for staging
(→Fennec) |
(specify which config files to use for staging) |
||
| Line 774: | Line 774: | ||
== Staging Specific Notes == | == Staging Specific Notes == | ||
Release automation in staging is mostly the same as in production, but does have a few differences you should | Release automation in staging is mostly the same as in production, but does have a few differences you should know about: | ||
* Use the config files with the prefix "<tt>staging_</tt>". These have many values already set correctly for staging. | |||
* All uploading (builds, snippets, symbols) is done to dev-stage01.build.mozilla.org | * All uploading (builds, snippets, symbols) is done to dev-stage01.build.mozilla.org | ||
* It can take a few tries to get repo_setup to run properly. This is because hgweb sometimes returns a 500 (internal server error) when we query about a locale. The best solution is just to start the automation from scratch until it works, to make sure you get a clean run. If this is too frustrating for you, you can manually clone the repositories you care about and start automation from tag (see [[#Restarting_the_automation_from_a_specific_point | Restarting from a specific point]]). | * It can take a few tries to get repo_setup to run properly. This is because hgweb sometimes returns a 500 (internal server error) when we query about a locale. The best solution is just to start the automation from scratch until it works, to make sure you get a clean run. If this is too frustrating for you, you can manually clone the repositories you care about and start automation from tag (see [[#Restarting_the_automation_from_a_specific_point | Restarting from a specific point]]). | ||