[JIRA] (JENKINS-38129) pipelines stopped working after update to 2.22 must specify $class with an implementation
Title: Message Title Bram Verhaegh closed an issue as Fixed This appeared to be to be syntax issue, that didn't work after latest updates. Jenkins / JENKINS-38129 pipelines stopped working after update to 2.22 must specify $class with an implementation Change By: Bram Verhaegh Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-38129) pipelines stopped working after update to 2.22 must specify $class with an implementation
Title: Message Title Bram Verhaegh commented on JENKINS-38129 Re: pipelines stopped working after update to 2.22 must specify $class with an implementation It apears there is no alternative yet, but the properties properties is wrong with the latest plugin updates so properties: [[$class: 'GitLabConnectionProperty', gitLabConnection: 'gitlab']] works now. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38129) pipelines stopped working after update to 2.22 must specify $class with an implementation
Title: Message Title Bram Verhaegh commented on JENKINS-38129 Re: pipelines stopped working after update to 2.22 must specify $class with an implementation Thanks it gives me some direction where to look, so this is a gitlab specific issue due to that the $class does not work in this case. what is the alternative for properties properties: [[$class: 'GitLabConnectionProperty', gitLabConnection: 'gitlab']] Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38129) pipelines stopped working after update to 2.22 must specify $class with an implementation
Title: Message Title Bram Verhaegh updated an issue Jenkins / JENKINS-38129 pipelines stopped working after update to 2.22 must specify $class with an implementation Change By: Bram Verhaegh Summary: pipelines stopped working after update to 2.22 must specify $class with an implementation Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38129) pipelines stopped working after update to 2.22
Title: Message Title Bram Verhaegh updated an issue Jenkins / JENKINS-38129 pipelines stopped working after update to 2.22 Change By: Bram Verhaegh Environment: ubuntu 14.04 LTS, Jenkins 2.22, latest gitlab , pipelinescripts are at latest version Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38129) pipelines stopped working after update to 2.22
Title: Message Title Bram Verhaegh updated an issue Jenkins / JENKINS-38129 pipelines stopped working after update to 2.22 Change By: Bram Verhaegh Environment: ubuntu 14.04 LTS, Jenkins 2.22, latest gitlab pipelinescripts are at latest version Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38129) pipelines stopped working after update to 2.22
Title: Message Title Justin Rainwater commented on JENKINS-38129 Re: pipelines stopped working after update to 2.22 I found this bug by searching online for the error message. I was able to resolve it by using the pipeline syntax snippet generator, to change all of my properties away from the old $class style. However I see from Jenkinsfile that the gitlab parameter is the only property you have using $class and I dont see gitlab as an available parameter in the snippet generator so maybe that won't help in your case. Either way I think a more accurate description of this issue would be gitlab specific rather than just "pipelines stopped working" Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38129) pipelines stopped working after update to 2.22
Title: Message Title Justin Rainwater edited a comment on JENKINS-38129 Re: pipelines stopped working after update to 2.22 I found this bug by searching online for the error message. I was able to resolve it by using the pipeline syntax snippet generator, to change all of my properties away from the old $class style. However I see from your Jenkinsfile that the gitlab parameter is the only property you have using $class and I dont see gitlab as an available parameter in the snippet generator so maybe that won't help in your case.Either way I think a more accurate description of this issue would be gitlab specific rather than just "pipelines stopped working" Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38129) pipelines stopped working after update to 2.22
Title: Message Title Bram Verhaegh updated an issue Jenkins / JENKINS-38129 pipelines stopped working after update to 2.22 Change By: Bram Verhaegh Summary: pipeline scripts pipelines stopped working after update to 2.22 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
