Gitlab-plugin: Version 1.5.7 of the plugin breaks Pipeline support

Created on 29 Jun 2018 · 10Comments · Source: jenkinsci/gitlab-plugin

It appears that #747 inadvertently broke Pipeline support, and this was released today in version 1.5.7 of the plugin.

gitLabConnection now throws a java.lang.NoSuchMethodError: No such DSL method 'gitLabConnection' found error, and gitlabCommitStatus throws java.lang.IllegalArgumentException: Expected named arguments but got checkout

@stchar please look into this ASAP.

All others, please downgrade to 1.5.6 if you encounter this issue.

Source

omehegan

❤20

Most helpful comment

Released as 1.5.8.

omehegan on 4 Jul 2018

🎉5

All 10 comments

@stchar can you comment on this to confirm you're aware of it? If I don't hear anything today I will probably revert the PR and do another release so we don't have a broken version in the update center. Thanks!

omehegan on 2 Jul 2018

the gitlabCommitStatus signature has changed. it has nothing to do with the old version...
That's not a trivial impact.
Do downgrade indeed. 1.5.6 works with the latest version of gitlab (11.0.2)

CelesteGH on 2 Jul 2018

Same issue for me. It's fixed after downgrade to 1.5.6

jandry on 2 Jul 2018

Needed to downgrade to 1.5.6 too, because declarative pipeline jobs were not working anymore altogether.
I uploaded some more details on pastebin while asking for help on the IRC channel:
Sample Jenkinsfile
Error stacktrace

IOOOTAlan on 2 Jul 2018

Same problem :(

ripper2hl on 3 Jul 2018

I tested the fix in #793 locally, after first reproducing the problem in 1.5.7, and the fix seems to work. I published a snapshot with this fix at http://repo.jenkins-ci.org/snapshots/org/jenkins-ci/plugins/gitlab-plugin/1.5.8-SNAPSHOT/gitlab-plugin-1.5.8-20180703.040227-1.hpi I would recommend that other folks verify this before I merge and release it. Please comment here if you can confirm the problem is fixed.

omehegan on 3 Jul 2018

👍1

@omehegan I deployed the updated snapshot and confirm that declarative pipeline jobs run again with no changes on the Jenkinsfile used.
Will soon test if build status is correctly reported back to gitlab...

IOOOTAlan on 3 Jul 2018

@omehegan using the snapshot, all pipelines seem to run fine again without further changes. Commit status has been reported back to gitlab successfully.