The build infrastructure uses old code.google.com paths everywhere in the infrastructure.
This needs to be fixed, but there are a few different strategies:
a) Do the full rename everywhere. This includes a potentially risky mass update of the
build dashboard datastore. The watcher tool will need to updated to use "go
get" to initially fetch repositories instead of "hg clone". The builder
daemons would not need to be updated.
b) Leave the paths as-is in the dashboard datastore, but update the builder daemons to
rewrite the paths before checking out the code. This requires updating all the running
builders, but is the lowest risk approach.
c) Have the dashboard app use the new paths in all its communications with the builders
and watcher, but keep using the old paths in the datastore. This also requires updating
the watcher code. The risk here is that we don't catch all the cases and corrupt the
datastore by accidentally putting in references to the new paths.
Approach "a' is the hardest but least gross approach. "c" is also
difficult and also the most gross. "b' is kinda gross but also low risk.
I might go ahead with plan B just to get 1.4 out the door, with a view to implementing
plan A further down the track.
The text was updated successfully, but these errors were encountered:
…d 'go test'
The dashboard still uses the old "code.google.com/p/go.*" import paths.
Rewrite them to the new "golang.org/x/*" before running 'go get' and 'go test'.
Update golang/go#9079.
LGTM=rsc
R=rsc, bradfitz
CC=golang-codereviews
https://golang.org/cl/174740043
…d 'go test'
The dashboard still uses the old "code.google.com/p/go.*" import paths.
Rewrite them to the new "golang.org/x/*" before running 'go get' and 'go test'.
Update golang/go#9079.
LGTM=rsc
R=rsc, bradfitz
CC=golang-codereviews
https://golang.org/cl/174740043
rsc
changed the title
go.tools/dashboard: make builders aware of golang.org/x/... sub-repo paths
x/build/dashboard: make builders aware of golang.org/x/... sub-repo paths
Apr 26, 2015
The text was updated successfully, but these errors were encountered: