diff options
Diffstat (limited to 'doc/integration/jenkins_deprecated.md')
| -rw-r--r-- | doc/integration/jenkins_deprecated.md | 23 |
1 files changed, 11 insertions, 12 deletions
diff --git a/doc/integration/jenkins_deprecated.md b/doc/integration/jenkins_deprecated.md index 63d5ac48765..b5d68e3183f 100644 --- a/doc/integration/jenkins_deprecated.md +++ b/doc/integration/jenkins_deprecated.md @@ -1,30 +1,30 @@ --- -stage: none -group: unassigned -info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers +stage: Create +group: Ecosystem +info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments --- # Jenkins CI (deprecated) service -NOTE: **Note:** +NOTE: In GitLab 8.3, Jenkins integration using the [GitLab Hook Plugin](https://wiki.jenkins.io/display/JENKINS/GitLab+Hook+Plugin) was deprecated in favor of the [GitLab Plugin](https://wiki.jenkins.io/display/JENKINS/GitLab+Plugin). Please use documentation for the new [Jenkins CI service](jenkins.md). -NOTE: **Note:** +NOTE: This service was [removed in v13.0](https://gitlab.com/gitlab-org/gitlab/-/issues/1600) Integration includes: -- Trigger Jenkins build after push to repo +- Trigger Jenkins build after push to repository - Show build status on Merge Request page Requirements: - [Jenkins GitLab Hook plugin](https://wiki.jenkins.io/display/JENKINS/GitLab+Hook+Plugin) -- Git clone access for Jenkins from GitLab repo (via SSH key) +- Git clone access for Jenkins from GitLab repository (via SSH key) ## Jenkins @@ -41,7 +41,7 @@ In GitLab, perform the following steps. Jenkins needs read access to the GitLab repository. We already specified a private key to use in Jenkins, now we need to add a public one to the GitLab -project. For that case we will need a Deploy key. Read the documentation on +project. For that case we need a Deploy key. Read the documentation on [how to set up a Deploy key](../ssh/README.md#deploy-keys). ### Jenkins service @@ -50,14 +50,13 @@ Now navigate to GitLab services page and activate Jenkins  -Done! Now when you push to GitLab - it will create a build for Jenkins. -And also you will be able to see merge request build status with a link to the Jenkins build. +Done! Now when you push to GitLab - it creates a build for Jenkins, and you can view the merge request build status with a link to the Jenkins build. ### Multi-project Configuration The GitLab Hook plugin in Jenkins supports the automatic creation of a project -for each feature branch. After configuration GitLab will trigger feature branch -builds and a corresponding project will be created in Jenkins. +for each feature branch. After configuration GitLab triggers feature branch +builds and a corresponding project is created in Jenkins. Configure the GitLab Hook plugin in Jenkins. Go to 'Manage Jenkins' and then 'Configure System'. Find the 'GitLab Web Hook' section and configure as shown below. |