[MGNLTEST-312] Local usage of docker-compose deploys "arbitrary" versions of test-webapps versions Created: 03/Oct/22  Updated: 27/Oct/22

Status: Open
Project: Magnolia Test Framework
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Christoph Meier Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Team: Foundation

 Description   

Local usage of docker-compose deploys "arbitrary" versions of test-webapps versions (for ce, dx-core ... test-fkw maybe too)

 

To run UI-tests locally we have the file "docker-compose.yml" - which reads values from .env file.

Observation is that the versions of the test-webapps deployed to local docker is arbitrary.

  • Sometimes when having checked out master, 6.2-SNAPSHOTs are deployed
  • Sometimes when having checked out release/6.2, 6.3-SNAPSHOTS are deployed

On jenkins the test-webapps are deployed correctly.

On ce, dx-core, the .env sets

MAGNOLIA_VERSION=1.0

(In test-fkw/.env - it is set to 6.2-SNAPSHOT)

For me it is not totally clear  -  how docker knows what version needs to be deployed,
anyhow, the docker-compose should reliably deploy the proper version of the test-webapps.

 

There are some notes on stack-overflow that IntelliJ may cache env-file values, but that is not totally clear. And maybe there's another "culprit".

 

Links:


Generated at Mon Feb 12 07:47:38 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.