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

Issue 614508 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Jun 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Bbuildbot pinned manifest support

Project Member Reported by sbasi@chromium.org, May 24 2016

Issue description

From deymo:

"From the BrilloSync stage, it looks like the builder grabs the latest master at the time you run that, but I couldn't find any pinned manifest (like in cros canaries).
https://uberchromegw.corp.google.com/i/internal.client.brillo/builders/bbuildbot/builds/3457/steps/BrilloSync/logs/stdio

Can we somehow add the ArchiveManifest() to the bbuildbot so we can repro it? That wouldn't help in this case, but might help in the future."


 
Archiving the way ChromeOS does might be tricky, but something can be arranged.

At the very least, the builder to log the pinned manifest it used which would make it possible to reproduce, if not easy.

Comment 2 by de...@chromium.org, May 24 2016

Running "repo manifest -r" should be enough for now.
Status: Fixed (was: Untriaged)
Status: Verified (was: Fixed)
Closing. please reopen if its not fixed.

Sign in to add a comment