ReleaseEngineering/How To/Reset the Try Server: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
m (Bug 1082602)
 
(20 intermediate revisions by 10 users not shown)
Line 1: Line 1:
Due to increased usage on tryserver, this is something we need to do approx once a month. This can typically be done in 30-60minutes.
{{Release Engineering How To|Reset the Try Server}}


* make sure joduinn has extracted all the logs he needs for blogposts. Its nice, but not required, to do this repo reset at the end of the calendar month, as it makes blogpost work easier.
The Try server [http://hg.mozilla.org/try repo] needs to be reset periodically (measured in weeks and months). This is due to Mercurial slowing down over time with the usage pattern that Try places on it.
* RelEng to post downtime notices to dev.planning, and mark the [http://tinderbox.mozilla.org/showbuilds.cgi?tree=MozillaTry TryServer closed].
 
** Note this does *not* touch any production build/test/talos machines, so does *not* require closing mozilla-central, or any other tree.
Mozilla IT have scripted the Try repo reset.  The location of the script is TBD (:fubar is finding a place for it).
* File IT bug to
 
** delete [http://hg.mozilla.org/try the try server hg repo]
Historically, Try was reset once developers grew frustrated at the slowdown of making pushes to the try repository on hg.mozilla.org.  The reset would need to be approved at the CAB (change advistory board) meeting and communicated to developers (dev-gaia dev-gaia@lists.mozilla.org, dev-b2g@lists.mozilla.org, dev-planning@lists.mozilla.org, dev-platform@lists.mozilla.org, dev-tree-management@lists.mozilla.org) at least the day before the reset (unless critical).
** create a fresh new hg repo cloned from [http://hg.mozilla.org/mozilla-central/ mozilla-central].
 
** typically this is done by aravind
Try reset machanics:
* RelEng to pull in tip of releases/mozilla-1.9.2 and releases/mozilla-1.9.1 to help make life easier for developers after reopening
 
* RelEng to reconfig [http://sm-try-master.mozilla.org:8010/waterfall http://sm-try-master.mozilla.org:8010/waterfall]
* RelEng closes Try (mention bug#)
* RelEng to remove message from tinderbox server.
* IT runs Try reset script
* RelEng reconfig's the buildbot schedulers (to reset the hg poller state)
* RelEng reopens Try
 
Going forward (after January 23, 2014), Try will be reset at each pre-planned tree closing window (TCW).

Latest revision as of 17:28, 21 December 2014


The Try server repo needs to be reset periodically (measured in weeks and months). This is due to Mercurial slowing down over time with the usage pattern that Try places on it.

Mozilla IT have scripted the Try repo reset. The location of the script is TBD (:fubar is finding a place for it).

Historically, Try was reset once developers grew frustrated at the slowdown of making pushes to the try repository on hg.mozilla.org. The reset would need to be approved at the CAB (change advistory board) meeting and communicated to developers (dev-gaia dev-gaia@lists.mozilla.org, dev-b2g@lists.mozilla.org, dev-planning@lists.mozilla.org, dev-platform@lists.mozilla.org, dev-tree-management@lists.mozilla.org) at least the day before the reset (unless critical).

Try reset machanics:

  • RelEng closes Try (mention bug#)
  • IT runs Try reset script
  • RelEng reconfig's the buildbot schedulers (to reset the hg poller state)
  • RelEng reopens Try

Going forward (after January 23, 2014), Try will be reset at each pre-planned tree closing window (TCW).

Retrieved from "https://wiki.allizom.org/index.php?title=ReleaseEngineering/How_To/Reset_the_Try_Server&oldid=1043353"