Closed esiqveland closed 7 years ago
Hi @esiqveland you should be able to specify a version range from which the latest version will be polled. If that doesn't work, please copy&paste your config and we'll have a look into your issue :)
Ok, so you have to set a lower bound on the versions to include them? Then I will close this issue, but maybe note this in the readme?
As implemented by this plugin the term latest
is equal to the highest available version in the repository.
Let's talk it through by an example. Say you have an artifact and there are multiple versions in the repo including
When you leave the upper & lower bound blank, the plugin will always poll the latest (highest) version. Here, that's version 2.0.
If you want to only use the artifacts with major version 1, you have to set the upper bound to 2.0. This will leave you with the list of
and you're latest (highest) version is 1.3.
Now the lower bound is basically useless I guess, except you want to make sure that the plugin wont use version 1.0 even if version 1.3 was deleted from the repository. Yet I'm not sure if that's even allowed.
Does this answer your question? Do you need another approach / another definition of latest?
Thank you for a very thorough answer! Every build gets a version number with us, so I was just wondering where all the versions went. We used to use the other maven-poller plugin for gocd, which shows the last 10 versions or something when you leave the lower bound blank.
It's ok, I will close this then!
Does this plugin only let you choose latest revision from maven for a material, or did I configure something wrong?