Use a template¶
⏳ Quick use
- Go to the R2Devops public catalog and search for job templates you want.
- Click on the template card and copy past the "Quick use" code in your gitlab-ci.yml file.
- You can now run your pipeline 🎉
Follows these steps to setup your CI/CD pipeline in less than 5 minutes!
If you haven't yet a
.gitlab-ci.ymlfile in the root on your repository: you can create it and use the following list of stages:
stages: - build - tests - provision - review - release - deploy - others
You can check the stages section to get more information about this list or if you already have a configuration with different stages.
Select the job templates you want in the job templates section and append their URL in the
includelist of your
include: - remote: 'https://api.r2devops.io/job/r/<path>@<version>.yaml' - remote: 'https://api.r2devops.io/job/r/<path>@<version>.yaml' - ...
The job templates can be customized 👉 check the job templates customization section.
Everything is ready! You can now benefit the full power of a CI/CD pipeline 🎉🚀
You can also combine job's templates and your own jobs in your
🤓 Pipeline examples¶
Several examples of projects using R2Devops hub:
An example of a full
.gitlab-ci.ymlconfiguration using job templates from the hub 👇
Job templates used in the example
- Plug-and-play set of job templates from the hub to automatically build, test and deploy static documentation website:
- Plug-and-play set of jobs from the hub to automatically build, push and test docker images:
- A custom manual job
stages: - build - tests - provision - review - release - deploy - others # Jobs from r2devops.io (they don't need any configuration in standard cases) include: - remote: 'https://email@example.com' - remote: 'https://firstname.lastname@example.org' - remote: 'https://email@example.com' - remote: 'https://firstname.lastname@example.org' - remote: 'https://email@example.com' # Locally configured job template unit_tests: image: python:3.9-alpine stage: tests before_script: - pip install pipenv && pipenv --bare install --dev script: - make test
By default, each job templates from the hub is a part of on these stages:
- 🧱 Build: building and packaging of the software
- 🔎 Tests: testing your repository files with dynamic and static tests
- 🛠 Provision: preparation of the software infrastructure
- 👌 Review: deployment of the software in an isolated review environment
- 🏷 Release: releasing and tagging of the software
- 🚀 Deploy: deployment of the software on environments
- 🦄 Others: all other magic jobs not included in previous stages
This is an efficient and simple workflow. Nevertheless, if you want to use your own custom stage list: you can re-declare yourself the stage of any job template from the hub. Follow the customization section to do it.
To retrieve a template version, choose among following syntaxes:
- To have always the latest version use:
- You can otherwise precise an exact version:
- To use the latest version of minor releases with a precise major:
- Or the latest version of patch releases with a precise major and minor:
🔧 Job templates customization¶
All the job templates from the
r2devops/hub specify a docker image to be run in a docker container.
Each job templates of the hub can be customized. To do it, you have to include the job template URL as usual and, in addition, override the options you want to customize.
This way, you can override all Gitlab job templates parameters. All parameters are described in Gitlab documentation.
For example, if you want to use the trivy_image job template and customize it by:
- Redefining the
securityto fit in your personal stages workflow,
- Set the variable
0.9.1to use this version instead of the default,
- Set the variable
CRITICALto display only CRITICAL issues.
include: - remote: 'https://api.r2devops.io/job/r/gitlab/r2devops/hub/trivy_image.yaml' trivy_image: stage: security variables: TRIVY_VERSION: "0.9.1" TRIVY_SEVERITY: "CRITICAL"
✏️ Use custom stage¶
If you want to use your own stage name, it's possible to do so when including your job template. Example:
stages: - security include: - remote: 'https://api.r2devops.io/job/r/gitlab/r2devops/hub/trivy_image.yaml' trivy_image: stage: security
You may want one of your job template to interact with a container instance (API, database, web server...) to work. GitLab has an option to run a container next to a job template:
To use this option, you must have access to an image of the container you want to run as a service. For example, if you are using our docker_build job template to build an image of your application, and you want to test this image using the nmap job template, just add the following configuration in your
nameoption must contain your image name and tag, or an image name from Docker Hub.
aliasoption permits to the job template to reach your application using a name. This name must be the same that the one specified inside the job template target's variable.
- You may also run some other services, like a database depending on your application needs.
nmap: services: - name: $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA alias: app
🎶 Multiple usage of the same job template in your pipeline¶
If you want to reuse a job template from the hub, for example launching
apiDoc to build 2 API documentations in the same pipeline, you can easily do so with the Hub's job templates using extends GitLab keyword.
stages: - build include: - remote: 'https://api.r2devops.io/job/r/gitlab/r2devops/hub/apidoc/0.2.0.yaml' apidoc: variables: APIDOC_CONFIG_PATH: src/doc/project1/apidoc.json APIDOC_OUTPUT_PATH: website_build/apidoc/project1/ apidoc_project2: extends: apidoc variables: APIDOC_CONFIG_PATH: src/doc/project2/apidoc.json APIDOC_OUTPUT_PATH: website_build/apidoc/project2/
Be aware to have different artifacts path to not overwrite your first artifact by the second one.