Upgrade the Vera Server applications

These instructions will automatically update the Vera components configured inside your Docker compose file. In a standard installation, that will include the Vera API Server, the Tricentis Vera Web Portal, Vera Microservices and RabbitMQ.

Updated: 09 DEC 2020

The Docker login credentials listed below have been updated. The credentials listed before this update will not work.

Download the new software

The recommended Vera deployment now uses an environment variable file named .env in the same directory as the docker-compose.yml file. For more information on updating your docker deployment, check out Vera Deployment with Docker.

To download the new software, follow these steps:

  1. Open an Administrative PowerShell prompt.

  2. Navigate to the Vera Docker Compose directory that was configured during installation. This is the directory that contains the docker-compose.yml and .env files.

  3. Update the VERA_RELEASE_TAG variable in the .env file with the corresponding release version .env. For example: VERA_RELEASE_TAG=2025.2.0

  4. Add container sections for vera.api.workflows, vera.worker.workflows.

  5. If upgrading from 2024.1 or earlier, rename the vera.api.qtest.routeactions container to vera.api.qtest in the docker-compose.yml file.

    Docker-Compose example:

    Copy 
    vera.server:
        image: veraserver20190209075900.azurecr.io/tx3/vera-server-legacy:${VERA_RELEASE_TAG}

    vera.web.portal:
        image: veraserver20190209075900.azurecr.io/tx3/vera-web-portal:${VERA_RELEASE_TAG}

    vera.worker.qtest:
        image: veraserver20190209075900.azurecr.io/tricentis/vera-worker-qtest:${VERA_RELEASE_TAG}

    vera.api.qtest:
       image: veraserver20190209075900.azurecr.io/tricentis/vera-api-qtest:${VERA_RELEASE_TAG}

    vera.api.routes.routeevents:
        image: veraserver20190209075900.azurecr.io/tricentis/vera-api-routes-routeevents:${VERA_RELEASE_TAG}

    vera.api.connections.testconnection:
       image: veraserver20190209075900.azurecr.io/tricentis/vera-api-connections-testconnection:${VERA_RELEASE_TAG}
       
    vera.worker.jira:
       image: veraserver20190209075900.azurecr.io/tricentis/vera-worker-jira:${VERA_RELEASE_TAG}

    vera.api.jira.routeactions:
       image: veraserver20190209075900.azurecr.io/tricentis/vera-api-jira-routeactions:${VERA_RELEASE_TAG}
       
    vera.jira.jobservice:
       image: veraserver20190209075900.azurecr.io/tricentis/vera-worker-jobservice:${VERA_RELEASE_TAG}
       
    vera.worker.audithistory:
       image: veraserver20190209075900.azurecr.io/tricentis/vera-worker-audithistory:${VERA_RELEASE_TAG}

    vera.api.audithistory:
       image: veraserver20190209075900.azurecr.io/tricentis/vera-api-audithistory:${VERA_RELEASE_TAG}

    vera.api.domains:
       image: veraserver20190209075900.azurecr.io/tricentis/vera-api-domains:${VERA_RELEASE_TAG}
       
    vera.api.documents:
       image: veraserver20190209075900.azurecr.io/tricentis/vera-api-documents:${VERA_RELEASE_TAG}
       
    vera.api.traceability:
       image: veraserver20190209075900.azurecr.io/tricentis/vera-api-documents:${VERA_RELEASE_TAG}

    vera.api.verification:
       image: veraserver20190209075900.azurecr.io/tricentis/vera-api-verification:${VERA_RELEASE_TAG}

    vera.api.workflows:
       image: veraserver20190209075900.azurecr.io/tricentis/vera-api-workflows:${VERA_RELEASE_TAG}

    vera.worker.carbone:
       image: veraserver20190209075900.azurecr.io/tricentis/vera-worker-carbone:${VERA_RELEASE_TAG}

    vera.worker.domains:
       image: veraserver20190209075900.azurecr.io/tricentis/vera-worker-domains:${VERA_RELEASE_TAG}
      
    vera.worker.documents:
       image: veraserver20190209075900.azurecr.io/tricentis/vera-worker-documents:${VERA_RELEASE_TAG}

    vera.worker.traceability:
       image: veraserver20190209075900.azurecr.io/tricentis/vera-worker-traceability:${VERA_RELEASE_TAG}

    vera.worker.verification:
       image: veraserver20190209075900.azurecr.io/tricentis/vera-worker-verification:${VERA_RELEASE_TAG}

    vera.worker.workflows:
       image: veraserver20190209075900.azurecr.io/tricentis/vera-worker-workflows:${VERA_RELEASE_TAG}

    vera.query.engine:
       image: veraserver20190209075900.azurecr.io/tricentis/vera-query-engine:${VERA_RELEASE_TAG}ngine:${VERA_RELEASE_TAG}

  6. Execute the following commands:

    • docker login veraserver20190209075900.azurecr.io -u fc12bdd5-6753-40b3-a4da-32bc5d451b39 -p 7p/bia7LROke+DJjPIcCAFXatMlYv94vNNO7lELTiL+ACRAjR4zk

    • docker-compose pull

Restart Vera with the updated software

These steps will result in a temporary outage of the Vera software lasting several minutes. Therefore, we recommend scheduling an outage window before executing these steps.

To restart Vera with the updated software, follow these steps:

  1. Open an Administrative PowerShell prompt.

  2. Navigate to the Vera Docker Compose directory that was configured during installation. This is the directory that contains the docker-compose.yml file.

  3. Execute the following commands:

    • docker-compose down

    • docker-compose up -d