Deploy and validate your first build
Use this checklist to validate that your first deployment is healthy before you move on to Path to Live.
Check the deployment landed in the expected environment
Once your pull request has built successfully in Jenkins:
- Confirm the application deployed to the correct non-production target, usually preview or AAT.
- Check the values file overrides used for that environment, as described in Helm chart.
- Confirm the release includes the correct image tag and that the associated Kubernetes resources are present in the cluster.
Check the app is reachable
- Use the ingress host created for the environment and confirm the application responds over HTTPS.
- Check the expected route or homepage loads without a 500 error.
- Confirm any login flow or required startup checks for the service are working as expected.
Check health and readiness signals
Confirm the app is passing the health checks used by the platform. In most cases this means:
- the application responds to the expected health endpoint,
- the service is ready to receive traffic,
- the application does not crash or restart repeatedly after startup.
For production readiness guidance, see Health probes.
Check the supporting platform config
The earlier setup steps are part of the deployment, so verify the following are all healthy:
- the relevant infrastructure has been provisioned without errors,
- the expected secret values are available from Key Vault,
- the certificate and custom domain are valid,
- the public DNS record is present and resolving correctly,
- any Front Door or load balancer rules are pointing at the correct backend.
If something is wrong
Check the pipeline logs first, then review the application logs and the platform configuration for the environment. If you still cannot resolve it, see Troubleshooting or ask in #platops-help.
Sign-off before moving on
Do not move to Path to Live until the application is reachable, healthy, and the supporting configuration for DNS, TLS, secrets, and infrastructure is working in the non-production environment.
Next step in Creating a New Component: Path to Live