[JIRA] (JENKINS-49505) workflow-{cps,job,multibranch,support} require step-api 2.13, although 2.14 was released 3 months ago

2018-02-12 Thread christian.wans...@openknowledge.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Wansart commented on  JENKINS-49505  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: workflow-{cps,job,multibranch,support} require step-api 2.13, although 2.14 was released 3 months ago   
 

  
 
 
 
 

 
 Thanks, I'll try. If it breaks try to install the old versions. I was a bit confused that the security updates of the named above plugins are newer than then its dependency causing the warning.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-49505) workflow-{cps,job,multibranch,support} require step-api 2.13, although 2.14 was released 3 months ago

2018-02-12 Thread christian.wans...@openknowledge.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christian Wansart created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49505  
 
 
  workflow-{cps,job,multibranch,support} require step-api 2.13, although 2.14 was released 3 months ago   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 workflow-cps-plugin, workflow-job-plugin, workflow-multibranch-plugin, workflow-support-plugin  
 
 
Created: 
 2018-02-12 13:10  
 
 
Labels: 
 plugin pipeline  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Christian Wansart  
 

  
 
 
 
 

 
 Jenkins informs me about security updates for workflow-{cps,job,multibranch,support} but I get a warning in the Update Center for each of them: 

Warning: This plugin requires dependent plugins be upgraded and at least one of these dependent plugins claims to use a different settings format than the installed version. Jobs using that plugin may need to be reconfigured, and/or you may not be able to cleanly revert to the prior version without manually restoring old settings. Consult the plugin release notes for details.
 I checked the dependencies and as it seems, those four plugins require workflow-step-api in version 2.13, but 2.14 was released 3 months ago, according to its plugin site.