[8.18] backport #4912 #4985 #5000 #5075#5397
Conversation
Reimplement Makefile targets in mage. Change buildkite pipeline to use mage. Change Dockerfile* to use mage. (cherry picked from commit db5f46b) # Conflicts: # .buildkite/pipeline.yml # .buildkite/scripts/common.sh # .buildkite/scripts/local_build.sh # .buildkite/scripts/test-release.sh # Dockerfile.build # Dockerfile.fips # Makefile # NOTICE.txt # README.md # dev-tools/cloud/Makefile # dev-tools/cloud/terraform/main.tf # dev-tools/e2e/Dockerfile # dev-tools/e2e/build.sh # dev-tools/e2e/validatecerts.go # dev-tools/go.mod # dev-tools/go.sum # docs/developers-guide.md # docs/docker-images.md # docs/fips.md # testing/e2e/fips_test.go
* Ensure directory is made within zip artifacts * Make test:release extraction stricter
…#5000) Fail the pipeline if cloude2e tests can't run. mage docker:image now uses the DOCKER_IMAGE env var.
Fixes issue where change from make to mage, result in the loss of creating multiple platform images.
🎉 Snyk checks have passed. No issues have been found so far.✅ security/snyk check is complete. No issues have been found. (View Details) ✅ license/snyk check is complete. No issues have been found. (View Details) |
a41e112 to
2cfbe2a
Compare
2cfbe2a to
c35c19f
Compare
|
@pkoutsovasilis, for some reason the check-ci step is failing in buildkite but not on my local machine; i recall seeing something like this before but I don't remember how we resolved this, do you remember how to resolve this? EDIT: I think it's because the mod list that is passed when generating the notice file does not have the |
|
This pull request is now in conflicts. Could you fix it @michel-laterman? 🙏 |
|
This pull request is now in conflicts. Could you fix it @michel-laterman? 🙏 |
|


Backport PRs #4912 #4985 #5000 #5075 to 8.18 so that mage is used instead of Make.
Do additional cleanup so FIPS references have been removed.