Skip to content

Add missing e2e_smoke_release context #106

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

Merged
merged 3 commits into from
May 13, 2025
Merged

Conversation

MaciejKaras
Copy link
Collaborator

@MaciejKaras MaciejKaras commented May 12, 2025

Summary

Add missing e2e_smoke_release and e2e_static_smoke_release context.

Previous error:
(!!) Cannot switch context: File scripts/dev/contexts/e2e_static_smoke_release does not exist.

Proof of Work

https://spruce.mongodb.com/version/68224ca9feee0e0007c41c3c/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 marked this pull request as ready for review May 12, 2025 19:35
@MaciejKaras MaciejKaras requested a review from a team as a code owner May 12, 2025 19:35
@MaciejKaras MaciejKaras requested review from nammn and Julien-Ben May 12, 2025 19:35
@MaciejKaras MaciejKaras changed the base branch from master to release-1.0 May 12, 2025 19:36
@MaciejKaras MaciejKaras force-pushed the fix/mk-smoke-tests branch from 76c5422 to 269db5c Compare May 12, 2025 19:36
@MaciejKaras MaciejKaras changed the title Add missing e2e_smoke_release contex Add missing e2e_smoke_release context May 12, 2025
Comment on lines +28 to +29
DATABASE_VERSION="$(grep -o '"databaseImageVersion": "[^"]*' release.json | grep -o '[^"]*$')"
export DATABASE_VERSION
Copy link
Member

Choose a reason for hiding this comment

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

nit: is this not possible? 🤔

Suggested change
DATABASE_VERSION="$(grep -o '"databaseImageVersion": "[^"]*' release.json | grep -o '[^"]*$')"
export DATABASE_VERSION
export DATABASE_VERSION="$(grep -o '"databaseImageVersion": "[^"]*' release.json | grep -o '[^"]*$')"

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Probably it's possible, let's see ;) I just copied the existing e2e_smoke and e2e_static_smoke, didn't dive into what's exactly inside

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Screenshot 2025-05-13 at 10 12 34

@MaciejKaras MaciejKaras enabled auto-merge (squash) May 13, 2025 08:17
@MaciejKaras
Copy link
Collaborator Author

evergreen refresh

@MaciejKaras MaciejKaras disabled auto-merge May 13, 2025 08:34
@MaciejKaras MaciejKaras enabled auto-merge (squash) May 13, 2025 08:34
@MaciejKaras
Copy link
Collaborator Author

evergreen retry

@MaciejKaras
Copy link
Collaborator Author

evergreen refresh

@MaciejKaras MaciejKaras force-pushed the fix/mk-smoke-tests branch from 8e04f33 to 4ecea8a Compare May 13, 2025 09:35
@MaciejKaras
Copy link
Collaborator Author

evergreen retry

@MaciejKaras MaciejKaras merged commit 8f2abb5 into release-1.0 May 13, 2025
4 of 6 checks passed
This was referenced May 13, 2025
MaciejKaras added a commit that referenced this pull request May 14, 2025
# Summary

Add missing `e2e_smoke_release` and `e2e_static_smoke_release` context.

Previous error:
```(!!) Cannot switch context: File scripts/dev/contexts/e2e_static_smoke_release does not exist.```

## Proof of Work

https://spruce.mongodb.com/version/68224ca9feee0e0007c41c3c/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](https://docs.google.com/document/d/1T93KUtdvONq43vfTfUt8l92uo4e4SEEvFbIEKOxGr44/edit?tab=t.0)
- 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

---------

Co-authored-by: Nam Nguyen <[email protected]>
MaciejKaras added a commit that referenced this pull request May 14, 2025
# Summary

Add missing `e2e_smoke_release` and `e2e_static_smoke_release` context.

Previous error:
```(!!) Cannot switch context: File scripts/dev/contexts/e2e_static_smoke_release does not exist.```

## Proof of Work

https://spruce.mongodb.com/version/68224ca9feee0e0007c41c3c/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](https://docs.google.com/document/d/1T93KUtdvONq43vfTfUt8l92uo4e4SEEvFbIEKOxGr44/edit?tab=t.0)
- 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

---------

Co-authored-by: Nam Nguyen <[email protected]>
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.

5 participants