Alastair D'Silva please stop recommending people to build from git tags. When people build from a tag they will get an artifact that masquerades as the release version but with a different SHA1. Diagnosing issues with an installation becomes a lot harder when you do not know which are the official releases and which are rebuilds. This can be even more problematic in cases where the plugin maintainer decides to delete the tag and recreate because the release did not deploy. When a plugin maintainer hits that kind of problem they will typically start using mvn release:prepare release:perform -DpushChanges=false while they iterate... if they then forget to delete the first tag and manually push the actual release tag then you can end up in a state where the tag you have built is not the tag of the release code (I do not recommend that pattern for plugin developers, but I have seen it done) When there is a release version as a dependency, the release must have been cut and will therefore be available from the maven repository, e.g. http://repo.jenkins-ci.org/public/org/jenkins-ci/plugins/branch-api/ has the releases for branch-api In any case, all the updates that this depends on have now been published by the jenkins update center. |