Push Shepherd Responsibilities

Setup Notifications

Before starting as push shepherd, you will need to make sure you are on the list for notifications:

• Email Brian R. to be added on email notifications for robots and makes.
• Email Ann to be added as a watcher on Code Review Parent ticket.

Week 1 (Preview Build 1)

• Create CGI Build Ticket (CGI chatter) in Redmine:
  • set status as "Preview 1".
  • set Target version.
  • create subtask: "To Do" CGI Testing Responsibilities, rotate the guest CGI.

Week 2 (Preview Build 2)

• Change CGI Build Ticket status to "Preview 2".
• Make sure all build related issues are tested on dev before build happens on beta.

Week 3 (Final Build)

• Change CGI Build Ticket status to "Final Build".
• Review Error Logs for the Robots:

1. hgNear - sends an email with results
2. hgTables - sends an email with results
3. LiftOverTest - check by hand: /cluster/bin/build/scripts/logs/LiftOverTest-v$VERSION_NUMBER.log

• If there are any errors reported then go to the following location and check the logs: /cluster/bin/build/scripts/logs/

Week of Push

• Make sure of the following:
  • All related issues (Bugs, Features) have status of "CGI-ready" or "CGI-ready-open-issues"
  • All patch requests have been fulfilled
  • All Code Reviews are closed
  • Everyone has reported their testing (if any) on hgwbeta in the CGI Build ticket
• If necessary, send out a status update (or reminder) email 1-2 days before release day.
• The day before the push, send an email notice to browser-staff letting them know that tomorrow is a push day. Something along these lines:

   Just a heads up that tomorrow is a CGI push day. If you have big code changes included in
   this release please be available in case something goes wrong with the push of your changes.
   QA typically starts the push around 1:30pm.

Day of Push

Push to hgw0 only

• Send out push request
• Monitor Apache Error Log: hgw0:/usr/local/apache/logs/error_log:
  • use shift + g to go to bottom of page
  • use shift + f to follow incoming errors
    • If there are any unusual errors, use whois $ip_address or host $ip_address to see where errors are coming from, or vi error_log to determine if error occurred before pushing to hgw0.
• Wait to hear from QA on how their CGIs look on hgw0 (QA should update "CGI testing responsibilities" ticket).

Push to hgwN only

• SSH to hgwN machine before sending out push request.
• Send out push request.
• Monitor error log for a short while to make sure no new errors occur under the load.

Push to rest of the RR, hgwbeta-public, and euronode

• Send out push request.
• Send email to build-meister to let him/her know the CGIs are on the RR (send wrap-up email to Brian R.).

Day after Push

• Make sure all related issues have been closed out.
• Close patch tickets.
• Change CGI Build Ticket status to "Closed".