tz-deployment

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
commented latest reporting

uodated ci/cd for the reporting stack

uodate rejections

Added rejection category reasons

Added rejection reasons

Added updated version of superset from core openlmis changes

Added updated version of superset from core openlmis changes

updated reference-ui snapshot version to 8.3.5

updated requisition snapshot version to 8.3.5

Update .gitlab-ci.yml file

TZUP-276:-Added new superset report version

    • -0
    • +26
    /deployment/reporting_uat_latest_env/.env
    • -0
    • +108
    /deployment/reporting_uat_latest_env/README.md
    • -0
    • +30
    /deployment/reporting_uat_latest_env/config/init.sh
  1. … 45 more files in changeset.
TZUP-276:-Created CI/CD to deploy reporting stack to UAT

TZUP-276:-Created CI/CD to deploy reporting stack to UAT

TZUP-276:-Created CI/CD to deploy reporting stack to UAT

TZUP-276:-Created CI/CD to deploy reporting stack to UAT

    • -0
    • +26
    /deployment/tanzania_uat_reporting/.env
    • -0
    • +90
    /deployment/tanzania_uat_reporting/README.md
    • -0
    • +8
    /deployment/tanzania_uat_reporting/config/Dockerfile
    • -0
    • +30
    /deployment/tanzania_uat_reporting/config/init.sh
  1. … 45 more files in changeset.
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?

Updated referencedata version to 15.2.5-snapshot

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
Install docker-compose on before_script:

Attempt to make the deployment work.

    • -3
    • +0
    /deployment/tzuat_env/deploy_to_env.sh
TZUP-291 revert to tcp on remote docker communication

    • -1
    • +1
    /deployment/tz_pcmt_uat/deploy_to_env.sh
TZUP-291 use ssh instead of tcp on remote docker communication

    • -1
    • +1
    /deployment/tz_pcmt_uat/deploy_to_env.sh
TZUP-291 abstracted the image name to be used in building pipeline task as a CI/CD variable