You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CLOUDP-295785 - Fix multi-arch builds by migrating away from goreleaser (#547)
# Summary
⚠️ Some of the files were moved and this messes up GitHub preview. It's
better to review the last commit with all the changes
ec01373
Completely removed `goreleaser` usage in the project. It was preventing
us to build multiarch `kubect-mongodb` plugin binaries. There were also
other reasons to drop `goreleaser` i.e. it was only used to build
binaries, nothing else was used, but required us to keep additional,
static `.goreleaser.yaml` that was not compatible with
`build_info.json`.
This PR also improves quite a lot of other things:
- moves building of `kubectl-mongodb` plugin to a separate evergreen
task
- `kubectl-mongodb` plugin is now only dowloaded when building test
image. This means we need to wait with building test image for
`kubectl-plugin` to be available in s3
- `promote_kubectl_plugin.py` now uses temp_dir instead of hardcoded
`./artifacts` dir. Previously we couldn't re-run the promotion pipeline
if the signatures were already present on the machine: `Signature
already exists. Displaying proof`
- simplified and unified the
[build_kubectl_plugin.py](https://github.com/mongodb/mongodb-kubernetes/pull/547/files#diff-a6df2ec746c87a5d07b813bb16612734474e6c40f6f60a38f194802403dd4fe7)
and
[download_kubectl_plugin.py](https://github.com/mongodb/mongodb-kubernetes/pull/547/files#diff-eac03d2b21304201e625cb87a6701449d4ba1cfa0c3dbaa129db2dbd6522f2d4)
scripts
- removed all references to `goreleaser`
- `kubectl-mongodb` also pushes binaries to s3 release bucket so they
can be used for e2e smoke tests
- `kubectl-mongodb` is now pushed to staging and released with two new
architectures:
- `linux/s390x`
- `linux/ppc64le`
## Proof of Work
Passing CI for PR.
Passing CI for [smoke arm on staging
scenario](https://spruce.mongodb.com/version/68fb37de9e149f0007e8638a)
(with arm smoke tests enabled)
Passing CI for [release
scenario](https://spruce.mongodb.com/version/68fa1b1b9b6f3600075262c0/tasks?sorts=STATUS%3AASC%3BBASE_STATUS%3ADESC)
(`release_kubectl_mongodb_plugin` fails on adding assets to GH release,
which is expected since there is no release `rc-1.3.0`)
## Checklist
- [x] Have you linked a jira ticket and/or is the ticket in the title?
- [x] Have you checked whether your jira ticket required DOCSP changes?
- [x] Have you added changelog file?
- use `skip-changelog` label if not needed
- refer to [Changelog files and Release
Notes](https://github.com/mongodb/mongodb-kubernetes/blob/master/CONTRIBUTING.md#changelog-files-and-release-notes)
section in CONTRIBUTING.md for more details
0 commit comments