test(docker-compose): Test rollback with a new version of the same image - #2971
test(docker-compose): Test rollback with a new version of the same image#2971vpodzime wants to merge 1 commit into
Conversation
|
@vpodzime, start a full integration test pipeline with:
my commands and optionsYou can prevent me from automatically starting CI pipelines:
You can trigger a client pipeline on multiple prs with:
You can trigger a client pipeline for a specific Mender Client release with:
You can trigger GitHub->GitLab branch sync with:
You can print PR statistics for a repository with:
You can deploy a review app with:
You can run e2e tests against a deployed review app with:
You can cherry pick to a given branch or branches with:
|
When loading a new version of a previously-loaded image, i.e. with different IDs, but both using the same tag, the tag is assinged to the new version image. On a rollback the tag needs to be re-assigned back to the old version of the image otherwise `docker compose` won't find it. Ticket: MEN-10114 Signed-off-by: Vratislav Podzimek <vratislav.podzimek+auto-signed@northern.tech>
6f5af08 to
75bace3
Compare
|
@mender-test-bot start integration pipeline |
|
Hello 😺 I created a pipeline for you here: Pipeline-2819749192 Build Configuration Matrix
|
Fails as expected. Let's see if it passes with mendersoftware/mender-container-modules#30 applied. |
|
Hello 😺 I created a pipeline for you here: Pipeline-2828527741 Build Configuration Matrix
|
When loading a new version of a previously-loaded image, i.e. with different IDs, but both using the same tag, the tag is assinged to the new version image. On a rollback the tag needs to be re-assigned back to the old version of the image otherwise
docker composewon't find it.Ticket: MEN-10114
Test for mendersoftware/mender-container-modules#30