Checks and a build after the push
CI stands for continuous integration. Code changes are brought together and checked automatically. The pipeline runs the configured tests and checks, then builds a runnable application from the code in the repository. A successful build tells you those steps passed. You still need to open the application to judge whether the new form message makes sense.
On MainPath, a push to main starts the pipeline. For a browser application, its stages test the code, calculate a version, build a Docker image and publish the application to dev.
Delivery leaves room for approval
CD can mean continuous delivery or continuous deployment. Continuous delivery prepares a checked version for publication and can leave the final approval to a person. Continuous deployment also takes the step into production automatically.
MainPath uses a manual job for production. After checking the change on dev, you open the corresponding pipeline and start its production job with the play button. Production receives the same build you checked on dev. A successful build alone does not update production.
Find the job that failed
Each stage depends on the ones before it. If a job fails, the pipeline stops at that point. In GitLab, open CI/CD → Pipelines, select the affected run and open the failed job’s log. That gives you a starting point for investigating a failing test or a build error.
MainPath maintains the generated .gitlab-ci.yml. Do not edit that file to fix a pipeline error; discuss any additional automation with support.
Release the version you checked
What are pipelines explains the stages, logs and manual jobs. For the contact form correction, the workflow is to find the pipeline for the relevant commit, check the form on dev and then release that version to production.