Docs: add overview and use cases for Jenkins integration
What does this MR do?
Docs: add overview and use cases for GitLab's Jenkins integration.
Closes https://gitlab.com/gitlab-org/gitlab-ee/issues/3012
cc/ @axil @bikebilly
Merge request reports
Activity
mentioned in issue #2703 (closed)
mentioned in commit 3a1b9c6a
10 10 using the new 'Jenkins CI' project service instead which is described in this 11 11 document. 12 12 13 The Jenkins integration includes: 13 ## Overview 14 14 15 * Trigger a Jenkins build after push to a repository and/or when a merge request 16 is created 17 * Show build status on Merge Request page, on each commit and on the project 18 home page 15 [Jenkins](https://jenkins.io/) is a great Continuous Integration tool, similar to our built-in 16 [GitLab CI](../ci/README.md). 17 18 GitLab's Jenkins integration allows you to trigger a Jenkins build when you 19 push code to a repository, or when a merge request is created. Additionally, @marcia Is that technically correct? Can the Jenkins integration really differentiate between a MR being created and a branch being created? /cc @ayufan @bikebilly
Not sure about our implementation, but Jenkins can do that and gitlab-branch-source-plugin can definitely do that.
I don't know @markpundsack, I didn't write it, just reworded a little bit.
This is how it was before my change:
The Jenkins integration includes: * Trigger a Jenkins build after push to a repository and/or when a merge request is created * Show build status on Merge Request page, on each commit and on the project home pageLooks like @dblessing wrote it (https://gitlab.com/gitlab-org/gitlab-ee/commit/3e38e8415e1a334e4c1a6921dda480d5d931bcf9#016281a6239dfca3c7dffd8bda9a56ca94fd30f0_6_17), maybe he can help us here? :)
