-
Notifications
You must be signed in to change notification settings - Fork 17
CLOUDP-295785 - release tasks integration with atomic_pipeline.py
#344
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Fix build scenario Remove create and push manifests Continue improvement to main Simplify main and build_context missed Pass Build Configuration object directly Use legacy and new pipeline Fix Remove --include Rename MCO test image Multi platform builds, with buildx TODOs Implement is_release_step_executed() Fix init appdb image Import sort black formatting Some cleaning and version adjustments Adapt main to new build config Add buildscenario to buildconfig Handle build env Renaming, usage of high level config All images build pass on EVG Lint Explicit image type, support custom build_path Replace old by new pipeline in EVG Add documentation Split in multiple files, cleanup WIP, passing builds on staging temp + multi arch manifests Replace usage of sonar Remove namespace Remove pin_at and build_id Copied pipeline, removed daily builds and --exclude
This reverts commit 426e522.
# Conflicts: # scripts/release/atomic_pipeline.py # scripts/release/build/build_info.py # scripts/release/build/build_info_test.py
MCK 1.3.0 Release NotesNew FeaturesMulti-Architecture SupportWe've added comprehensive multi-architecture support for the kubernetes operator. This enhancement enables deployment on IBM Power (ppc64le) and IBM Z (s390x) architectures alongside
Bug Fixes
Other Changes
|
# Conflicts: # scripts/release/tests/build_info_test.py
include: | ||
- filename: .evergreen-functions.yml | ||
|
||
tasks: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should consider whether we want to migrate om and agent (independent release lifecycle) into this file or another independent file
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also thought about that, but first I wanted to tackle operator release tasks.
.evergreen-functions.yml
Outdated
binary: scripts/dev/run_python.sh scripts/release/pipeline_main.py --parallel ${image_name} | ||
env: | ||
git_tag: ${triggered_by_git_tag} | ||
binary: scripts/dev/run_python.sh scripts/release/pipeline_main.py ${image_name} --build-scenario release --version ${git_tag} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this won't work for om and agent, we should add support for these as well - otherwise we will be living in a limbo of requiring supporting both
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nammn I think you've already moved om and agent into the new pipeline, right?
# Conflicts: # build_info.json # scripts/dev/contexts/e2e_mdb_kind_ubi_cloudqa # scripts/dev/contexts/e2e_static_mdb_kind_ubi_cloudqa # scripts/dev/contexts/local-defaults-context # scripts/dev/contexts/variables/om60 # scripts/release/atomic_pipeline.py # scripts/release/build/image_build_configuration.py # scripts/release/build/image_build_process.py # scripts/release/pipeline_main.py # scripts/release/tests/build_info_test.py # scripts/release/tests/release_info_test.py
93648fd
to
9ced848
Compare
1f997c8
to
1f0f78d
Compare
Summary
Created new
.evergreen-release.yml
file that contains all release tasks including integration withkubectl-mongodb
plugin release task. All of the variants are triggered only whengithub_tag
is added.Additional changes:
om
andagent-pct
used during OM bump to newatomic_pipeline.py
.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
formatrelease_pipeline
evergreen function that usesrelease
build scenario and version provided bygit_tag
Proof of Work
List of tasks that are triggered when doing manual patch:
Checklist
skip-changelog
label if not needed