Skip to content

V
V8
Switch branch/tag
  1. 23 May, 2015 1 commit
  3. 18 May, 2015 1 commit
  5. 04 May, 2015 1 commit
  7. 27 Apr, 2015 1 commit
  9. 16 Apr, 2015 1 commit
  11. 15 Apr, 2015 1 commit
  13. 09 Apr, 2015 1 commit
  15. 07 Apr, 2015 2 commits
  17. 01 Apr, 2015 1 commit
  19. 14 Mar, 2015 2 commits
  21. 06 Mar, 2015 1 commit
    • machenbach's avatar
      Make automated branch creation gnumbd-save. · 934dd88d
      machenbach authored 
      This makes now the same simplification as the chromium
release scripts do. For creating branch B from a gnumbd'ed
(aka real) commit X do:
1. Branch Y off the real X
2. Set refs/pending/heads/B to Y
3. Set refs/pending-tags/B to X
4. Set refs/heads/B to X

The old algorithm tried to branch off the pending
correspondent of X. That commit was determined by comparing
tree objects of the real X and commits on pending.
Unfortunately, multiple commits on one branch can refer to
the same tree object, e.g., for commits P, Q, R with R being
the revert of Q, P and R refer to the same tree object.

TBR=tandrii@chromium.org
NOTRY=true
TEST=./script_test.py
TEST=tools/release/create_release.py -a me -r you --dry-run

Review URL: https://codereview.chromium.org/979243004

Cr-Commit-Position: refs/heads/master@{#27042}
      934dd88d
  23. 05 Mar, 2015 2 commits
    • machenbach's avatar
      Fix progress check in auto-roller. · f96e2260
      machenbach authored 
      Using a git range check for checking progress is wrong when
the last rolled revision and the revision candidate are on
different branches. The range A..B will always show the
commits from the merge-base of A and B until B.

Better compare the tags of the last rolled revision and the
candidate. The candidate's version must be strictly greater
than what's in chromium.

TBR=tandrii@chromium.org
NOTRY=true
TEST=./script_test.py

Review URL: https://codereview.chromium.org/979133002

Cr-Commit-Position: refs/heads/master@{#27021}
      f96e2260
    • machenbach's avatar
      Make auto-roller roll recent release based on timestamp. · a6a0bd88
      machenbach authored 
      Before this change, out of two versions 4.2.13.1 and
4.2.14, the latter would have been considered the newest.
Now, the timestamp of the commit determines the age, which
allows to roll a patched version first. The auto-roller
will only roll forward (i.e. there needs to be a commit
range between the last roll and the new candidate).

Additionally, this CL does some cleanups:
- Use the sheriff detection mechanism in the auto-roller.
- Require the roll revision parameter in the chromium_roll
script to avoid redundancy. The auto_roll script determines
that revision automatically.
- Simplify the revision summary in the commit message. The
summary will now show last_roll..new_roll, which e.g.
includes the version change CL. It'll now show useful
information for cherry-picks, which it didn't before.
- Remove unused clusterfuzz check. That check is part of the
release process script.

TBR=tandrii@chromium.org
NOTRY=true
TEST=./script_test.py
TEST=./tools/release/chromium_roll.py --dry-run --sheriff -c ~/tmp/chromium/src --last-roll 55b9049ea3978a589d8db2aa191d21222eef737f fc263505535a175c8efa18f4c787bd92a1d1ab3d --use-commit-queue -r me -a you

Review URL: https://codereview.chromium.org/977903002

Cr-Commit-Position: refs/heads/master@{#27009}
      a6a0bd88
  25. 27 Feb, 2015 1 commit
    • machenbach's avatar
      Make the auto-pusher recover easier. · 002b1ddb
      machenbach authored 
      The auto-push script is only used in an automated fashion
on bots. It doesn't need to check for a clean git
environment as it has a special workdir checkout.

If the release creation fails for whatever reason (e.g.
a master restart happens in the middle), the workdir
checkout might be left dirty. Any new attempt of the auto
pusher then bails out.

After this change it will call the create_release script
in any case which tidies up the workspace on startup.

TBR=tandrii@chromium.org
NOTRY=true
TEST=./script_test.py

Review URL: https://codereview.chromium.org/960773007

Cr-Commit-Position: refs/heads/master@{#26928}
      002b1ddb
  27. 26 Feb, 2015 1 commit
  29. 24 Feb, 2015 1 commit
  31. 20 Feb, 2015 1 commit
  33. 17 Feb, 2015 1 commit
  35. 16 Feb, 2015 4 commits
  37. 12 Feb, 2015 1 commit
    • machenbach's avatar
      Create v8 roll branches in refs/heads. · 44bc8646
      machenbach authored 
      This is needed as normal chromium checkouts don't fetch
branch-heads.

These branches will also be replicated by GitHub and are
fetched when cloning from the repository.

The expected object size will be the same or smaller than
before as we currently push the same information onto the
candidates branch (which already is in refs/heads). The only
difference is the increasing number of refs in refs/heads.

BUG=chromium:451975
TBR=tandrii@chromium.org
NOTRY=true
LOG=n

TEST=./script_test.py
TEST=tools/release/create_release.py -r machenbach@chromium.org -a machenbach@chromium.org --dry-run

Review URL: https://codereview.chromium.org/914973002

Cr-Commit-Position: refs/heads/master@{#26629}
      44bc8646
  39. 30 Jan, 2015 1 commit
  41. 29 Jan, 2015 1 commit
  43. 28 Jan, 2015 1 commit
  45. 27 Jan, 2015 1 commit
  47. 26 Jan, 2015 1 commit