chore(web): add a script to spawn evergreen patch that runs compass-web with Atlas e2e tests COMPASS-10227#7861
Merged
gribnoysup merged 13 commits intomainfrom Mar 17, 2026
Conversation
…eb with Atlas e2e tests
…g; clearer arch mapping logic
309ad0e to
ddbf8e4
Compare
nbbeeken
approved these changes
Mar 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This patch adds new script to compass-web workspace that will download latest evergreen cli, create and schedule new patch with compass-web e2e tests against a specified environment, and then wait for the patch to finish (one way or another).
The goal is to use this script in the GHA workflow that releases compass-web to selected environment, but a prerequisite for this is to removeThis was resolved, so this patch now also includes changes that add the test running script to the GHA workflowpatchable: falseflag usage from our evergreen config. I have a draft PR for that, but currently trying to figure out with the evergreen team why exactly it's not working as expected. This is taking longer than I thought it would, so in the meantime I'm opening this patch with just the script for review.Credentials are available in our team 1pwd vault if you want to test the script yourself.