Add main (1.19) and main FIPS tags #127
Merged
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 microsoft/go
main
builds to the microsoft/go-imagesmicrosoft/nightly
branch. Add FIPS tags that build on top of them and setGOEXPERIMENT=opensslcrypto
by default.fips-linux
variant andmain
for microsoft/go-images go-infra#45The plan is to only build
main
tags in this repo'smicrosoft/nightly
branch, not the MAR/MCR-targetingmicrosoft/main
branch. Builds that come out of microsoft/go'smicrosoft/main
branch never belong on MAR, only in our public ACR for evaluation purposes.Once 1.19 is released and there's a release branch, the FIPS tags will be included in MAR builds.
Having go-images produce nightly builds based on
microsoft/main
will help us make sure ourmicrosoft/main
changes are ready for the coming 1.19 release. In the future it will help with 1.20, etc.Review tips:
variant
type to see the templates in action.manifest.json
is generated fromversions.json
. Supportfips-linux
variant andmain
for microsoft/go-images go-infra#45 has more context on the details in this file.Example internal build: https://dev.azure.com/dnceng/internal/_build/results?buildId=1806155&view=results