Enables Gitlab web hooks to be used to trigger SMC polling on Gitlab projects

Why?

For Gitlab there is an existing solution that might work for you.
You can just use the notifyCommit hook on Git plugin like this:

http://your-jenkins-server/git/notifyCommit?url=<URL of the Git repository for the Gitlab project>

But, with a large number of projects that are mostly polling (no hooks), the project might actually be built with a great delay (5 to 20 minutes).
You can find more details about notifyCommit and this issue here.

That is where this plugin comes in.
It gives you the option to use build_now or notify_commit hook, whichever suits your needs better.

Version history

Open issues

Version 1.4.2 (Apr 2016)

• Full support recent GitLab 8.x releases
• Support for GitLab 8.1 commit statuses
• JENKINS-33836, remove merge request projects even when merged branches triggering is disabled
• JENKINS-33252, skip reporting if gitlab url/token not configured
• JENKINS-29317, implemented endpoint for triggering a specific jenkins project
• JENKINS-30322, report on job log about communications through gitlab API
• JENKINS-28808, fixed Multiple SCMs projects
• Avoid tag building projects to be elected as candidates to automatically create projects
• Improved acceptance tests & documentation

Version 1.4.1.1 (Jan 2016)

• JENKINS-28327, uncaptured exception on malformed congiguration file
• JENKINS-28452, configurable triggering for projects with pre-build merges
• Fixed parameter serialization for tag builds

Version 1.4.0 (May 2015)

• JENKINS-23992, HTML on build reason
• JENKINS-25267, building merge request objects
• JENKINS-27101, undefined method isOlderThan on automatic project creation

Version 1.3.1 (Feb 27 2015)

• JENKINS-27101, exception happens when creating a project from a template
• Issue #56, elevated privileges required for automatic project creation

Version 1.3.0 (Feb 19 2015)

• Template based automatic project creation
• Improved branch matching. Mainly allow exact matches for */master and allow branch specifications starting with refs/

Version 1.2.1 (Feb 3 2015)

• Issue #3 allowing also choice parameter type for branch name parameter

Version 1.2.0 (Jan 19 2015)

• Issue #44 global configuration for automatic project per branch creation
• Issue #50 trigger the build only for multi configuration project, not it's axis
• Issue #31 payload data is auto-filled to job parameters
• Issue #41 supporting refspec matching (if refspec present in job configuration)
• Issue #39 multiple smc's support
• Issue #42 git 2 support
• Issue #43 better error handling, exceptions converted to java RuntimeException
• #JENKINS-24232 fix for branch specifier that is not of String type, now just skipping such projects instead of raising exception
• Issue #45 fix for getting branch name from payload, did not work correctly for tags
• fix for invalid or empty payload, returns the actual payload sent and a more meaningful description
• catching invalid route, displaying known routes and link to wiki
• improved logging for request details, payload, matching projects
• displaying stack trace on exception, nicely formatted for api response or in log

Version 1.1.0 (Jul 13 2014)

• Issue #30 supporting crumb exclusion
• Issue #26 automatic detection and filling of parameters from payload
• RSpec 3.0 compliance