Skip to content

CLOUDP-295785 - add dockerfile_path to build_info.json #335

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

Open
wants to merge 91 commits into
base: master
Choose a base branch
from

Conversation

MaciejKaras
Copy link
Collaborator

@MaciejKaras MaciejKaras commented Aug 11, 2025

Summary

Moved dockerfile_path from code to build_info.json. It will be easier to refactor the filenames later and to see what files are used in each image type.

Proof of Work

CI + updated unit test passing.

Checklist

  • Have you linked a jira ticket and/or is the ticket in the title?
  • Have you checked whether your jira ticket required DOCSP changes?
  • Have you added changelog file?

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.
Julien-Ben and others added 15 commits August 8, 2025 15:20
This reverts commit c6fc163.
…d-versions

# Conflicts:
#	scripts/release/atomic_pipeline.py
#	scripts/release/build/image_build_process.py
#	scripts/release/build_context.py
…d-versions

# Conflicts:
#	scripts/release/atomic_pipeline.py
#	scripts/release/build/image_build_process.py
#	scripts/release/pipeline_main.py
# Conflicts:
#	scripts/release/atomic_pipeline.py
#	scripts/release/pipeline_main.py
# Conflicts:
#	scripts/release/atomic_pipeline.py
# Conflicts:
#	scripts/release/build_context.py
…ckerfiles

# Conflicts:
#	scripts/release/build/build_info.py
Copy link

⚠️ (this preview might not be accurate if the PR is not rebased on current master branch)

MCK 1.3.0 Release Notes

Bug Fixes

  • This change fixes the current complex and difficult-to-maintain architecture for stateful set containers, which relies on an "agent matrix" to map operator and agent versions which led to a sheer amount of images.
  • We solve this by shifting to a 3-container setup. This new design eliminates the need for the operator-version/agent-version matrix by adding one additional container containing all required binaries. This architecture maps to what we already do with the mongodb-database container.

Other Changes

  • Optional permissions for PersistentVolumeClaim moved to a separate role. When managing the operator with Helm it is possible to disable permissions for PersistentVolumeClaim resources by setting operator.enablePVCResize value to false (true by default). When enabled, previously these permissions were part of the primary operator role. With this change, permissions have a separate role.
  • subresourceEnabled Helm value was removed. This setting used to be true by default and made it possible to exclude subresource permissions from the operator role by specifying false as the value. We are removing this configuration option, making the operator roles always have subresource permissions. This setting was introduced as a temporary solution for this OpenShift issue. The issue has since been resolved and the setting is no longer needed.

@MaciejKaras MaciejKaras changed the base branch from master to maciejk/use-ar-related-versions August 11, 2025 18:41
@MaciejKaras MaciejKaras added the skip-changelog Use this label in Pull Request to not require new changelog entry file label Aug 11, 2025
@MaciejKaras MaciejKaras marked this pull request as ready for review August 11, 2025 18:55
@MaciejKaras MaciejKaras requested a review from a team as a code owner August 11, 2025 18:55
@MaciejKaras MaciejKaras requested review from m1kola and anandsyncs and removed request for a team August 11, 2025 18:55
Base automatically changed from maciejk/use-ar-related-versions to master August 12, 2025 10:58
# Conflicts:
#	build_info.json
#	scripts/release/atomic_pipeline.py
#	scripts/release/build/build_info.py
#	scripts/release/build/build_info_test.py
#	scripts/release/build/image_build_configuration.py
#	scripts/release/pipeline_main.py
@MaciejKaras MaciejKaras requested review from viveksinghggits and Julien-Ben and removed request for m1kola August 12, 2025 13:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip-changelog Use this label in Pull Request to not require new changelog entry file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants