tz-deployment

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Thank you

Thank you

looks good, thank you!

looks good, thank you!

Ahhhh, got it. I missed the "trigger". Thanks, resolved.

Ahhhh, got it. I missed the "trigger". Thanks, resolved.

The first build stage is intended for building an image for the individual common-ui whose codes are in this repository. Later on the common-ui and other xxx-ui's are combined within the tanzania-u...

The first build stage is intended for building an image for the individual common-ui whose codes are in this repository. Later on the common-ui and other xxx-ui's are combined within the tanzania-ui to create a tanzania-ui image

The second build-ui stage is just a trigger stage for the repository of tanzania-ui which is intended for building the tanzania-ui image which combines other xxx-ui's such as equipment-ui, auth-ui etc

The two stages are separated because the trigger for tanzania-ui building process should happen when the build for commons-ui is completed successfully.

This looks odd - as in the "build" stage is building and pushing a docker image for the common-ui from OpenLMIS, and then this "build_ui" step is building what's in this repo. How are these things...

This looks odd - as in the "build" stage is building and pushing a docker image for the common-ui from OpenLMIS, and then this "build_ui" step is building what's in this repo.

How are these things related, and why are they both ui builds in separate stages?

TZUP-291 Review and Fix CI/CD pipeline build for tz specific repositories
TZUP-291 Review and Fix CI/CD pipeline build for tz specific repositories
TZUP-217: Run the pcmt-integration service as part of the tz-distribution
TZUP-217: Run the pcmt-integration service as part of the tz-distribution
TZUP-202: CI/CD process for deploying tz_pcmt_uat
TZUP-202: CI/CD process for deploying tz_pcmt_uat
TZUP-204: CI/CD codes to upload Google Analytics file the server

TZUP-217: Run the pcmt-integration service as part of the tz-distribution

Add log container as a dependency to integration service

    • -0
    • +3
    /deployment/tzuat_env/docker-compose.yml
TZUP-217: Run the pcmt-integration service as part of the tz-distribution

    • -0
    • +11
    /deployment/tzuat_env/docker-compose.yml
TZUP-202: Refactor the openlmis UAT deployment to accomodate pcmt deployment.

- Separate Traefik deployment to it's own docker compose file and it's own network.

- Make sure openlmis uat works with the separated out traefik.

- Update the URL used to access docker.

    • -1
    • +6
    /deployment/tzuat_env/deploy_to_env.sh
    • -22
    • +12
    /deployment/tzuat_env/docker-compose.yml
    • -0
    • +32
    /deployment/tzuat_env/traefik-docker-compose.yml
merge with master

upgraded service versions in env file

TZUP-186: remove absolute docker-compose path to use what is available.

TZUP-186: install git so the deployment process succeeds.

TZUP-186: Setup a CI/CD process for deploying the reporting stack.

    • -0
    • +9
    /deployment/tz_reporting_env/services/init_env_gl.sh
changes to env file

TZUP-190: limit max connection at 5 per service.
TZUP-190: limit max connection at 5 per service.
TZUP-190: limit max connection at 5 per service.

    • -12
    • +12
    /deployment/tzuat_env/docker-compose.yml
add the common service to the tz distro

    • -1
    • +12
    /deployment/tzuat_env/docker-compose.yml