--latest ignores whether the plugin is actually available or not

If I want to resolve the latest dependencies for my Jenkins plugins I often run into a scenario where a plugin is in the process of being bumped to a newer version (by the maintainer), and this is reflected on the jenkins update center as a new directory, however the actual jpi hasn’t been uploaded yet so it fails to download. This is troublesome as if I test that the plugins are available in a test environment before rolling to production, there could be a plugin version bump in progress that causes a failure in the time between testing in the test environment and moving it to production.

Perhaps a --latest-available flag that checks if there is a jpi available and if not rolls to the previous release of a plugin would avoid this? To play devils advocate, I can’t see why someone would want this behaviour using --latest in the first place.

[EcHoOfInSaNiTy]

@timja would your recommendation be to pin plugin versions in the YAML file until this is resolved to improve reliability?

Yes

I’ve opened up a PR to update the README here as I think this is valuable information for anyone looking to use this.

[timja]

Fixed in https://issues.jenkins-ci.org/browse/INFRA-160