|
|
Created:
4 years, 9 months ago by Sébastien Marchand Modified:
4 years, 9 months ago CC:
chromium-reviews, dpranke+depot_tools_chromium.org, iannucci+depot_tools_chromium.org Base URL:
https://chromium.googlesource.com/chromium/tools/depot_tools.git@master Target Ref:
refs/heads/master Project:
depot_tools Visibility:
Public. |
DescriptionAdd a Syzygy fetch config.
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=299057
Patch Set 1 #Patch Set 2 : Rename the DEPS file. #Messages
Total messages: 17 (4 generated)
sebmarchand@chromium.org changed reviewers: + maruel@chromium.org
PTAL.
On 2016/03/02 17:07:21, Sébastien Marchand wrote: > PTAL. wouldn't that make the CI depend on github?
On 2016/03/02 17:29:28, M-A Ruel wrote: > On 2016/03/02 17:07:21, Sébastien Marchand wrote: > > PTAL. > > wouldn't that make the CI depend on github? The CI doesn't use fetch . You want to use github here, because that's the repo that you actually commit to. There's a precedent in the fetch_config for mojo, for example. I'm a bit surprised that you're using DEPS.syzygy, rather than just DEPS, though?
I don't know :) , the dartium config is already depending on GitHub (https://code.google.com/p/chromium/codesearch#chromium/tools/depot_tools/fetc...), not saying that this is a good thing, but I'm not sure if it's a bad one too. (also, why would the CI use this config ?) We have a chromium.googlesource clone of this project: https://chromium.googlesource.com/external/github.com/google/syzygy/ but I don't know if it can be used for development (i.e. it's a clone of the Syzygy repo, I don't know if you can commit in it).
Yeah, we're using DEPS.syzygy for historical reasons (this repo was also containing the Sawbuck project). We could switch back to DEPS but it'll break the setup of most of the developers (not a big deal, but not sure that it's worth it?)
On 2016/03/02 17:39:06, Sébastien Marchand wrote: > Yeah, we're using DEPS.syzygy for historical reasons (this repo was also > containing the Sawbuck project). We could switch back to DEPS but it'll break > the setup of most of the developers (not a big deal, but not sure that it's > worth it?) Why would that break the setup of most developers? Can't you just rename the file?
On 2016/03/02 18:21:08, Dirk Pranke wrote: > On 2016/03/02 17:39:06, Sébastien Marchand wrote: > > Yeah, we're using DEPS.syzygy for historical reasons (this repo was also > > containing the Sawbuck project). We could switch back to DEPS but it'll break > > the setup of most of the developers (not a big deal, but not sure that it's > > worth it?) > > Why would that break the setup of most developers? Can't you just rename the > file? i.e., I think gclient will default back to looking for 'DEPS' if it doesn't find 'DEPS.syzygy', but I could be wrong ...
Ha ok, I didn't knew that. I'll move my DEPS file then.
On 2016/03/02 18:27:54, Sébastien Marchand wrote: > Ha ok, I didn't knew that. I'll move my DEPS file then. I could well be wrong, we should probably check first to see :).
Looks like you're right ! I've renamed our DEPS file, updated our builders etc... PTAnL.
dpranke@chromium.org changed reviewers: + dpranke@chromium.org
lgtm
The CQ bit was checked by sebmarchand@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1749213002/20001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1749213002/20001
Message was sent while issue was closed.
Description was changed from ========== Add a Syzygy fetch config. ========== to ========== Add a Syzygy fetch config. Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=299057 ==========
Message was sent while issue was closed.
Committed patchset #2 (id:20001) as http://src.chromium.org/viewvc/chrome?view=rev&revision=299057 |