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 - release tasks integration with atomic_pipeline.py (#344)
# Summary
⚠️ **Important notice**
This PR contains some changes from
#336, but they are not
used yet and don't impact the PRs or patches. They are included because
previously this PR was stacked on the staging PR and it is much easier
to include them. The changes that are included:
- `latest_tag` support - this is needed for staging builds, but like
mentioned earlier, staging builds are not yet used
- replace `268558157000.dkr.ecr.us-east-1.amazonaws.com/dev` with
`BASE_REPO_URL`. This will be used to distinguish different repo urls:
dev, staging and release. Currently hardcoded to
`268558157000.dkr.ecr.us-east-1.amazonaws.com/dev`
---
**This change is made to unblock the release of MCK 1.3.0. It is not
final state of the release mechanism and most of it will be replaced by
image promotion process.**
Created new `.evergreen-release.yml` file that contains all release
tasks including integration with `kubectl-mongodb` plugin release task.
All of the variants are triggered only when `github_tag` is added.
Additional changes:
- each released image will be also released with additional `olm_tag`
that has dynamic timestamp part. It will prevent accidental overriding
the tags used by OLM. The tag syntax is
`{version}-olm-{timestamp_suffix}` where timestamp suffix is in
`%Y%m%d%H%M%S` format
- created separate `release_operator_pipeline` evergreen function that
uses `release` build scenario and version provided by `git_tag`
- fixed and bumped preflight script
## Proof of Work
List of tasks that are triggered when doing manual patch:
<img width="2036" height="1017" alt="Screenshot 2025-09-03 at 11 00 16"
src="https://github.com/user-attachments/assets/b3e7e707-3929-4f88-bc4f-2f998a16482a"
/>
⚠️ This PR was tested by running evergreen command locally:
```
sudo evergreen patch -p mongodb-kubernetes -a release -d "Release test" -f -y -u --browse --path .evergreen.yml --param RELEASE_OPERATOR_VERSION=1.3.0-rc
```
Link to evg job
-> https://spruce.mongodb.com/version/68b81b45285a950007bc8398
## 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