Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(175)

Issue 1002383002: Make release scripts more robust. (Closed)

Created:
5 years, 9 months ago by Michael Achenbach
Modified:
5 years, 9 months ago
Reviewers:
tandrii(chromium)
CC:
v8-dev, Michael Hablich
Base URL:
https://chromium.googlesource.com/v8/v8.git@master
Target Ref:
refs/pending/heads/master
Project:
v8
Visibility:
Public.

Description

Make release scripts more robust. Remembering the current branch is a relic from the past where no work-dir checkout was used. Now this doesn't give much benefit and screws up the script if it was left in a bad state (e.g. after a master restart). TBR=tandrii@chromium.org NOTRY=true Committed: https://crrev.com/db7e074d92d53d3e43364ca8766f4927aa6e16c9 Cr-Commit-Position: refs/heads/master@{#27196}

Patch Set 1 #

Total comments: 4
Unified diffs Side-by-side diffs Delta from patch set Stats (+13 lines, -20 lines) Patch
M tools/release/common_includes.py View 2 chunks +4 lines, -8 lines 4 comments Download
M tools/release/test_scripts.py View 9 chunks +9 lines, -12 lines 0 comments Download

Messages

Total messages: 9 (2 generated)
Michael Achenbach
PTAL
5 years, 9 months ago (2015-03-14 01:20:20 UTC) #2
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1002383002/1
5 years, 9 months ago (2015-03-14 01:20:38 UTC) #4
commit-bot: I haz the power
Committed patchset #1 (id:1)
5 years, 9 months ago (2015-03-14 01:20:49 UTC) #5
commit-bot: I haz the power
Patchset 1 (id:??) landed as https://crrev.com/db7e074d92d53d3e43364ca8766f4927aa6e16c9 Cr-Commit-Position: refs/heads/master@{#27196}
5 years, 9 months ago (2015-03-14 01:21:03 UTC) #6
tandrii(chromium)
lgtm % one inconsistency, I think. https://codereview.chromium.org/1002383002/diff/1/tools/release/common_includes.py File tools/release/common_includes.py (right): https://codereview.chromium.org/1002383002/diff/1/tools/release/common_includes.py#newcode549 tools/release/common_includes.py:549: self.DeleteBranch(self._config["BRANCHNAME"]) this seems ...
5 years, 9 months ago (2015-03-15 10:50:18 UTC) #7
Michael Achenbach
https://codereview.chromium.org/1002383002/diff/1/tools/release/common_includes.py File tools/release/common_includes.py (right): https://codereview.chromium.org/1002383002/diff/1/tools/release/common_includes.py#newcode553 tools/release/common_includes.py:553: self.GitDeleteBranch(self._config["BRANCHNAME"]) On 2015/03/15 10:50:18, tandrii(chromium) wrote: > seems inconsistent ...
5 years, 9 months ago (2015-03-18 22:33:45 UTC) #8
tandrii(chromium)
5 years, 9 months ago (2015-03-25 23:12:01 UTC) #9
Message was sent while issue was closed.
https://codereview.chromium.org/1002383002/diff/1/tools/release/common_includ...
File tools/release/common_includes.py (right):

https://codereview.chromium.org/1002383002/diff/1/tools/release/common_includ...
tools/release/common_includes.py:553:
self.GitDeleteBranch(self._config["BRANCHNAME"])
On 2015/03/18 22:33:45, Michael Achenbach (travelling) wrote:
> On 2015/03/15 10:50:18, tandrii(chromium) wrote:
> > seems inconsistent from above.
> 
> I don't follow. PrepareBranch is always called in the beginning of the
scripts,
> CommonCleanup in the end. In all cases the workbranch
self._config["BRANCHNAME"]
> is deleted if it exists.

I meant that I didn't quite understand why you call different function
DeleteBranch vs GitDeleteBranch .

Powered by Google App Engine
This is Rietveld 408576698