Uploaded image for project: 'Magnolia Test Framework'
  1. Magnolia Test Framework
  2. MGNLTEST-312

Local usage of docker-compose deploys "arbitrary" versions of test-webapps versions

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Unresolved
    • Neutral
    • None
    • None
    • None

    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:

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              Unassigned Unassigned
              cmeier Christoph Meier
              Foundation
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:

                Checklists

                  Task DoD