home/gitlabhq
2
0
Fork 0
mirror of https://github.com/wahyd4/gitlabhq.git synced 2026-08-15 15:46:08 +10:00
Code Issues Packages Projects Releases Wiki Activity

Add development info on how to make a CI tool project service.

Browse Source
This commit is contained in:
dosire
2014-05-22 10:16:43 +02:00
parent 7ab468317b
commit a7ca07012c
1 changed files with 18 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/integration/jenkins.md
+18 -2
View File
@@ -37,5 +37,21 @@ Now navigate to GitLab services page and activate Jenkins
![screen](jenkins/gitlab_service.png)
Done! Now when you push to GitLab - it will create build for Jenkins.
And also you will be able to see merge request build statuswith link to Jenkins build.
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.
## Development
An explanation of how this works in case anyone want to improve it or develop this service for another CI tool.
In GitLab there is no database table that lists the commits, these are always read from the repository.
Therefore it is not possible to mark the build status of a commit in GitLab.
Actually we believe this information should be stored in a single place, the CI tool itself.
To show this information in a merge request you make a project service in GitLab.
This project service does a (JSON) query to a url of the CI tool with the SHA1 of the commit.
The project service builds this url and payload based on project service settings and knowlegde of the CI tool.
The response is parsed to give a response in GitLab (success/failed/pending).
All this happens with AJAX requests on the merge request page.
The Jenkins project service code is only available in GitLab EE.
The GitLab CI project service code is available in the GitLab CE codebase.
In GitLab 6.9 there is a small difference between GitLab CE and EE regarding project services, but this should be gone in 7.0.