Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Blocker
-
Resolution: Won't Fix
-
Component/s: delivery-pipeline-plugin
-
Labels:
-
Similar Issues:
Description
Jenkins version: 2.60.1
After upgrading the delivery-pipeline-plugin from 1.0.3 to 1.0.4, all of my pipeline views disappeared and the option to create a new delivery pipeline is missing.
Attachments
Activity
FWIW I have removed the broken 1.0.4 release from the update sites. The rest is up to the maintainers.
Apologies for the issues you've faced and the slow response on this issue. I've been away so I have not had any possibility to look into this issue just yet. I did not encounter this issue before the release (all tests passed) so I can unfortunately not give any more information before actually looking into to it.
Tommy Tynjä
added a comment - Apologies for the issues you've faced and the slow response on this issue. I've been away so I have not had any possibility to look into this issue just yet. I did not encounter this issue before the release (all tests passed) so I can unfortunately not give any more information before actually looking into to it. I was not able to reproduce this on 1.642.3, which is the minimum Jenkins version that the plugin supports and what all tests are run against in CI, which is why this was not discovered before release of 1.0.4. I was able to reproduce the behavior on 2.60.1.
The logs display the following (and only errors)
Sep 13, 2017 7:47:04 PM hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error
INFO: Failed to instantiate optional component se.diabol.jenkins.pipeline.trigger.BPPManualTriggerResolver; skipping
Sep 13, 2017 7:47:10 PM hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error
INFO: Failed to instantiate optional component se.diabol.jenkins.pipeline.domain.status.promotion.PromotionStatusProvider; skipping
This issue probably occurred due to failure in the infrastructure. It seems like the 1.0.4 worked for some users. Will issue a new release of the plugin which hopefully will be packaged and distributed correctly as expected.
Tommy Tynjä
added a comment - - edited I was not able to reproduce this on 1.642.3, which is the minimum Jenkins version that the plugin supports and what all tests are run against in CI, which is why this was not discovered before release of 1.0.4. I was able to reproduce the behavior on 2.60.1.
The logs display the following (and only errors)
Sep 13, 2017 7:47:04 PM hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error
INFO: Failed to instantiate optional component se.diabol.jenkins.pipeline.trigger.BPPManualTriggerResolver; skipping
Sep 13, 2017 7:47:10 PM hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error
INFO: Failed to instantiate optional component se.diabol.jenkins.pipeline.domain.status.promotion.PromotionStatusProvider; skipping
This issue probably occurred due to failure in the infrastructure. It seems like the 1.0.4 worked for some users. Will issue a new release of the plugin which hopefully will be packaged and distributed correctly as expected.
We will not attempt to re-release 1.0.4. Users are encouraged to upgrade to 1.0.5 instead to take advantage of the additions added in 1.0.4. Users on 1.0.3 or earlier wishing to upgrade should upgrade to straight 1.0.5, avoiding the 1.0.4 version.
Tommy Tynjä
added a comment - We will not attempt to re-release 1.0.4. Users are encouraged to upgrade to 1.0.5 instead to take advantage of the additions added in 1.0.4. Users on 1.0.3 or earlier wishing to upgrade should upgrade to straight 1.0.5, avoiding the 1.0.4 version.
Code changed in jenkins
User: Daniel Beck
Path:
src/main/resources/artifact-ignores.properties
http://jenkins-ci.org/commit/backend-update-center2/52c9e748e5cb639ccef85f8961219abc3f186194
Log:
Merge pull request #163 from daniel-beck/
JENKINS-46130JENKINS-46130Remove delivery-pipeline-plugin-1.0.4Compare: https://github.com/jenkins-infra/backend-update-center2/compare/e3a60955f5df...52c9e748e5cb