Confirmed users
1,351
edits
ReleaseEngineering/DisposableProjectRepositories: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/DisposableProjectRepositories (view source)
Revision as of 23:35, 21 February 2014
, 21 February 2014only a "reconfig" is needed on scheduler, not a "restart"
(only a "reconfig" is needed on scheduler, not a "restart") |
|||
| Line 27: | Line 27: | ||
* '''NOTE''': Your repository will have no hooks enabled after a reset. You'll need to specify in the request if you need any configured. | * '''NOTE''': Your repository will have no hooks enabled after a reset. You'll need to specify in the request if you need any configured. | ||
* Sit back and watch your builds and test results roll in (eg [http://tbpl.mozilla.org/?tree=Alder Alder], [http://tbpl.mozilla.org/?tree=Birch Birch], [http://tbpl.mozilla.org/?tree=Cedar Cedar],[http://tbpl.mozilla.org/?tree=Holly Holly], [http://tbpl.mozilla.org/?tree=Larch Larch], [http://tbpl.mozilla.org/?tree=Maple Maple]). | * Sit back and watch your builds and test results roll in (eg [http://tbpl.mozilla.org/?tree=Alder Alder], [http://tbpl.mozilla.org/?tree=Birch Birch], [http://tbpl.mozilla.org/?tree=Cedar Cedar],[http://tbpl.mozilla.org/?tree=Holly Holly], [http://tbpl.mozilla.org/?tree=Larch Larch], [http://tbpl.mozilla.org/?tree=Maple Maple]). | ||
* '''Special note:''' the first push to your newly cloned repo may not trigger builds if the repo had been pushed to previously, which is {{bug|774862}}. If it does not, please re-open the bug and move it to mozilla.org :: Release Engineering with a comment 'Please | * '''Special note:''' the first push to your newly cloned repo may not trigger builds if the repo had been pushed to previously, which is {{bug|774862}}. If it does not, please re-open the bug and move it to mozilla.org :: Release Engineering with a comment 'Please reconfigure the build scheduler'. | ||
* It will take 3 build runs for the leak checking tools to establish themselves. Before the third run expect to see the builds marked as burning. Other than the leak check the builds should compile and test fine. | * It will take 3 build runs for the leak checking tools to establish themselves. Before the third run expect to see the builds marked as burning. Other than the leak check the builds should compile and test fine. | ||