Gitlab2jenkins is a simple web application, which makes a proxy between Gitlab and Jenkins CI.
Gitlab2jenkins is a simple web application, which provides a bridge between [GitLab](http://gitlab.org/) and [Jenkins CI](http://jenkins-ci.org/) server.
...
The application exposes API, which looks the same as API used by [GitLab CI](http://gitlab.org/gitlab-ci/) server. However all requests are processed and proxied to Jenkins. This is useful especially when your testing infrastructure is complicated and GitLab CI cannot satisfy your requirements — for instance, multi-host builds, triggering of other tasks, etc.
It is written in Ruby (Sinatra) and is capable of running on OpenShift cloud.
It is written in Ruby (using [Sinatra](http://www.sinatrarb.com/) web micro framework) and is ready to be run on OpenShift cloud.
Requirements
------------
**Demo**, actually used in production:
[Knot DNS - gitlab2jenkins](http://gitlab2jenkins-fcelda.rhcloud.com/projects/1) at CZ.NIC Labs.
OpenShift with Ruby 1.9, MySQL 5.1, and Foreman
## Deployment
Quick start
-----------
### Local deployment
Clone the repository, install required gems, edit the configuration, and start the server:
Open Gitlab2jenkis in web browser, link to the project should be on the main page.
### Configure GitLab to use the proxy
1. In the project settings in GitLab select *Services* and *GitLab CI*.
2. Enable the service by checking the *Activate* checkbox.
3. Set *Token* token a value generated by `add_project.rb` script.
4. Set *Project url* to project page in Gitlab2jenkins. In case of OpenShift, it will be something like `http://<app-name>-<namespace>.rhcloud.com/projects/<project-id>`.
## Troubleshooting
New builds are pulled from Jenkins periodically. If it does not work, try updating the builds manually: