Closed osis closed 7 years ago
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/150527129
The labels on this github issue will be updated when the story is started.
@osis I think this has always been an issue. I think the regex needs to be anchored to the beginning of the version, because what is happening is that the regex 1.9.*
matches <anything>1<single-char>9<any number of chars>
. Specifically 1.11.9
matches <1.1>1<.>.9<nothing>
and similar for 1.11.10
- this just hasn't shown up before because we hadn't released these numbers yet.
Pivnet resource could choose to fix this by implicitly anchoring the start and end of regex, but regardless, you could anchor the regex with something like: ^1.11.*$
.
and really, the trailing $
isn't necessary (or useful) if the last element in the regex is .*
.
Didn't know the regex was interpreted that way so that makes sense. Not sure how I got that impression though... Anywho, thanks!!
TL;DR - I think there is an issue with the regex and duplicate numbers in the version.
I am using the Pivnet Resource to pull in versions 1.9.*, 1.10.*, and 1.11.* of Runtime. It looks like the 1.9.* and 1.10.* resources have suddenly pulled in versions 1.11.9, and 1.11.10.
Concourse Config
Concourse Resource Output
I also checked to see whether there had been a change since it pulled an intended version vs the unintended and both showed version 0.31.3 of the Pivnet Resource.