Owen Mehegan

@timols from reviewing the description of your plugin, my impression is that it only triggers on merge request events, and upon completion just comments on the MR. Are there any...

@timols https://wiki.jenkins-ci.org/display/JENKINS/Deprecating+a+Plugin has the steps to deprecate a plugin. It would remove it form the Update Center, so people wouldn't be able to install it anymore. That might be more...

@tomgoto I don't understand that comment. The gitlab-plugin does not handle cloning the repo, it only handles triggering the job based on the webhook from GitLab. The regular Git plugin...

@tomasbjerre that's incorrect. Gitlab-plugin is triggered by GitLab webhooks, and can be used with either CE or EE.

@AntoineConffx no, just have not had time to look at it yet.

@AntoineConffx can you please attach the two config.xml files for your jobs? It seems that one job does not think there is any git repo configured or any git checkout...

@AntoineConffx sorry for the late reply. It is a bit hard for me to parse your Pipeline code, so I can't be sure of what is going on here. For...

I can confirm this. The full stack trace is: ``` Jul 24, 2018 4:05:04 PM org.jenkinsci.plugins.pipeline.modeldefinition.generator.DirectiveGenerator doGenerateDirective WARNING: failed to render {"triggers": {"triggerOnPush": true, "triggerOnMergeRequest": true, "triggerOnAcceptedMergeRequest": false, "triggerOnClosedMergeRequest": false,...

@raghur sorry that this is broken, it may not get fixed quickly... but the README has examples of how to configure jobs using Declarative Pipeline, hopefully that will be enough...

@abayer are we doing something obviously wrong here? I only ask because I believe the regular Snippet Generator works fine for the plugin's steps, it seems only the Declarative generator...