1. 07 Nov, 2017 1 commit
  2. 06 Mar, 2017 1 commit
  3. 18 Nov, 2016 1 commit
    • qyearsley's avatar
      Reland of Update usage of linux blink try bot to use linux_trusty_blink_rel.... · 4a70104a
      qyearsley authored
      Reland of Update usage of linux blink try bot to use linux_trusty_blink_rel. (patchset #1 id:1 of https://codereview.chromium.org/2507853002/ )
      
      Reason for revert:
      linux_trusty_blink_rel is now working, with more capacity
      
      Original issue's description:
      > Revert of Update usage of linux blink try bot to use linux_trusty_blink_rel. (patchset #1 id:1 of https://codereview.chromium.org/2475563002/ )
      >
      > Reason for revert:
      > Submitting this before more capacity was added to linux_trusty_blink_rel caused that builder to get too busy (http://crbug.com/665246); should be able to reland after http://crbug.com/665917 is fixed.
      >
      > Original issue's description:
      > > Update usage of linux blink try bot to use linux_trusty_blink_rel.
      > >
      > > Reason: We're planning to drop support for Linux Precise for layout tests.
      > >
      > > BUG=chromium:660580
      > > NOTRY=true
      >
      > TBR=machenbach@chromium.org
      > # Not skipping CQ checks because original CL landed more than 1 days ago.
      > BUG=chromium:660580
      > NOTRY=true
      
      TBR=machenbach@chromium.org
      # Skipping CQ checks because original CL landed less than 1 days ago.
      NOPRESUBMIT=true
      NOTREECHECKS=true
      NOTRY=true
      BUG=chromium:660580
      
      Review-Url: https://codereview.chromium.org/2505403002
      Cr-Commit-Position: refs/heads/master@{#41090}
      4a70104a
  4. 16 Nov, 2016 1 commit
  5. 03 Nov, 2016 1 commit
  6. 27 Jul, 2016 1 commit
  7. 26 Jul, 2016 2 commits
  8. 30 Jun, 2016 1 commit
  9. 29 Jun, 2016 1 commit
  10. 29 Apr, 2016 1 commit
  11. 29 Mar, 2016 1 commit
  12. 02 Feb, 2016 1 commit
  13. 04 Jan, 2016 1 commit
  14. 30 Nov, 2015 1 commit
  15. 24 Nov, 2015 2 commits
  16. 23 Nov, 2015 1 commit
  17. 20 Nov, 2015 1 commit
  18. 19 Jun, 2015 2 commits
  19. 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
  20. 20 Feb, 2015 1 commit
  21. 16 Feb, 2015 1 commit
  22. 28 Jan, 2015 1 commit
  23. 26 Jan, 2015 2 commits
    • machenbach's avatar
      External name changes of release scripts. · ae22d7f8
      machenbach authored
      Moved and renamed the scripts to fit with git.
      
      These changes require documentation updates, updates of
      the release spreadsheet and the buildbot side.
      
      BUG=chromium:451975
      TBR=tandrii@chromium.org
      NOTRY=true
      LOG=n
      
      Review URL: https://codereview.chromium.org/868473004
      
      Cr-Commit-Position: refs/heads/master@{#26271}
      ae22d7f8
    • machenbach's avatar
      Clean up release scripts. · 379dcd5b
      machenbach authored
      This makes some internal renaming, e.g. trunk -> candidates,
      bleeding edge -> master, without changing the api.
      
      Also remove some unused bailout steps from the push script.
      
      Remove unused bump version script.
      
      BUG=chromium:451975
      TBR=tandrii@chromium.org
      NOTRY=true
      LOG=n
      
      Review URL: https://codereview.chromium.org/873213002
      
      Cr-Commit-Position: refs/heads/master@{#26269}
      379dcd5b
  24. 03 Nov, 2014 2 commits
  25. 25 Sep, 2014 1 commit
  26. 23 Sep, 2014 1 commit
  27. 04 Sep, 2014 2 commits
  28. 03 Sep, 2014 2 commits
  29. 25 Jun, 2014 2 commits
  30. 08 Apr, 2014 1 commit
  31. 04 Apr, 2014 1 commit