Bitbucket Branch Source Plugin v2.0.1 SCM API Plugin v2.0.1 is older than required. To fix, install v2.0.2-beta-1 or later.

[ky...@kayak.com]

The available plugins doesn't show a version 2.0.2 of the SCM API Plugin...anyone know how to get that to show up?

[Stephen Connolly]

Please hold... we are working on resolving all the issues in https://issues.jenkins-ci.org/browse/JENKINS-41234 before the 2.0.x versions of these plugins are returned to the update center

On 24 January 2017 at 18:53, <ky...@kayak.com> wrote:

The available plugins doesn't show a version 2.0.2 of the SCM API Plugin...anyone know how to get that to show up?

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/4ed77bbf-efb0-4246-bfa7-bf0e738b9487%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ky...@kayak.com]

Wow.  Good to know.

Now we need a "is it safe to upgrade Jenkins" page somewhere :-)

[Stephen Connolly]

From my perspective there really were 3 issues that could be seen as release blockers (the build storm ones) and there were mitigations that could have been used to address the build storm issues, but due to Time Zone issues the decision was taken to pull all versions from the update centre without an opertunity to consult with me.

The other issues are not upgrade blockers but enough people have requested them that they are being addressed at the same time 

Hopefully the releases will be available in the next few days. The SCM API changes are somewhat exceptional from the normal as we had to do something rare in the Jenkins community, intentionally break existing plugins - a result of the bitbucket and GitHub branch source plugins from making invalid assumptions about internal behaviour of SCM API.

Additionally, these invalid assumptions could result in builds reporting as building one revision while actually building another revision (mostly affecting PR-merge builds where the PR has had its target branch changed after initial index)

So we had to fix the issues but that requires a coordinated release of many plugins.

Once 2.0.x is out, it should all be much more stable going forward and we have guidelines for plugin authors to prevent this kind of issue recurring 

--


You received this message because you are subscribed to the Google Groups "Jenkins Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.


To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/af8d4ea9-b1fa-4444-8a7f-95748ebd33f6%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Sent from my phone