-
Bug
-
Resolution: Fixed
-
Minor
-
Jenkins v2.32.2 running on Linux RHEL sever.
Dimensions-plugin 0.8.13
This started happening after our upgrade to Jenkins v2.32.2. The Dimensions plugin version used both before and after the upgrade is the same.
[DIMENSIONS] Checking out project "AIT:2017JUNDIIB"...
[DIMENSIONS] Checking out directory 'MessageBroker/EG'...
[DIMENSIONS] (Note: Dimensions command output was -
[DIMENSIONS] SUCCESS: 134 operations succeeded, 0 failed.
[DIMENSIONS] Operation completed
[DIMENSIONS] Operation completed
[DIMENSIONS] )
*[DIMENSIONS] Calculating changes for directory 'MessageBroker/EG'...
java.io.IOException: Failed to parse changelog*
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1728)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:404)
Caused by: java.lang.UnsupportedOperationException: getAffectedFiles() is not implemented by this SCM
at hudson.scm.ChangeLogSet$Entry.getAffectedFiles(ChangeLogSet.java:242)
at com.hp.application.automation.tools.octane.model.processors.scm.GenericSCMProcessor.buildScmCommits(GenericSCMProcessor.java:80)
at com.hp.application.automation.tools.octane.model.processors.scm.GenericSCMProcessor.getSCMData(GenericSCMProcessor.java:54)
at com.hp.application.automation.tools.octane.events.SCMListenerImpl.createSCMData(SCMListenerImpl.java:103)
at com.hp.application.automation.tools.octane.events.SCMListenerImpl.onChangeLogParsed(SCMListenerImpl.java:71)
at hudson.model.listeners.SCMListener.onChangeLogParsed(SCMListener.java:120)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:620)
[JENKINS-44583] Failed to parse changelog error using Dimensions
Code changed in jenkins
User: David Conneely
Path:
README.md
pom.xml
src/main/java/hudson/plugins/dimensionsscm/DimensionsAPI.java
src/main/java/hudson/plugins/dimensionsscm/DimensionsChangeSet.java
src/main/resources/hudson/plugins/dimensionsscm/ArtifactUploader/config.jelly
src/main/resources/hudson/plugins/dimensionsscm/ArtifactUploader/global.jelly
src/main/resources/hudson/plugins/dimensionsscm/DimensionsBuildNotifier/config.jelly
src/main/resources/hudson/plugins/dimensionsscm/DimensionsBuilder/config.jelly
src/main/resources/hudson/plugins/dimensionsscm/DimensionsChangeSetList/digest.jelly
src/main/resources/hudson/plugins/dimensionsscm/DimensionsChangeSetList/index.jelly
src/main/resources/hudson/plugins/dimensionsscm/DimensionsSCM/config.jelly
src/main/resources/hudson/plugins/dimensionsscm/DimensionsSCM/global.jelly
src/main/resources/index.jelly
src/main/webapp/canupdate.html
src/test/java/hudson/plugins/dimensionsscm/DimensionsChangeSetTest.java
http://jenkins-ci.org/commit/dimensionsscm-plugin/04338954272a19a9007d4bd8e02ee192917d7f49
Log:
updated to 2.x plugin POM (checked Jenkins 1.609.3+), initial fix for JENKINS-44583
HI. I'm new to this. Does this mean the issue has been fixed and there is a new version of the dimensonsscm plugin I should start using?
Thank you.
Hi Jed, No problem! All the automated notifications can be a tad confusing, I agree... What this means is that I made a source code change that I think fixes the issue, but I'm still testing it (which is actually going to be an imperfect test because I don't have access to HP ALM Octane).
If you know how, you could pull the source code, build it yourself and provide feedback. But otherwise just wait a while until I am able to do some dev testing of the fix. Then i'll create a new version of the plugin (it will be 0.8.14) and release it - updating this Jira ticket and the wiki when that happens.
Cheers, hope this helps, David.
David Conneely
added a comment - - edited Hi Jed, No problem! All the automated notifications can be a tad confusing, I agree... What this means is that I made a source code change that I think fixes the issue, but I'm still testing it (which is actually going to be an imperfect test because I don't have access to HP ALM Octane).
If you know how, you could pull the source code, build it yourself and provide feedback. But otherwise just wait a while until I am able to do some dev testing of the fix. Then i'll create a new version of the plugin (it will be 0.8.14) and release it - updating this Jira ticket and the wiki when that happens.
Cheers, hope this helps, David. David Conneely
added a comment - Release 0.8.14 now includes the fix in an official release.
Looks like it is caused by some interaction with the HPE ALM Octane CI plugin (or HP Application Automation Tools plugin), rather than upgrade of Jenkins.
See https://github.com/hpsa/hp-application-automation-tools-plugin/blob/master/src/main/java/com/hp/application/automation/tools/octane/model/processors/scm/GenericSCMProcessor.java#L80 which assumes ChangeLogSet.Entry.getAffectFiles() method is implemented but (as explained in Javadoc) it can throw UnsupportedOperationException.
Assigning to investigate how hard it is just to implement the missing method.