Establish API to perform branch creation |
|||
Issue descriptionToday, we use a branch utility “builder” to create new firmware, factory, or release branches. This has been broken at ToT for some time forcing the TPM’s to check out an older branch to perform this operation. The tasks required are: make all of the appropriate GoB requests to perform branch creation for all repos defined in the manifest. Once complete, a single manifest branch commit establishes the branch’s differentiation from mainline. This item tracks moving all of this to a server API. Previous discussions around this have centered around the implementation: whether it should be backed by a builder to perform the work or whether all work should be done in a persistent server. Either way, we need a consistent mechanism by which external systems can request creation of new branches programmatically. Over to the Build team to triage for an owner.
,
Nov 12
we have issue 825241 for writing a local util that specific people (TPMs) would be able to run to create branches. that's as much as we planned on doing. if we wanted to talk about moving this as a remote service, the only option in my mind is to have it be part of the existing GE service so TPMs/etc... could just fill out a form and submit it. GE already has support for generating git/gerrit CLs, so seems like creating a branch from GE is feasible. then there's no need for an API or any dedicated service. the API would be interpreting the manifest format (which we've already defined).
,
Nov 13
targeting this for the build service based on discussions today will discuss further with evan
,
Nov 13
follow up from today's discussion is that the GE logic is being split out into places that make more sense, in which case having a build service handle manifest parsing and branch creation makes a bit more sense
,
Nov 13
|
|||
►
Sign in to add a comment |
|||
Comment 1 by jclinton@chromium.org
, Nov 12