New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 754168 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature

Blocked on:
issue 771567

Blocking:
issue 753739



Sign in to add a comment

Make prebuilt luci-go in Chromium deps'able

Project Member Reported by machenb...@chromium.org, Aug 10 2017

Issue description

Currently luci-go-binary hashes are stored under the tools/luci-go subfolder.

Other projects like V8 have their own copy of those files. Currently it is not auto-rolled and can cause breakages when binaries in V8 get too old.

Suggestion 1: Make Chromium's tools/luci-go a subtreed repo, so that V8 can directly add it to its DEPS file.

Suggestion 2: Move luci-go folder under buildtools. The buildtools folder is already a subtreed repo and deps'ed into V8. Not sure if it's really a meaningful location. E.g. gn binary hashes are there, too, bot those are really needed for building, while luci-go is maybe a different matter.
 

Comment 1 by mar...@chromium.org, Aug 10 2017

Cc: tansell@chromium.org mcgreevy@chromium.org
Components: Infra>Platform>Swarming
I'm fine with this. cc'ing people who will do the next rolls.
Which of the suggestions is preferable? Is there another alternative?
Suggestion 2 isn't quite correct. Buildtools is not a subtreed, it's a separate repo. Like that a drawback of suggestion 2 is that rolling luci-go would require a two stage roll. First a CL inside buildtools, then a separate buildtools roll. This might not be convenient.
Blockedon: 771567
Project Member

Comment 5 by bugdroid1@chromium.org, Oct 9 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/d137552822699e748d38d7a86e97ba6e2bce093e

commit d137552822699e748d38d7a86e97ba6e2bce093e
Author: Michael Achenbach <machenbach@chromium.org>
Date: Mon Oct 09 18:52:13 2017

Build: Properly nest gitignore for luci-go

The directory tools/luci-go is now under a subtreed repo mirror and
should have its own gitignore file.

Bug:  chromium:754168 
Change-Id: I716b6c853f04c9284287e417500a821c01dab8c4
Reviewed-on: https://chromium-review.googlesource.com/707146
Reviewed-by: Sergiy Byelozyorov <sergiyb@chromium.org>
Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
Commit-Queue: Michael Achenbach <machenbach@chromium.org>
Cr-Commit-Position: refs/heads/master@{#507430}
[modify] https://crrev.com/d137552822699e748d38d7a86e97ba6e2bce093e/.gitignore
[add] https://crrev.com/d137552822699e748d38d7a86e97ba6e2bce093e/tools/luci-go/.gitignore

Cc: kjellander@chromium.org ehmaldonado@chromium.org
This is a subtree repo now and subprojects can deps into it.

@webrtc, fyi
Owner: machenb...@chromium.org
Status: Verified (was: Available)

Sign in to add a comment