-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sensible version strings #6
Comments
Fix your parser? https://jenkins.io/jep/229 |
It's not my parser, it's a vendor product. Never mind, helpful as ever. |
What vendor would this be? For some “repository”? https://github.com/jenkinsci/lib-version-number/blob/6069936f093629bcf6e3a559dd67bb20a583d056/src/main/java/hudson/util/VersionNumber.java#L36-L53 FTR. There is no limit on the number of version number components, and nonnumeric final components are permitted. Also compliant with Maven (modulo jenkinsci/lib-version-number#6). |
Yes understood. Unfortunately I work for a very large corporate and I'm not permitted to divulge any details. I'll raise it with the internal repo support team. |
Can we have version strings in line with the majority of other plugins, i.e major.minor.patch please?
We have an automated process to pull plugins to an internal on-prem repo and 0.11.2.8.82737cbfa6f5 has broken the version parser.
The text was updated successfully, but these errors were encountered: