Skip to content

Remove duplicated e2e_*_smoke_release variants. #110

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

Conversation

MaciejKaras
Copy link
Collaborator

@MaciejKaras MaciejKaras commented May 13, 2025

Summary

Added e2e_*_smoke_release to git_tag_aliases

Proof of Work

e2e_*_smoke tasks are part of https://spruce.mongodb.com/version/682321bcc5dd2f0007539fd0/tasks?sorts=STATUS%3AASC%3BBASE_STATUS%3ADESC

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

@MaciejKaras MaciejKaras force-pushed the fix/mk-smoke-tests branch from bfe0c8c to 6d474e2 Compare May 13, 2025 10:40
@MaciejKaras MaciejKaras marked this pull request as ready for review May 13, 2025 10:42
@MaciejKaras MaciejKaras requested a review from a team as a code owner May 13, 2025 10:42
@@ -230,8 +230,8 @@ github_checks_aliases:
# Triggered on git tag
git_tag_aliases:
- git_tag: "^(\\d+\\.)?(\\d+\\.)?(\\d+)$"
variant_tags: [ "release" ]
task_tags: [ "image_release", "image_preflight", "openshift_bundles", "code_snippets" ]
variant_tags: [ "release", "e2e_smoke_release_test_suite" ]
Copy link
Member

Choose a reason for hiding this comment

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

Is my understanding correct that the release can be started without depending on successful e2e tests?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

yes, e2e_smoke_release_test_suite variant is only depending on init_test_run and nothing will block other release tasks to run

variant_tags: [ "release" ]
task_tags: [ "image_release", "image_preflight", "openshift_bundles", "code_snippets" ]
variant_tags: [ "release", "e2e_smoke_release_test_suite" ]
task_tags: [ "image_release", "image_preflight", "openshift_bundles", "code_snippets", "patch-run" ]
Copy link
Member

Choose a reason for hiding this comment

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

Why does this now include patch-run task tags?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

patch-run is required because e2e_smoke_release_test_suite variant has tasks with that tag. It will only add tasks matching variant e2e_smoke_release_test_suite and not all e2e tests

@SimonBaeumer
Copy link
Member

@MaciejKaras Please ask @nammn or @mircea-cosbuc for a peer review too. I don't feel very confident reviewing this change.

@MaciejKaras MaciejKaras force-pushed the fix/mk-smoke-tests branch from 92605b1 to 3a6b3c2 Compare May 18, 2025 10:47
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.

3 participants