diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-12-01 12:09:49 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-12-01 12:09:49 +0300 |
| commit | 17a47c3e305567151191ce166702bd4e35e62a7b (patch) | |
| tree | 782c7a8ff75abc7f95b6801c39397c843ce6adf3 /doc/integration | |
| parent | 916bb1bb577b64ec769b4c081c4f861a2f47322f (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/integration')
| -rw-r--r-- | doc/integration/jenkins.md | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/integration/jenkins.md b/doc/integration/jenkins.md index b90ae3c3b79..ed173fcb298 100644 --- a/doc/integration/jenkins.md +++ b/doc/integration/jenkins.md @@ -18,6 +18,12 @@ You should use a Jenkins integration with GitLab when: - You're invested in [Jenkins plugins](https://plugins.jenkins.io/) and choose to keep using Jenkins to build your apps. +This integration can trigger a Jenkins build when a change is pushed to GitLab. + +You cannot use this integration to trigger GitLab CI/CD pipelines from Jenkins. Instead, +use the [pipeline triggers API endpoint](../api/pipeline_triggers.md) in a Jenkins job, +authenticated with a [pipeline trigger token](../ci/triggers/index.md#create-a-pipeline-trigger-token). + After you have configured a Jenkins integration, you trigger a build in Jenkins when you push code to your repository or create a merge request in GitLab. The Jenkins pipeline status displays on merge request widgets and the GitLab |