Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 22 Next »

ProjectJenkins jobPurposecronenvironment
ANYservice-env-deploy
  • This is a manual job only
  • Can deploy any service in any environment
  • Deploys the version in platform.yml
noAny





ANYservice-pipeline
  • Run by other jenkins jobs
  • Creates JAR and Docker inages
  • Put them into the registry
noNone/Dev





ESResr
  • This is the main job for esr
  • It is triggered by a push into github
  • It creates the JAR and Docker image by running service-pipeline
  • When FINALTAG is set, it deploys esr-etl into dev
noNone/Dev





ESR-ETLtis-esr-etl
  • This is the main job for esr
  • It is triggered by a push into github
  • It creates the JAR and Docker image by running service-pipeline
  • When FINALTAG is set, it deploys esr-etl into dev
noNone/Dev

tis-esr-parameterized
  • This is for manual run only
  • One runs it to pass a parameter like the date or the type of load needed
  • It does not create any JAR file or docker image
  • It just deploys whatever is in platform.yml into the selected environment
  • One can pass any parameter to the job, unlike service-env-deploy
noAny

tis-esr-etl-param-apc-import
  • This is a cron job in jenkins
  • It runs tis-esr-parameterized with LOAD_TYPE=apc-import
  • 20h00
  • daily
stage

tis-esr-etl-param-applicant-load
  • This is a cron job in jenkins
  • It runs tis-esr-parameterized with LOAD_TYPE=applicant-load
  • 15h00
  • daily
stage

tis-esr-etl-param-applicant-export
  • This is a cron job in jenkins
  • It runs tis-esr-parameterized with LOAD_TYPE=applicant-export
  • 17h00
  • daily
stage

tis-esr-etl-param-notification-export
  • This is a cron job in jenkins
  • It runs tis-esr-parameterized with LOAD_TYPE=notification-export
  • 17h00
  • daily
stage

tis-esr-etl-param-notification-daily-load
  • This is a cron job in jenkins
  • It runs tis-esr-parameterized with LOAD_TYPE=notification-export
  • 02h00
  • daily
stage

esr-etldisabled because tis-esr-etl does the same thing






NDW-ETLndw-etl
  • This is the main job for NDW-ETL
  • It is triggered by a push into github
  • It creates the JAR and Docker image by running service-pipeline
  • When FINALTAG is set, it deploys esr-etl into dev
noNone/Dev

tis-ndw-etl-parameterized
  • This is a cron job in Jenkins
  • It can take a parameter: the environment
  • It will by default run in prod
  • 07h00
  • daily
Prod

chris-tis-ndw
  • Uses jenkinsfile
  • Can run against all our github repositories
  • configured to use tis-ndw-etl github repo



service-pipeline-ndw-etldisabled because this was a poor attempt to change service-pipeline






Generic Uploadtis-generic-upload-parameterized
  • This is for manual run only
  • One runs it to pass a DEBUG parameter which allows one to attach to port 5005TCP
  • It does not create any JAR file or docker image
  • It just deploys whatever is in platform.yml into the selected environment
  • One can pass the debug parameter to the job, unlike service-env-deploy
noAny

tis-generic-upload
  • This is the main job for generic-upload
  • It is triggered by a push into github
  • It creates the JAR and Docker image by running service-pipeline
  • When FINALTAG is set, it deploys generic-upload into dev
noNone/Dev





TCStcs
  • This is the main job for tcs
  • It is triggered by a push into github
  • It creates the JAR and Docker image by running service-pipeline
  • When FINALTAG is set, it deploys generic-upload into dev



tcs-paramameterizeddisabled because this was a poor attempt to change service-pipeline






admins-uiadmins-ui
  • This is the main job for admins-ui
  • It is triggered by a push into TIS-ADMINS-UI github repo
  • It creates the JAR and Docker image by running service-pipeline
  • When FINALTAG is set, it deploys generic-upload into dev



TIS-ADMINS-UI
  • Uses jenkinsfile
  • Can run against all our github repositories
  • configured to use ndw-etl github repo



admins-ui-e2e


admins-ui-uat
  • This is a clone of the main job for admins-ui
  • It used to be triggered by a push into TIS-ADMINS-UI github repo
  • It creates the JAR and Docker image by running service-pipeline
  • When FINALTAG is set, it deploys generic-upload into dev
  • DECISION REQUIRED - last run was on 2018 March 7th



chris-admins-ui
  • this is a different implementation of a pipeline
  • It uses groovy pipeline directly implemented in the GUI
  • It never succeded, last run was on 2018 March 18th
  • Last error: java.lang.NoSuchMethodError: No such DSL method 'post' found among steps
  • DECISION REQUIRED



TIS-ADMINS-UI
  • Uses jenkinsfile
  • Can run against all our github repositories
  • configured to use TIS-ADMINS-UI github repo







referencereference
  • This is the main job for reference
  • It is triggered by a push into TIS-REFERENCE github repo
  • It creates the JAR and Docker image by running service-pipeline
  • When FINALTAG is set, it deploys generic-upload into dev







profileprofile
  • This is the main job for reference
  • It is triggered by a push into TIS-PROFILE github repo
  • It creates the JAR and Docker image by running service-pipeline
  • When FINALTAG is set, it deploys generic-upload into dev



profile-parent
  • This is the main job for reference
  • It is triggered by a push into TIS-PROFILE github repo
  • It creates the JAR and Docker image by running service-pipeline
  • When FINALTAG is set, it deploys generic-upload into dev
  • DUPLICATE ???







assessmentsassessments
  • This is the main job for reference
  • It is triggered by a push into TIS-ASSESSMENTS github repo
  • It creates the JAR and Docker image by running service-pipeline
  • When FINALTAG is set, it deploys generic-upload into dev







auditaudit-logs-backup-dev
  • runs ansible task tasks/audit-logs-backup.yml in dev
  • backs audt logs to azure storage container heetislogsbackup


  • No labels