- 15 Dec, 2016 1 commit
-
-
machenbach authored
This splits branch ref creation and landing. The ref now directly uses heads (without pending) and for landing we use depot_tools. For simplicity, the check for existing tags is removed, as it now is very unlikely to happen again without gnumbd. BUG=chromium:674448 NOTRY=true TBR=tandrii@chromium.org Review-Url: https://codereview.chromium.org/2584523002 Cr-Commit-Position: refs/heads/master@{#41716}
-
- 13 Apr, 2016 3 commits
-
-
machenbach authored
TBR=hablich@chromium.org NOTRY=true Review URL: https://codereview.chromium.org/1885863003 Cr-Commit-Position: refs/heads/master@{#35442}
-
machenbach authored
Fix after https://codereview.chromium.org/1887583002/ TBR=hablich@chromium.org NOTRY=true Review URL: https://codereview.chromium.org/1881163003 Cr-Commit-Position: refs/heads/master@{#35441}
-
machenbach authored
Check if a previous run left an inconsistent state behind. The check is right before trying to push a new state as then all information is available, like commit message and tag name. This is still only a band-aid. If gnumbd is down for a longer period, an unprocessed commit won't be found, but the push attempt will still fail. Review URL: https://codereview.chromium.org/1887583002 Cr-Commit-Position: refs/heads/master@{#35437}
-
- 04 Feb, 2016 1 commit
-
-
hablich authored
With the combination of the WATCHLISTS feature and create_release.py it is possible to notify the mailing list v8-merges@googlegroups.com on pending merges. On master this notification is deactivated. R=machenbach@chromium.org NOTRY=true Review URL: https://codereview.chromium.org/1663003003 Cr-Commit-Position: refs/heads/master@{#33719}
-
- 06 Mar, 2015 1 commit
-
-
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}
-
- 12 Feb, 2015 1 commit
-
-
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}
-
- 30 Jan, 2015 1 commit
-
-
machenbach authored
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/881683004 Cr-Commit-Position: refs/heads/master@{#26364}
-