General: Fix wrong Artemis image issue on Bamboo E2E multinode configuration
#8852
Conversation
This file contains 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
…s in compose file" This reverts commit d3b063f.
…node-configuration-wrong-branch
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.
Checklist
General
Client
Motivation and Context
Bamboo build plan of E2E Playwright tests use wrong Artemis image on multi-node configuration. It uses the
developimage rather than PR-related one. As a result, tests are run for a wrong branch and builds either fail/succeed incorrectly or never finish.Description
This PR changes the pull policy of multi-node configuration on its compose file to default, which means to pull the Artemis image from
latestonly if there is no image found locally. Fixes Issue #8831.Another change is to pull the corresponding database image during compose command in shell script, used for deploying the services and running E2E tests. It was using a wrong service name.
Steps for Testing
Check both Playwright E2E single-node and multi-node build plans for correctly executing and finishing the tests. Check video recordings of tests from both build plans to ensure they run on the branch this PR belongs to. To watch the recordings, check the artifacts of these builds:
P.S. E2E test recording of Playwright tests are currently turned off and only the builds on URLs above contain recordings for debugging purposes
Testserver States
Note
These badges show the state of the test servers.
Green = Currently available, Red = Currently locked
Review Progress
Code Review
Manual Tests