Configure CI/CD pipelines
After creating your GitLab group and repositories, configure CI/CD pipelines to automate build, test, and deployment workflows.
SHIP-HATS provides pipeline templates that help you quickly set up standard CI/CD workflows for your project.
Complete these steps in GitLab. See Log in to GitLab.
Steps
Choose a CI approach
Decide the continuous integration (CI) approach for your project.
SHIP-HATS provides pipeline templates that implement recommended CI practices.
Refer to:
Create the pipeline configuration
Copy the E2E template into your repository.
Update the required project variables.
Commit the
.gitlab-ci.ymlfile to your repository.
This configuration defines the pipeline stages and jobs executed when code changes are pushed.
Customise the pipeline (Optional)
If the E2E template does not meet your requirements, you can modify the pipeline using modular templates.
Refer to:
- Common templates (Modular)
- Reference pipelines
- Sample pipeline for an example implementation.
Apply compliance framework
Apply the SHIP-HATS GitLab compliance framework to enforce security and governance requirements.
Configure deployments
Decide the continuous delivery (CD) approach for your application.
Ensure the pipeline can successfully deploy to:
- non-production environments
- production environments
Pipeline execution environment
Pipelines run on GitLab runners. SHIP-HATS provides shared runners for executing pipelines. Agencies that require dedicated execution environments can host and manage their own runners, known as agency-hosted GitLab runners.
If your project requires dedicated execution environments, see:
Next steps
After configuring CI/CD pipelines, you can monitor delivery performance using:
