New issue
Advanced search Search tips

Issue 904926 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: 5
NextAction: ----
OS: Chrome
Pri: 1
Type: Feature

Blocking:
issue 904881


Show other hotlists

Hotlists containing this issue:
CrOSParallelCQ


Sign in to add a comment

InitialCheckout

Project Member Reported by cindyb@google.com, Nov 13

Issue description

Get ToT checkout to sane state
 - repo recipe_module
 
See "scripts/repo_sync_manifest" which is currently being enhanced to do nearly everything needed to sync branches, versions, buildspecs, and cherry-pick in CLs as needed.

Status: Available (was: Untriaged)
Cc: dgarr...@chromium.org
Owner: athilenius@chromium.org
Don, what do you think the ETA is on that? I was planning on leveraging/stealing your work to implement syncing to manifests/ToT.
This landed today: https://crrev.com/c/1330170

It now supports everything except:

A) Cherry-picks defined inside a buildspec manifest.
B) "Local" cherry-picks (cros tryjob -p)

I plan to put it into production in the new "buildspec" builders I'm creating for firmware / factory.
Cool! I'm going to merge this into crbug.com/904926 because I don't think Initial Checkout really makes a ton of sense when Recipe is the one doing the checkout and it's updated out of band (via the ChOPs Recipe Builder). Sound reasonable?
Um... this is 904926.

But in general, yes. All of the sync stages should be merged into one bug.
I'm not sure what the other bug tracking the same thing happening in Recipes but as long as we have a bug tracking that Recipes impl, it makes sense to merge.
Status: Assigned (was: Available)
EstimatedDays: 5

Sign in to add a comment