grunt-release build numbers no longer increment after move to swarming |
||
Issue descriptionPreviously, for each build (config) there was a single builder, with a monotonic build number. The build number incremented on every build, and were easy to predict, understand, and use to reference a specific build, via a URL, like this: https://uberchromegw.corp.google.com/i/chromeos/builders/grunt-release/builds/763 Issue (a) - the "uberchromegw" link above was working as recently as last week, but now returns a 404. The equivalent build information can still be found using a "cros-goldeneye" URL: 763 - https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?builderName=grunt-release&buildNumber=763 However, since grunt-release "moved to swarming", the useful "monotonic build number" is now always just "0". Build numbers are now referenced via your choice of unpredictable very large integers, "CIDB build ID" or "Buildbucket ID": - CIDB build ID: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?id=2716759 - Buildbucket ID: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8942059981280261744 It would be very useful to bring back the concept of a monotonically increment-by-1 identifier for each build config if possible.
,
Jul 9
Ugh - this was supposed to be a "2 part" bug. For clarity: Issue (a) the "uberchromegw" links are now 404s (instead of redirecting?) Issue (b) please bring back a monotonic "inc-by-1" config build number.
,
Jul 9
a) The uberchromegw links are dead, and will stay that way.
1) The buildbot data of a build from before the migration was lost when the
build was removed from buildbot.
2) We can't really make buildbot code changes to create the redirects.
3) The types of id's in the URLs don't exist in the new system, so a simple redirect won't work.
4) I did suggest that people start using Legoland about 6 months ago for this
reason (it has had a rougher start than expected, so I'm not surprised people didn't listen).
5) go/legoland does have build history from before the migration.
b) The monotonic numbers aren't a native concept in the new system. Re-adding something similar is
being considered, but behind other UI issues (like performance).
,
Jul 9
It appears that buganizer search is down, so I'm not able to find / link to the tracking bug for re-adding them. Passing to athilenius@ who surely owns that bug and will be driving it.
,
Jul 10
There is b/78123581, is that what you're talking about Don?
,
Jul 10
Yes, I that's the bug I was thinking of. Though, there are also been multiple discussions about the issue among multiple sets of people and on multiple docs, without any clear conclusions.
,
Jul 12
This will hopefully be addressed by cl/204170088. It's a stopgap and by no means a "good" solution, but it will do till the rewrite goes live.
,
Jul 30
|
||
►
Sign in to add a comment |
||
Comment 1 by jclinton@chromium.org
, Jul 9Status: Assigned (was: Untriaged)