diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-08-11 21:10:06 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-08-11 21:10:06 +0300 |
commit | 7a1895c74ad57da757c02b2675147a5a5e2cfe6d (patch) | |
tree | 7204fd4cdecbf1166f1aebca080994fcb7f290cd /doc/integration/jenkins.md | |
parent | 9dde2726710184f066387d044fce4ae2b3684210 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/integration/jenkins.md')
-rw-r--r-- | doc/integration/jenkins.md | 18 |
1 files changed, 0 insertions, 18 deletions
diff --git a/doc/integration/jenkins.md b/doc/integration/jenkins.md index 002ee35bc59..8fc638db95a 100644 --- a/doc/integration/jenkins.md +++ b/doc/integration/jenkins.md @@ -147,24 +147,6 @@ Configure the GitLab integration with Jenkins. authentication. 1. Click **Test settings and save changes**. GitLab tests the connection to Jenkins. -## Plugin functional overview - -GitLab does not contain a database table listing commits. Commits are always -read from the repository directly. Therefore, it's not possible to retain the -build status of a commit in GitLab. This is overcome by requesting build -information from the integrated CI tool. The CI tool is responsible for creating -and storing build status for Commits and Merge Requests. - -### Steps required to implement a similar integration - -NOTE: **Note:** -All steps are implemented using AJAX requests on the merge request page. - -1. In order to display the build status in a merge request you must create a project service in GitLab. -1. Your project service will do a (JSON) query to a URL of the CI tool with the SHA1 of the commit. -1. The project service builds this URL and payload based on project service settings and knowledge of the CI tool. -1. The response is parsed to give a response in GitLab (success/failed/pending). - ## Troubleshooting ### Error in merge requests - "Could not connect to the CI server" |