Run backend e2e tests with given gateway docker tag when provided in PR body, add dev docs #1624
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.
___REQUIRES_GATEWAY_PR___="116"
Description
Closes #1538
For reference see NASA-AMMOS/aerie-ui#1439
This PR contains two things:
aerie
backend PRs to specify anaerie-gateway
PR/image to use for e2e tests - since, as noted in this comment from @Mythicaeda, the backend e2e tests may rely on changes in Gateway. This is an exact copy of the approach from Run UI e2e tests with given aerie/gateway docker tags when provided in PR body aerie-ui#1439 applied to theaerie
backend e2e testsVerification
I tested this PR both with and without the
REQUIRES_GATEWAY_PR
tag at the top, and verified that when it is present, the e2e test action correctly pulls and runs the gateway image tagged aspr-116
(shown in the workflow run logs)