Zeller

Joined 28 June 2013
No edit summary
Line 1: Line 1:
== Ship It ==
== Ship It ==
=== Bug 826753 ===
=== Bug 826753 - release automation should update ship it at certain points ===
==== Notes ====
* pulse.m.o gives buildbot events
* pulse.m.o gives buildbot events
** Look for build.release-*.finished (Found in ['_meta']['routing_key'])
** Look for build.release-*.finished (Found in ['_meta']['routing_key']?)
** Use FF candidate buildlogs to help determine the names of the builder I am interested in (ie the first part before "bmNN" is the name of the builder)
** Use [http://ftp.mozilla.org/pub/mozilla.org/firefox/candidates/31.0b3-candidates/build1/logs/ FF candidate buildlogs] to help determine the names of the builder I am interested in (ie the first part before "bmNN" is the name of the builder)
*** http://ftp.mozilla.org/pub/mozilla.org/firefox/candidates/31.0b3-candidates/build1/logs/
==== Questions ====
** Message format for Buildbot is found on pulse
==== To Do ====
* /status - Lists all available releases, that have status data, in JSON format and can be queried with parameters (ie /status?var1=1&var2=10). Analogous to /releases
* /status.html – Pretty GUI view of the info shown in /status. Analogous to /releases.html
* /status/
** GET: Lists release status info in JSON. Analogous to /releases/
** POST: covered in Bug 1032985
* /status/.html – Pretty GUI view of the info shown in /status/ GET, possibly including a visual timeline of the 6 steps: Tagging completed, All builds/repacks completed, Updates on betatest, Ready for releasetest, Ready for release and Postrelease. (status steps taken from Bug 826753 comment 0)
 
=== Bug 1032985 - Add REST API entry point to shipit that allows shipit-agent to enter release data into shipit database ===
==== Notes ====
==== Questions ====
==== To Do ====
* Add REST API entry point for updating update.db at /status/<release-name> when POST
* Add REST API entry point for updating update.db at /status/<release-name> when POST
* New entry points for shipit
 
** /status - Lists all available releases, that have status data, in JSON format and can be queried with parameters (ie /status?var1=1&var2=10). Analogous to /releases
=== Bug 1032978 - Add a standalone process that listens to pulse for release related buildbot messages ===
** /status.html – Pretty GUI view of the info shown in /status. Analogous to /releases.html
==== Notes ====
** /status/
==== Questions ====
*** GET: Lists release status info in JSON. Analogous to /releases/
==== To Do ====
*** POST: covered in Bug 1032985
** /status/.html – Pretty GUI view of the info shown in /status/ GET, possibly including a visual timeline of the 6 steps: Tagging completed, All builds/repacks completed, Updates on betatest, Ready for releasetest, Ready for release and Postrelease. (status steps taken from Bug 826753 comment 0)
* Long-running standalone script (shipit-agent.py) that listens to pulse and uses / status/<release-name> with POST to update update.db for <release-name> status
* Long-running standalone script (shipit-agent.py) that listens to pulse and uses / status/<release-name> with POST to update update.db for <release-name> status
=== Bug 1032975 - Add new table(s) to shipit database ===
==== Notes ====
==== Questions ====
==== To Do ====
* New status table in update.db
* New status table in update.db
Confirmed users
194

edits