Pass toolchain archive to make in pipeline template

[dmcilvaney]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

The toolkit should generally be called with a static set of inputs, we are using TOOLCHAIN_ARCHIVE=./path/to/toolchain.tar.gz when we call make toolchain. We should continue to use the same input for future commands. Generally we won't re-create the toolchain .rpms since nothing will cause a rebuild, but we should be defensive. If something DOES change, without setting TOOLCHAIN_ARCHIVE the toolkit will assume it should download the .rpms. This may fail if one of the toolchain packages has been bumped and was rebuild in the previous stage.

If we pass TOOLCHAIN_ARCHIVE to all commnads that use the toolchain the toolkit will know to extract antying that is missing from the archive instead of trying to download a missing file from PMC.

Change Log

• Pass TOOLCHAIN_ARCHIVE to the "Build packages" stage of PackageBuild.yml.

Does this affect the toolchain?

NO

Associated issues

• https://dev.azure.com/mariner-org/mariner/_git/CBL-Mariner-Pipelines/pullrequest/16818

Test Methodology

• Pipeline build id: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=443426&view=results

[dmcilvaney]

Will look into suggestions, hadn't had a chance to run a test yet so I'll update and then run a build.