Jenkins Pipelines

Maven projects currently has two types of structures, refer below example projects.

https://github.com/Health-Education-England/TIS-REFERENCE (<servicename>-api, <servicename>-client, <servicename>-service, <servicename>-ui)

Node project - https://github.com/Health-Education-England/TIS-COMMON-COMPONENTS

Npm project - https://github.com/Health-Education-England/TIS-ADMINS-UI

All of the above project types have their own jenkins project which will get built on github push to the master branch and on sucess trigger the same service pipeline https://build.tis.nhs.uk/jenkins/job/service-pipeline/ with the exception of admins-ui project which uses https://build.tis.nhs.uk/jenkins/job/admins-ui-pipeline/ and will be merged into main pipeline once we start using the master branch.

Example of the entire flow.

https://build.tis.nhs.uk/reports/service-registry (to know the versions deployed on each environment)