-
Bug
-
Resolution: Fixed
-
Minor
It seems that the gitlab plugin does not work very well with the jenkins pipeline plugin in jenkins 2.0. If you create a new pipeline job in jenkins you are not able to trigger it from a gitlab web hook since the project has no SCM connection (the scm connection is defined in the pipeline dsl)
WARNING: Error while serving http://<jenkins url>/project/<project-name>
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:320)
...
Caused by: java.lang.IllegalArgumentException: This project does not use git:<project-name>
at com.dabsquared.gitlabjenkins.GitLabPushTrigger$DescriptorImpl.getSourceRepoNameDefault(GitLabPushTrigger.java:894)
at com.dabsquared.gitlabjenkins.GitLabPushTrigger.createActions(GitLabPushTrigger.java:289)
at com.dabsquared.gitlabjenkins.GitLabPushTrigger.onPost(GitLabPushTrigger.java:238)
at com.dabsquared.gitlabjenkins.GitLabWebHook.generatePushBuild(GitLabWebHook.java:378)
at com.dabsquared.gitlabjenkins.GitLabWebHook.generateBuild(GitLabWebHook.java:338)
at com.dabsquared.gitlabjenkins.GitLabWebHook.getDynamic(GitLabWebHook.java:146)
... 71 more
Why is a scm connection required?
