-
v1.4.1
Changelog: * Broken serialization of ParametersAction * Increased required jenkins core version * Tests improvement * Fixed status reporting on merges * Fixed namespace parsing from payload * Building of merges made optional * Capture exception when reading broken configs
-
v1.4.0
Changelog: * Build status publisher * Tag building * Merge requests processing * Added acceptance tests * Removed support for 1.x git plugin * Shrink build cause to single line
-
v1.3.1
Changelog: * Fixed exception when creating template projects * Added Security::impersonate to handle project creation
-
v1.3.0
Changelog: * Template based automatic project creation * Improved branch matching # project match function branches - produce exact matches when configured branches like */master - special handling when configured branch starts with refs/...
-
v1.2.0
Changelog: * global configuration for automatic project per branch creation https://github.com/elvanja/jenkins-gitlab-hook-plugin/pull/44 * trigger the build only for multi configuration project, not it's axis https://github.com/elvanja/jenkins-gitlab-hook-plugin/issues/50 * payload data is auto-filled to job parameters https://github.com/elvanja/jenkins-gitlab-hook-plugin/pull/31 * supporting refspec matching (if refspec present in job configuration) https://github.com/elvanja/jenkins-gitlab-hook-plugin/pull/41 * multiple smc's support `https://github.com/elvanja/jenkins-gitlab-hook-plugin/pull/39 * git 2 support https://github.com/elvanja/jenkins-gitlab-hook-plugin/pull/42 * better error handling, exceptions converted to java RuntimeException https://github.com/elvanja/jenkins-gitlab-hook-plugin/pull/43 * fix for branch specifier that is not of String type, now just skipping such projects instead of raising exception https://issues.jenkins-ci.org/browse/JENKINS-24232 * fix for getting branch name from payload, did not work correctly for tags https://github.com/elvanja/jenkins-gitlab-hook-plugin/pull/45 * 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