1. 27 Mar, 2019 1 commit
  2. 07 Mar, 2019 1 commit
  3. 19 Feb, 2019 1 commit
  4. 29 Jan, 2019 1 commit
  5. 28 Jan, 2019 1 commit
  6. 21 Nov, 2018 1 commit
  7. 17 Oct, 2018 1 commit
  8. 16 Oct, 2018 1 commit
  9. 10 Oct, 2018 1 commit
  10. 17 May, 2018 2 commits
    • Michael Achenbach's avatar
      Reland "[release] Switch auto-roller to gclient setdep" · 90e61da1
      Michael Achenbach authored
      This reverts commit d169622f.
      
      Reason for revert: setdep bug should be fixed
      
      Original change's description:
      > Revert "[release] Switch auto-roller to gclient setdep"
      > 
      > This reverts commit a9f5dd30.
      > 
      > Reason for revert:
      > Temporarily use legacy method until https://crbug.com/843917 is fixed.
      > 
      > Original change's description:
      > > [release] Switch auto-roller to gclient setdep
      > > 
      > > NOTRY=true
      > > 
      > > Bug: chromium:828745
      > > Change-Id: I051f57893937796e01f0b823f1050dd36e0fbfd9
      > > Reviewed-on: https://chromium-review.googlesource.com/997556
      > > Reviewed-by: Sergiy Byelozyorov <sergiyb@chromium.org>
      > > Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      > > Cr-Commit-Position: refs/heads/master@{#52385}
      > 
      > TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org
      > 
      > NOTRY=true
      > 
      > Bug: chromium:843917
      > Change-Id: I69978ba55ffa5996101e1d31bdf10364b7ef273f
      > Reviewed-on: https://chromium-review.googlesource.com/1064130
      > Reviewed-by: Michael Achenbach <machenbach@chromium.org>
      > Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#53230}
      
      TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org
      
      Change-Id: Ia70dc1df7e25e0c8ffd3fafeb97830b5d5f87336
      No-Presubmit: true
      No-Tree-Checks: true
      No-Try: true
      Bug: chromium:843917
      Reviewed-on: https://chromium-review.googlesource.com/1064413Reviewed-by: 's avatarMichael Achenbach <machenbach@chromium.org>
      Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#53238}
      90e61da1
    • Michael Achenbach's avatar
      Revert "[release] Switch auto-roller to gclient setdep" · d169622f
      Michael Achenbach authored
      This reverts commit a9f5dd30.
      
      Reason for revert:
      Temporarily use legacy method until https://crbug.com/843917 is fixed.
      
      Original change's description:
      > [release] Switch auto-roller to gclient setdep
      > 
      > NOTRY=true
      > 
      > Bug: chromium:828745
      > Change-Id: I051f57893937796e01f0b823f1050dd36e0fbfd9
      > Reviewed-on: https://chromium-review.googlesource.com/997556
      > Reviewed-by: Sergiy Byelozyorov <sergiyb@chromium.org>
      > Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#52385}
      
      TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org
      
      NOTRY=true
      
      Bug: chromium:843917
      Change-Id: I69978ba55ffa5996101e1d31bdf10364b7ef273f
      Reviewed-on: https://chromium-review.googlesource.com/1064130Reviewed-by: 's avatarMichael Achenbach <machenbach@chromium.org>
      Commit-Queue: Michael Achenbach <machenbach@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#53230}
      d169622f
  11. 12 Apr, 2018 1 commit
  12. 05 Apr, 2018 1 commit
  13. 21 Mar, 2018 1 commit
  14. 20 Mar, 2018 1 commit
  15. 14 Mar, 2018 1 commit
  16. 07 Nov, 2017 1 commit
  17. 06 Mar, 2017 1 commit
  18. 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
  19. 16 Nov, 2016 1 commit
  20. 03 Nov, 2016 1 commit
  21. 27 Jul, 2016 1 commit
  22. 26 Jul, 2016 2 commits
  23. 30 Jun, 2016 1 commit
  24. 29 Jun, 2016 1 commit
  25. 29 Apr, 2016 1 commit
  26. 29 Mar, 2016 1 commit
  27. 02 Feb, 2016 1 commit
  28. 04 Jan, 2016 1 commit
  29. 30 Nov, 2015 1 commit
  30. 24 Nov, 2015 2 commits
  31. 23 Nov, 2015 1 commit
  32. 20 Nov, 2015 1 commit
  33. 19 Jun, 2015 2 commits
  34. 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
  35. 20 Feb, 2015 1 commit