Skip to content

Tag latest readiness and versionhook when building on master #205

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 4 commits into
base: master
Choose a base branch
from

Conversation

lsierant
Copy link
Contributor

@lsierant lsierant commented Jun 20, 2025

Summary

This is another attempt at publishing latest tags of readiness probes and versionhooks from CI after master merges. The previous attempt (#57) was unsuccessful and was reverted.

This problem affects multi-arch images as they're not using sonar and have multi-arch manifests pushed after sonar build in pipeline.py. Single-arch images have latest images published via sonar inventory

Current approach adds logic checking if we're not building from a patch (from PR or manually triggered evg pipeline) and in evg:

Proof of Work

Manual test

It's difficult to trigger "master" build from PR, so a manual test was performed by changing the condition [here] (https://github.com/mongodb/mongodb-kubernetes/pull/205/files#diff-6b92e3e77956f8020482ca91889a24f3411c9a4854f2aaaac30ee504ef26ede4R1012) with changed tag to latest-test
We can see latest-test pushed here

Build from PR

When building from PR it's not pushing tag: evg

The final test will be performed after merging.

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 checked for release_note changes?

Reminder (Please remove this when merging)

  • Please try to Approve or Reject Changes the PR, keep PRs in review as short as possible
  • Our Short Guide for PRs: Link
  • Remember the following Communication Standards - use comment prefixes for clarity:
    • blocking: Must be addressed before approval.
    • follow-up: Can be addressed in a later PR or ticket.
    • q: Clarifying question.
    • nit: Non-blocking suggestions.
    • note: Side-note, non-actionable. Example: Praise
    • --> no prefix is considered a question

@lsierant lsierant marked this pull request as ready for review June 20, 2025 10:14
@lsierant lsierant requested a review from a team as a code owner June 20, 2025 10:14
@@ -1007,8 +1007,24 @@ def build_image_generic(
# But since we don't run daily rebuilds on ecr image builds, we can do that step instead here.
# We only need to push manifests for multi-arch images.
create_and_push_manifest(registry_address, version, architectures=architectures)
latest_tag = "latest"
if not is_running_in_patch() and is_running_in_evg_pipeline():
logger.info(f"Tagging and pushing {registry_address}:{version} as {latest_tag}")
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

q: do you think this as an attribute and trace is useful? Consider the cross-patches query-ability.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants