[JIRA] (JENKINS-38129) pipelines stopped working after update to 2.22 must specify $class with an implementation

2016-09-13 Thread b...@beech.it (JIRA)
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

2016-09-13 Thread b...@beech.it (JIRA)
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

2016-09-13 Thread b...@beech.it (JIRA)
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

2016-09-12 Thread b...@beech.it (JIRA)
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.