[JIRA] (JENKINS-57690) Support more sophisticated versioning

2019-05-26 Thread christopherpiercecoo...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 chris cooney updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57690  
 
 
  Support more sophisticated versioning   
 

  
 
 
 
 

 
Change By: 
 chris cooney  
 

  
 
 
 
 

 
 At the moment, the  ` @Library `  annotation supports the exact tag from a repository. This is great, but simplistic. As a team who are semantically versioning the shared library and regularly pushing out patch and minor versions, the overhead of expecting teams to constantly update their Jenkinsfiles is a little unfair. We want teams to be able to pin to a major version but be able to accept minor or patch version updates.For example, the following syntax should be valid:  ` @Library('library@v0.1. * ') ` . It should find the latest tag matching  ` v0.1.* `    and pull in that version.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199625.155081000.12119.155140129%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-57690) Support more sophisticated versioning

2019-05-26 Thread christopherpiercecoo...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 chris cooney created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57690  
 
 
  Support more sophisticated versioning   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 workflow-cps-global-lib-plugin  
 
 
Created: 
 2019-05-26 16:28  
 
 
Labels: 
 plugins  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 chris cooney  
 

  
 
 
 
 

 
 At the moment, the `@Library` annotation supports the exact tag from a repository. This is great, but simplistic. As a team who are semantically versioning the shared library and regularly pushing out patch and minor versions, the overhead of expecting teams to constantly update their Jenkinsfiles is a little unfair. We want teams to be able to pin to a major version but be able to accept minor or patch version updates. For example, the following syntax should be valid: `@Library('library@v0.1.')`. It should find the latest tag matching `v0.1.` and pull in that version.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment