Add Docker update pipeline/yml, build asset JSON generation command #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add a build asset JSON generation command.
dockermanifest
model. I call it a "summary" in a couple places.Add a yaml pipeline that triggers on microsoft/go build completion and submits an auto-update PR to microsoft/go-docker. If a PR already exists, adds the commit to the end of the PR branch.
This PR doesn't include much error handling or retries, so updates running at the same time will race. I filed Add error handling/retries to Go -> Docker auto-update infra go#209 to track fixing that up.
Fix some assumptions about the branch model that I ran into while testing. Mostly, remove assumption that the PR will use a fork.
Simplify the update commands into just the one for update PRs. It always runs from this repo now, with a temp Git dir to clone go-docker.
Here's a testing PR: microsoft/go-images#7
I set up two microsoft/go dev branches to produce build asset JSON files and ran the update build once for each:
Here's what the dev branches did: https://github.com/microsoft/go/compare/dev/dagood/manifest?expand=1
I used
go mod vendor
on top of those changes to generate branches that would run in CI, because go-infra is private and I haven't set up auth. I want to set this repo public and use that when I submit the PR to microsoft/go.