- 08 Nov, 2016 1 commit
-
-
Aaron Gable authored
This is still important, but at least now it won't result in a stacktrace. Change-Id: If6e7e15a98b0a03df7e978201762fea670312ede Reviewed-on: https://chromium-review.googlesource.com/408660Reviewed-by:
Andrii Shyshkalov <tandrii@chromium.org> Commit-Queue: Aaron Gable <agable@chromium.org>
-
- 04 Nov, 2016 2 commits
-
-
nodir authored
Master names were confused with bucket names R=tandrii@chromium.org, qyearsley@chromium.org BUG=661580 Review-Url: https://codereview.chromium.org/2482523002
-
tandrii authored
R=borenet@chromium.org,qyearsley@chromium.org BUG=599931 Review-Url: https://codereview.chromium.org/2468263005
-
- 01 Nov, 2016 1 commit
-
-
agable authored
BUG=661187 Review-Url: https://codereview.chromium.org/2466953003
-
- 31 Oct, 2016 1 commit
-
-
qyearsley authored
Note: This CL originally just removed a deprecated use of Remove use of DoGetTrySlaves, suggested in http://crrev.com/2442153002, then was expanded to remove DoGetTrySlaves, GetPreferredTrySlaves and GetTrySlavesExecuter since these are all deprecated and unused. BUG=660453 Review-Url: https://codereview.chromium.org/2453823002
-
- 28 Oct, 2016 1 commit
-
-
qyearsley authored
Assuming that assuming bots are always just builder names, and they're never specified along with tests in git cl --bot options, then some logic used for git cl try can be removed. Review-Url: https://codereview.chromium.org/2448193006
-
- 26 Oct, 2016 2 commits
-
-
qyearsley authored
It might be good to make this change after the refactoring CL http://crrev.com/2442153002. BUG=640740 Review-Url: https://codereview.chromium.org/2439293002
-
qyearsley authored
When triggering the build, there's a field called "reason", which is currently populated by default with the user's branch name. I have a feeling that this is optional and could be completely omitted. Andrii notes that if users want to send a "reason" string, they could send invoke git cl try with the argument -p reason="<reason>". PSA on infra-dev: https://groups.google.com/a/chromium.org/d/msg/infra-announce/PXkM1WinTYY/w2IvN5B4AwAJ BUG=659552 Review-Url: https://codereview.chromium.org/2428383010
-
- 24 Oct, 2016 3 commits
-
-
qyearsley authored
The purpose of this change is to prepare for modifying git cl try so that builders on multiple masters can be triggered in one invocation (http://crbug.com/640740). This should not affect behavior; this CL makes several non-essential changes to formatting and comments. Review-Url: https://codereview.chromium.org/2442153002
-
nodir authored
It was broken in https://chromiumcodereview.appspot.com/2419113002 R=borenet@chromium.org BUG=658317 Review-Url: https://codereview.chromium.org/2442393002
-
skobes authored
BUG=557512 Review-Url: https://codereview.chromium.org/2445543002
-
- 23 Oct, 2016 2 commits
-
-
qyearsley authored
This is a very little fix. Review-Url: https://codereview.chromium.org/2441213002
-
bradnelson authored
Detect CC=<users> lines the way we detect R= and TBR=. Add these as CC'ed users for rietveld and gerrit. R=iannucci@chromium.org,hinoka@chromium.org,dnj@chromium.org Review-Url: https://codereview.chromium.org/2433323004
-
- 19 Oct, 2016 2 commits
-
-
borenet authored
BUG= Review-Url: https://chromiumcodereview.appspot.com/2419113002
-
tandrii authored
R=machenbach@chromium.org Review-Url: https://chromiumcodereview.appspot.com/2433813004
-
- 18 Oct, 2016 2 commits
-
-
Dan Jacques authored
This reverts commit a8fb3a28.
-
Dan Jacques authored
BUG=chromium:657064 TEST=local - Ran "git cl status" during outage with override, works. R=tandrii@chromium.org Review URL: https://chromiumcodereview-hr.appspot.com/2425673005 .
-
- 17 Oct, 2016 1 commit
-
-
tandrii authored
BUG=656555 R=emso@chromium.org,andybons@chromium.org Review-Url: https://codereview.chromium.org/2421253002
-
- 14 Oct, 2016 1 commit
-
-
rmistry authored
BUG=chromium:656042 Review-Url: https://codereview.chromium.org/2419123002
-
- 12 Oct, 2016 1 commit
-
-
tandrii authored
This also adds first test to cover case of custom properties. R=machenbach@chromium.org,sergiyb@chromium.org BUG=599931 Review-Url: https://codereview.chromium.org/2409223002
-
- 11 Oct, 2016 3 commits
-
-
tandrii authored
R=nodir@chromium.org,sergiyb@chromium.org BUG=599931 Review-Url: https://codereview.chromium.org/2400713003
-
tandrii authored
R=nodir@chromium.org,sergiyb@chromium.org BUG=599931 Review-Url: https://codereview.chromium.org/2401943002
-
tandrii authored
The flow looks like this: $ git cl status Branches associated with reviews: gerrit-4483 : https://chromium-review.googlesource.com/381231 (waiting) $ git cl try-results Warning: Codereview server has newer patchsets (2) than most recent upload from local checkout (None). Did a previous upload fail? By default, git cl try uses latest patchset from codereview, continuing using such patchset 2. Warning: Some results might be missing because You are not logged in. Please login first by running: depot-tools-auth login chromium-review.googlesource.com Started: Infra Linux Precise 32 Tester https://luci-milo.appspot.com/swarming/... Infra Linux Trusty 64 Tester https://luci-milo.appspot.com/swarming/... Total: 2 try jobs $ depot-tools-auth login chromium-review.googlesource.com <<<auth in my browser>>> Logged in to chromium-review.googlesource.com as <some@email.com> To login with a different email run: depot-tools-auth login chromium-review.googlesource.com To logout and purge the authentication token run: depot-tools-auth logout chromium-review.googlesource.com $ git config branch.gerrit-4483.gerritpatchset 2 $ git cl try-results Started: Infra Linux Precise 32 Tester https://luci-milo.appspot.com/swarming/... Infra Linux Trusty 64 Tester https://luci-milo.appspot.com/swarming/... Infra Mac Tester https://luci-milo.appspot.com/swarming/... Total: 3 try jobs R=sergiyb@chromium.org,emso@chromium.org BUG=599931 TEST=new unittests + end-to-end local. Review-Url: https://codereview.chromium.org/2392463009
-
- 10 Oct, 2016 2 commits
-
-
tandrii authored
No stacktrace is printed, instead just a user-friendly string is shown. Add test + some tests refactoring. This CL also improve missing Gerrit issue exception elsewhere by raising user-friendly exception. BUG=654360 R=sergiyb@chromium.org TEST=manual Review-Url: https://codereview.chromium.org/2403793002
-
tandrii authored
R=nodir@chromium.org BUG= Review-Url: https://codereview.chromium.org/2399993004
-
- 07 Oct, 2016 1 commit
-
-
tandrii authored
R=phajdan.jr@chromium.org,sergiyb@chromium.org BUG=599931 Review-Url: https://codereview.chromium.org/2400793004
-
- 06 Oct, 2016 2 commits
-
-
tandrii authored
R=emso@chromium.org,phajdan.jr@chromium.org BUG=599931 TEST=new teste + local end-to-end Review-Url: https://codereview.chromium.org/2395113002
-
tandrii authored
R=emso@chromium.org BUG= Review-Url: https://codereview.chromium.org/2393253002
-
- 29 Sep, 2016 2 commits
-
-
tandrii authored
Originally landed as issue 2378703002 at patchset 60001 (http://crrev.com/2378703002#ps60001). BUG=chromium:649660 TBR=rmistry@chromium.org Review-Url: https://codereview.chromium.org/2376323002
-
tandrii authored
Revert of Add CC_LIST and --cc to Gerrit issues via API to be similar to CCs in Rietveld (patchset #4 id:60001 of https://codereview.chromium.org/2378703002/ ) Reason for revert: Actually, it doesn't break uploads, add cc-ed emails post-upload fails with exception and confuses users, and I couldn't find workaround. Original issue's description: > Add CC_LIST and --cc to Gerrit issues via API to be similar to CCs in Rietveld > > BUG=chromium:649660 > > Committed: https://chromium.googlesource.com/chromium/tools/depot_tools/+/3574740929abd37c45db1d2f8a2c3799bdfe77c5 TBR=rmistry@google.com # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=chromium:649660 Review-Url: https://codereview.chromium.org/2375393002
-
- 28 Sep, 2016 1 commit
-
-
rmistry authored
BUG=chromium:649660 Review-Url: https://codereview.chromium.org/2378703002
-
- 23 Sep, 2016 1 commit
-
-
stip authored
BUG=Every time I run 'git cl upstream' I get "The --set-upstream flag is deprecated and will be removed. Consider using --track or --set-upstream-to." Review-Url: https://codereview.chromium.org/2352393003
-
- 22 Sep, 2016 1 commit
-
-
agable authored
We no longer support git-svn as a workflow. R=iannucci@chromium.org BUG=475320 Review-Url: https://codereview.chromium.org/2360143002
-
- 19 Sep, 2016 1 commit
-
-
rmistry authored
BUG=chromium:628237 Review-Url: https://codereview.chromium.org/2343363003
-
- 14 Sep, 2016 4 commits
-
-
tandrii authored
R=iannucci@chromium.org BUG=642493 Review-Url: https://codereview.chromium.org/2322783002
-
tandrii authored
R=agable@chromium.org BUG=642759,609225 Review-Url: https://codereview.chromium.org/2317253003
-
tandrii authored
R=machenbach@chromium.org BUG= Review-Url: https://codereview.chromium.org/2339903002
-
tandrii authored
This will be used in repositories that use Cr-Commit-Position footers to generate them at the time of git cl land instead of gnumbd. R=iannucci@chromium.org BUG=642493 Review-Url: https://codereview.chromium.org/2324583002
-
- 09 Sep, 2016 1 commit
-
-
agable authored
R=andybons@chromium.org, tandrii@chromium.org Review-Url: https://codereview.chromium.org/2324283002
-
- 08 Sep, 2016 1 commit
-
-
dsansome authored
BUG=641838 Review-Url: https://codereview.chromium.org/2318903002
-