ReleaseEngineering/How To/Reset the Try Server

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.

• 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.
• RelEng to post downtime notices to dev.planning, and mark the TryServer closed.
  • Note this does *not* touch any production build/test/talos machines, so does *not* require closing mozilla-central, or any other tree.
• File IT bug to
  • delete the try server hg repo
    • rm -rf /repo/hg/mozilla/try
  • create a fresh new hg repo cloned from mozilla-central.
    • su - hg
    • cd /repo/hg/mozilla
    • hg clone mozilla-central try
  • create an empty pushlog db.
    • su - hg
    • touch /repo/hg/mozilla/try/.hg/pushlog2.db
    • chown hg:hg_mozilla /repo/hg/mozilla/try/.hg/pushlog2.db
    • chmod g+w /repo/hg/mozilla/try/.hg/pushlog2.db
  • Reset perms on the repo.
    • Become the root user on the machine.
    • cd /repo/hg/mozilla/try/.hg/store
    • chown hg:hg_mozilla *
  • typically this is done by aravind
• 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
• RelEng to remove message from tinderbox server.