New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 667436 link

Starred by 2 users

Issue metadata

Status: Archived
Owner:
Last visit > 30 days ago
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Automate prod branch update process.

Project Member Reported by pprabhu@chromium.org, Nov 21 2016

Issue description

Currently, the push to prod instructions require deputy to manually update the prod branch reference. 
https://sites.google.com/a/google.com/chromeos/for-team-members/infrastructure/chromeos-admin/push-to-prod

Instead,
- test_push should update a remote-ref 'prod-next' whenever test_push succeeds (shuqianz@ Please reference CLs that have already landed for this).
- deploy_servers.py should reset 'prod' to 'prod-next' before starting the push.
 
FR: 
There are instructions for rollback of prod also: https://sites.google.com/a/google.com/chromeos/for-team-members/infrastructure/chromeos-admin/push-to-prod#TOC-Rolling-Back-a-Prod-Push

... but they're known to not work.

Is it possible / worthwhile to also:
- have deploy_servers.py reset a 'prod-last' to 'prod' before moving 'prod'. This way, we leave a ref of the rollback target if we want to do that.
- Add a flag '--rollback' to deploy_servers.py to update prod back to prod-last instead of going forward to 'prod-next'.

wdyt?
Issue 657887 has been merged into this issue.
Cc: akes...@chromium.org
+akeshet: Do you think investing in rollback is worthwhile here? Most pushes should theoretically be safe to rollback (db updates are exceptions).
I think investing in rollback is a lower priority than other work.

Comment 5 by autumn@chromium.org, Nov 29 2016

Labels: -current-issue
Status: Fixed (was: Started)
The automation part has been fixed. If there is a feature request for the rollback, feel free to open a separate one for this.

Comment 7 by dchan@google.com, Mar 4 2017

Labels: VerifyIn-58

Comment 8 by dchan@google.com, Apr 17 2017

Labels: VerifyIn-59

Comment 9 by dchan@google.com, May 30 2017

Labels: VerifyIn-60
Labels: VerifyIn-61

Comment 11 by dchan@chromium.org, Oct 14 2017

Status: Archived (was: Fixed)

Sign in to add a comment