how-to-deploy.txt

Normally now use the build pipeline 

DEV DEPLOY
1. Goto https://build.tax.service.gov.uk/
2. Search for your service (top-right)
3. Find and check the automated build (build history, clicky build number, copy version number)(maybe build now)
4. # Goto https://ci-dev.tax.service.gov.uk
5. # Search for create-a-release-slug
6. # Build with parameters using service name and copied version number from 3
7. Goto http://orchestrator.tools.development.tax.service.gov.uk/
8. Search for deploy-microservice and build with parameters using same version number (6)
9. Check your service here https://www.development.tax.service.gov.uk/<service-name>

QA/STAGING DEPLOY
1. Goto https://ci-open.tax.service.gov.uk
2. Search for your service (top-right)
3. Find and check the automated build (build history, clicky build number, copy version number)
4. Goto https://ci-open.tax.service.gov.uk/
5. Search for create-a-release
6. Build with parameters using service name and copied version number from 3
7. Take new version number from build history
8. Goto https://ci-build.tax.service.gov.uk/
9. Search for create-a-release-slug
10. Build with parameters using version number copied in 7
11. Goto https://orchestrator.tools.qa.tax.service.gov.uk/
12. Search for deploy-microservice
13. Build with parameters using version number copied in 7
14. Optionally repeat on 11 to 13 replacing qa with staging/production in the domain

Troubleshooting
- you need app configs for each environment(dev, qa, staging, prod), which override app-config-base
- shuttering is another jenkins service
- the regime may need to be added by ETMP (e.g. ZSDL) for enrollment lookups to work