---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-service-management
Release :
- australia
ft:locale :
- en-US
ft:publication_title :
- Australia IT Service Management
ft:clusterId :
- itsm
bundleId :
- itsm
workflow :
- Technology
---
# Model a GitLab basic CI pipeline in DevOps
# Model a GitLab basic CI pipeline in DevOps {#ariaid-title1}
* Release version: Australia
*
* Updated March 12, 2026
*
*  3 minutes to read
Model a GitLab basic CI pipeline by mapping the pipeline to an app, and mapping DevOps pipeline steps to GitLab pipeline jobs.
## Before you begin
Role required: sn_devops.admin
## Procedure
1. Map your pipeline to an app.
1. Navigate to DevOpsApps \& PipelinesApps and open the application record to associate with the pipeline.
2. In the Pipelines related list, click Edit... to select a pipeline to associate with the app, or click New to create the pipeline.
Note:
While associating a pipeline with an app, the pipeline steps are also fetched during import.
For a new pipeline, fill in the Orchestration pipeline field using the group name, subgroup name (if applicable), and project name as specified in GitLab.
For example, My Group/My SubGroup/My Project.
If a project is not under a group, simply specify My Project.
3. Click Submit.
2. Open the pipeline record again and create DevOps steps to map to each GitLab pipeline job so an orchestration task can be created.
Steps can be created in one of the following ways.
* Automatically create and map pipeline steps in DevOps by running your GitLab pipeline.
Pipeline steps are automatically created, mapped, and associated when DevOps receives step notifications from your GitLab pipeline during the run.
* Manually create and map each pipeline step to a GitLab pipeline job.
In the Steps related list, click New to create a DevOps step for each GitLab pipeline job (Orchestration stage field).
Note:
The Orchestration stage field value of each step is case-sensitive and must match the original name of the corresponding GitLab pipeline job.
|-|-|
| Name | Name of the pipeline step. |
| Pipeline | Pipeline in which the step is configured. |
| Type | Pipeline step type. * Build and Test * Test * Deploy * Deploy and Test * Manual * Prod Deploy {#model-gitlab-pipeline-dev-ops__ul_w1m_crk_wmb} |
| Order | Order in which the steps are run. Note: The step order determines the order of the cards in the [Pipeline UI](https://www.servicenow.com/docs/yaj2dQuVNc7UKuimbU8Fug "Use the Pipeline UI to visualize interactions and results across a pipeline execution. This graphical view shows pipeline step progression and other details for each pipeline."). The order of the cards in the Pipeline UI is by task execution. |
| Orchestration stage | GitLab pipeline job name (case-sensitive). Note: For step association with GitLab CI pipeline jobs, the Orchestration stage field must be configured. |
| Business service | Configuration service that applies to the step. |
[ ]
{#model-gitlab-pipeline-dev-ops__table_v1m_crk_wmb}
Once orchestration tasks are created, associate each orchestration task in the Orchestration Tasks related list with a DevOps pipeline step.
3. **Optional:** Select the Change control check box in a step to enable [change acceleration](https://www.servicenow.com/docs/1IOGCXHTnX02RprvPaB2wg "Enable the change acceleration feature of DevOps Change Velocity for automatic change request creation in your pipeline, and use change approval flows and policies to automate approval under certain conditions.") and the corresponding configuration fields.
Note:
The [Change Management](https://www.servicenow.com/docs/uBHHMv4DsgI5VM1mPhonMg "The ServiceNow Change Management application provides a systematic approach to control the life cycle of all changes, facilitating beneficial changes to be made with minimum disruption to IT services.") feature must be installed for change acceleration.
|-|-|
| Change receipt | Select to enable change receipt for the step so the pipeline doesn't pause when a change request is created. All pipeline data is included in the change, but approval is not required for the pipeline to proceed. |
| Change approval group | Approval group for the change request. The change approval group becomes the Assignment group in the DevOps change request. Note: Ensure that the selected group has members and a group manager so approver field is not empty. |
| Change type | Change request type to create. * Normal (default) * Standard * Emergency {#model-gitlab-pipeline-dev-ops__ul_zrc_xdf_llb} |
| Change model | Change model for the change request. For more information, see [DevOps change models](https://www.servicenow.com/docs/kYawifgINsRlYqcbPCDx_A "DevOps Change Velocity enables you to use fit-for-purpose change models that allow better flexibility in defining change models or processes to reflect modern development practices."). |
| Template Note: This field is shown only when Change type is Normal or Emergency. | List of templates to use to auto populate fields for Normal or Emergency change requests. Select a template or create a new one. |
| Standard change template Note: This field is shown only when Change type is Standard. | List of standard change templates to use for Standard change requests. Note: This field is required for Standard change type. |
| Change controlled branches | (Multibranch only) Comma-separated list of branches under change control. Wildcards are supported. |
[ ]
{#model-gitlab-pipeline-dev-ops__table_xm1_tdf_llb}
You can set up change control in GitLab for manual GitLab jobs.
Note:
A pipeline must be run and completed at least once before enabling change control.
## What to do next
[Change acceleration in GitLab](https://www.servicenow.com/docs/86vnXC6V4GS4G6pkyCalQg "Change acceleration is supported in DevOps Change Velocity for GitLab jobs.")
*[\>]: and then