[JIRA] (JENKINS-12824) Master does not build due to version bump
[ https://issues.jenkins-ci.org/browse/JENKINS-12824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159233#comment-159233 ] SCM/JIRA link daemon commented on JENKINS-12824: Code changed in jenkins User: James E. Blair Path: gerrit-events/pom.xml gerrithudsontrigger/pom.xml http://jenkins-ci.org/commit/gerrit-trigger-plugin/ca02b133619005d8f0ee5ee56453eee819307b83 Log: Update build-config dependency versions. Update to 1.2.5-SNAPSHOT. Fixes https://issues.jenkins-ci.org/browse/JENKINS-12824 > Master does not build due to version bump > - > > Key: JENKINS-12824 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12824 > Project: Jenkins > Issue Type: Bug > Components: gerrit-trigger >Reporter: James Blair >Assignee: rsandell > > The recent version bump to build-config 1.2.5-SNAPSHOT is incomplete, so > master doesn't currently build. > The build-config dependency versions in the other subprojects need to be > updated to match. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12824) Master does not build due to version bump
[ https://issues.jenkins-ci.org/browse/JENKINS-12824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159234#comment-159234 ] SCM/JIRA link daemon commented on JENKINS-12824: Code changed in jenkins User: Olivier Lamy Path: gerrit-events/pom.xml gerrithudsontrigger/pom.xml http://jenkins-ci.org/commit/gerrit-trigger-plugin/c86949fb7f002eea2474b2c48aa1cfee836be74d Log: Merge pull request #10 from jeblair/JENKINS-12824 fixed [JENKINS-12824] Update build-config dependency versions. Compare: https://github.com/jenkinsci/gerrit-trigger-plugin/compare/c04a9d6...c86949f > Master does not build due to version bump > - > > Key: JENKINS-12824 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12824 > Project: Jenkins > Issue Type: Bug > Components: gerrit-trigger >Reporter: James Blair >Assignee: rsandell > > The recent version bump to build-config 1.2.5-SNAPSHOT is incomplete, so > master doesn't currently build. > The build-config dependency versions in the other subprojects need to be > updated to match. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12812) dryRun switch failes
[ https://issues.jenkins-ci.org/browse/JENKINS-12812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-12812. Resolution: Fixed > dryRun switch failes > > > Key: JENKINS-12812 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12812 > Project: Jenkins > Issue Type: Bug > Components: m2release > Environment: m2release 0.9.0 >Reporter: domi >Assignee: domi > > triggering a release build with the dryRun checkbox checked failes because > release:perform does not support the dryRun flag. > I have already opened a feature request for the maven-release-plugin: > https://jira.codehaus.org/browse/MRELEASE-736 > ...but I will also work on a fix in the jenkins m2release plugin asap to get > this issue sorted for all versions of the maven-release-plugin -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12812) dryRun switch failes
[ https://issues.jenkins-ci.org/browse/JENKINS-12812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159235#comment-159235 ] SCM/JIRA link daemon commented on JENKINS-12812: Code changed in jenkins User: imod Path: src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseArgumentInterceptorAction.java src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseBuildWrapper.java src/main/resources/org/jvnet/hudson/plugins/m2release/M2ReleaseBuildWrapper/config.jelly src/main/webapp/help-projectConfig-dryRunGoals.html src/test/java/org/jvnet/hudson/plugins/m2release/M2ReleaseActionTest.java http://jenkins-ci.org/commit/m2release-plugin/5dcb1672efae3e4e6acbec057193829b4bad3a65 Log: [FIXED JENKINS-12812] make dryRun goal configurable > dryRun switch failes > > > Key: JENKINS-12812 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12812 > Project: Jenkins > Issue Type: Bug > Components: m2release > Environment: m2release 0.9.0 >Reporter: domi >Assignee: domi > > triggering a release build with the dryRun checkbox checked failes because > release:perform does not support the dryRun flag. > I have already opened a feature request for the maven-release-plugin: > https://jira.codehaus.org/browse/MRELEASE-736 > ...but I will also work on a fix in the jenkins m2release plugin asap to get > this issue sorted for all versions of the maven-release-plugin -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12128) Expose releaseVersion and developmentVersion as environment variables
[ https://issues.jenkins-ci.org/browse/JENKINS-12128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-12128. Resolution: Fixed > Expose releaseVersion and developmentVersion as environment variables > - > > Key: JENKINS-12128 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12128 > Project: Jenkins > Issue Type: Improvement > Components: m2release >Affects Versions: current > Environment: Not applicable >Reporter: Jason Spotswood >Assignee: teilo > Labels: envinronment-variables > > When building a Maven release, the parameters Release Version and Development > Version are passed to the Maven release command via -DreleaseVersion and > -DdevelopmentVersion respectively. > It would be extremely handy to expose these as environment variables so that > they can be accessed throughout the job configuration; for example just like > the variable WORKSPACE. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12128) Expose releaseVersion and developmentVersion as environment variables
[ https://issues.jenkins-ci.org/browse/JENKINS-12128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159236#comment-159236 ] SCM/JIRA link daemon commented on JENKINS-12128: Code changed in jenkins User: imod Path: src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseAction.java src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseBuildWrapper.java http://jenkins-ci.org/commit/m2release-plugin/c78a508bcb9634c01b582ea7c3791fae86eeded0 Log: [FIXED JENKINS-12128] expose dryRun flag, release and dev version as env variables Compare: https://github.com/jenkinsci/m2release-plugin/compare/d302d15...c78a508 > Expose releaseVersion and developmentVersion as environment variables > - > > Key: JENKINS-12128 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12128 > Project: Jenkins > Issue Type: Improvement > Components: m2release >Affects Versions: current > Environment: Not applicable >Reporter: Jason Spotswood >Assignee: teilo > Labels: envinronment-variables > > When building a Maven release, the parameters Release Version and Development > Version are passed to the Maven release command via -DreleaseVersion and > -DdevelopmentVersion respectively. > It would be extremely handy to expose these as environment variables so that > they can be accessed throughout the job configuration; for example just like > the variable WORKSPACE. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12128) Expose releaseVersion and developmentVersion as environment variables
[ https://issues.jenkins-ci.org/browse/JENKINS-12128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159237#comment-159237 ] dogfood commented on JENKINS-12128: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_m2release #66|http://ci.jenkins-ci.org/job/plugins_m2release/66/] [FIXED JENKINS-12128] expose dryRun flag, release and dev version as env variables (Revision c78a508bcb9634c01b582ea7c3791fae86eeded0) Result = SUCCESS imod : Files : * src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseAction.java * src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseBuildWrapper.java > Expose releaseVersion and developmentVersion as environment variables > - > > Key: JENKINS-12128 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12128 > Project: Jenkins > Issue Type: Improvement > Components: m2release >Affects Versions: current > Environment: Not applicable >Reporter: Jason Spotswood >Assignee: teilo > Labels: envinronment-variables > > When building a Maven release, the parameters Release Version and Development > Version are passed to the Maven release command via -DreleaseVersion and > -DdevelopmentVersion respectively. > It would be extremely handy to expose these as environment variables so that > they can be accessed throughout the job configuration; for example just like > the variable WORKSPACE. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12812) dryRun switch failes
[ https://issues.jenkins-ci.org/browse/JENKINS-12812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159238#comment-159238 ] dogfood commented on JENKINS-12812: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_m2release #66|http://ci.jenkins-ci.org/job/plugins_m2release/66/] [FIXED JENKINS-12812] make dryRun goal configurable (Revision 5dcb1672efae3e4e6acbec057193829b4bad3a65) Result = SUCCESS imod : Files : * src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseBuildWrapper.java * src/main/resources/org/jvnet/hudson/plugins/m2release/M2ReleaseBuildWrapper/config.jelly * src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseArgumentInterceptorAction.java * src/main/webapp/help-projectConfig-dryRunGoals.html * src/test/java/org/jvnet/hudson/plugins/m2release/M2ReleaseActionTest.java > dryRun switch failes > > > Key: JENKINS-12812 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12812 > Project: Jenkins > Issue Type: Bug > Components: m2release > Environment: m2release 0.9.0 >Reporter: domi >Assignee: domi > > triggering a release build with the dryRun checkbox checked failes because > release:perform does not support the dryRun flag. > I have already opened a feature request for the maven-release-plugin: > https://jira.codehaus.org/browse/MRELEASE-736 > ...but I will also work on a fix in the jenkins m2release plugin asap to get > this issue sorted for all versions of the maven-release-plugin -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12807) CVS plugin throwing Exception every time
[ https://issues.jenkins-ci.org/browse/JENKINS-12807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159239#comment-159239 ] Michael Clarke commented on JENKINS-12807: -- I'm not sure how you can get a NPE there - File.listFiles() is returning null which should only happen if we're calling it on a file rather than a directory, which shouldn't be possible in that block of code. I'll put in a null check but is there any chance you could upload your job's xml config (obscure any values you don't want the world to know)? > CVS plugin throwing Exception every time > > > Key: JENKINS-12807 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12807 > Project: Jenkins > Issue Type: Bug > Components: cvs >Affects Versions: current > Environment: SLES11 >Reporter: Mark Trinh > > After using the cvs plugin to get changes, it's throwing an exception at the > end and never passes. > cvs rlog: Logging zlib/x64/Release > FATAL: null > java.lang.NullPointerException > at hudson.scm.CVSSCM$3.buildFileList(CVSSCM.java:922) > at hudson.scm.CVSSCM$3.invoke(CVSSCM.java:900) > at hudson.scm.CVSSCM$3.invoke(CVSSCM.java:886) > at hudson.FilePath.act(FilePath.java:758) > at hudson.FilePath.act(FilePath.java:740) > at hudson.scm.CVSSCM.getCvsFiles(CVSSCM.java:886) > at hudson.scm.CVSSCM.calculateWorkspaceState(CVSSCM.java:869) > at hudson.scm.CVSSCM.checkout(CVSSCM.java:836) > at hudson.model.AbstractProject.checkout(AbstractProject.java:1193) > at > hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:566) > at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:454) > at hudson.model.Run.run(Run.java:1376) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:230) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12807) CVS plugin throwing Exception every time
[ https://issues.jenkins-ci.org/browse/JENKINS-12807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Clarke reassigned JENKINS-12807: Assignee: Michael Clarke > CVS plugin throwing Exception every time > > > Key: JENKINS-12807 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12807 > Project: Jenkins > Issue Type: Bug > Components: cvs >Affects Versions: current > Environment: SLES11 >Reporter: Mark Trinh >Assignee: Michael Clarke > > After using the cvs plugin to get changes, it's throwing an exception at the > end and never passes. > cvs rlog: Logging zlib/x64/Release > FATAL: null > java.lang.NullPointerException > at hudson.scm.CVSSCM$3.buildFileList(CVSSCM.java:922) > at hudson.scm.CVSSCM$3.invoke(CVSSCM.java:900) > at hudson.scm.CVSSCM$3.invoke(CVSSCM.java:886) > at hudson.FilePath.act(FilePath.java:758) > at hudson.FilePath.act(FilePath.java:740) > at hudson.scm.CVSSCM.getCvsFiles(CVSSCM.java:886) > at hudson.scm.CVSSCM.calculateWorkspaceState(CVSSCM.java:869) > at hudson.scm.CVSSCM.checkout(CVSSCM.java:836) > at hudson.model.AbstractProject.checkout(AbstractProject.java:1193) > at > hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:566) > at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:454) > at hudson.model.Run.run(Run.java:1376) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:230) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12807) CVS plugin throwing Exception every time
[ https://issues.jenkins-ci.org/browse/JENKINS-12807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-12807 started by Michael Clarke. > CVS plugin throwing Exception every time > > > Key: JENKINS-12807 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12807 > Project: Jenkins > Issue Type: Bug > Components: cvs >Affects Versions: current > Environment: SLES11 >Reporter: Mark Trinh >Assignee: Michael Clarke > > After using the cvs plugin to get changes, it's throwing an exception at the > end and never passes. > cvs rlog: Logging zlib/x64/Release > FATAL: null > java.lang.NullPointerException > at hudson.scm.CVSSCM$3.buildFileList(CVSSCM.java:922) > at hudson.scm.CVSSCM$3.invoke(CVSSCM.java:900) > at hudson.scm.CVSSCM$3.invoke(CVSSCM.java:886) > at hudson.FilePath.act(FilePath.java:758) > at hudson.FilePath.act(FilePath.java:740) > at hudson.scm.CVSSCM.getCvsFiles(CVSSCM.java:886) > at hudson.scm.CVSSCM.calculateWorkspaceState(CVSSCM.java:869) > at hudson.scm.CVSSCM.checkout(CVSSCM.java:836) > at hudson.model.AbstractProject.checkout(AbstractProject.java:1193) > at > hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:566) > at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:454) > at hudson.model.Run.run(Run.java:1376) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:230) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12807) CVS plugin throwing Exception every time
[ https://issues.jenkins-ci.org/browse/JENKINS-12807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-12807. Resolution: Fixed > CVS plugin throwing Exception every time > > > Key: JENKINS-12807 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12807 > Project: Jenkins > Issue Type: Bug > Components: cvs >Affects Versions: current > Environment: SLES11 >Reporter: Mark Trinh >Assignee: Michael Clarke > > After using the cvs plugin to get changes, it's throwing an exception at the > end and never passes. > cvs rlog: Logging zlib/x64/Release > FATAL: null > java.lang.NullPointerException > at hudson.scm.CVSSCM$3.buildFileList(CVSSCM.java:922) > at hudson.scm.CVSSCM$3.invoke(CVSSCM.java:900) > at hudson.scm.CVSSCM$3.invoke(CVSSCM.java:886) > at hudson.FilePath.act(FilePath.java:758) > at hudson.FilePath.act(FilePath.java:740) > at hudson.scm.CVSSCM.getCvsFiles(CVSSCM.java:886) > at hudson.scm.CVSSCM.calculateWorkspaceState(CVSSCM.java:869) > at hudson.scm.CVSSCM.checkout(CVSSCM.java:836) > at hudson.model.AbstractProject.checkout(AbstractProject.java:1193) > at > hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:566) > at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:454) > at hudson.model.Run.run(Run.java:1376) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:230) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12807) CVS plugin throwing Exception every time
[ https://issues.jenkins-ci.org/browse/JENKINS-12807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159240#comment-159240 ] SCM/JIRA link daemon commented on JENKINS-12807: Code changed in jenkins User: Michael Clarke Path: src/main/java/hudson/scm/CVSSCM.java http://jenkins-ci.org/commit/cvs-plugin/8051c513eb71d274273a8004f76607764ce31113 Log: [FIXED JENKINS-12807] Adding null check in when getting child files > CVS plugin throwing Exception every time > > > Key: JENKINS-12807 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12807 > Project: Jenkins > Issue Type: Bug > Components: cvs >Affects Versions: current > Environment: SLES11 >Reporter: Mark Trinh >Assignee: Michael Clarke > > After using the cvs plugin to get changes, it's throwing an exception at the > end and never passes. > cvs rlog: Logging zlib/x64/Release > FATAL: null > java.lang.NullPointerException > at hudson.scm.CVSSCM$3.buildFileList(CVSSCM.java:922) > at hudson.scm.CVSSCM$3.invoke(CVSSCM.java:900) > at hudson.scm.CVSSCM$3.invoke(CVSSCM.java:886) > at hudson.FilePath.act(FilePath.java:758) > at hudson.FilePath.act(FilePath.java:740) > at hudson.scm.CVSSCM.getCvsFiles(CVSSCM.java:886) > at hudson.scm.CVSSCM.calculateWorkspaceState(CVSSCM.java:869) > at hudson.scm.CVSSCM.checkout(CVSSCM.java:836) > at hudson.model.AbstractProject.checkout(AbstractProject.java:1193) > at > hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:566) > at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:454) > at hudson.model.Run.run(Run.java:1376) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:230) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12807) CVS plugin throwing Exception every time
[ https://issues.jenkins-ci.org/browse/JENKINS-12807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159241#comment-159241 ] dogfood commented on JENKINS-12807: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_cvs #11|http://ci.jenkins-ci.org/job/plugins_cvs/11/] [FIXED JENKINS-12807] Adding null check in when getting child files (Revision 8051c513eb71d274273a8004f76607764ce31113) Result = SUCCESS michael.m.clarke : Files : * src/main/java/hudson/scm/CVSSCM.java > CVS plugin throwing Exception every time > > > Key: JENKINS-12807 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12807 > Project: Jenkins > Issue Type: Bug > Components: cvs >Affects Versions: current > Environment: SLES11 >Reporter: Mark Trinh >Assignee: Michael Clarke > > After using the cvs plugin to get changes, it's throwing an exception at the > end and never passes. > cvs rlog: Logging zlib/x64/Release > FATAL: null > java.lang.NullPointerException > at hudson.scm.CVSSCM$3.buildFileList(CVSSCM.java:922) > at hudson.scm.CVSSCM$3.invoke(CVSSCM.java:900) > at hudson.scm.CVSSCM$3.invoke(CVSSCM.java:886) > at hudson.FilePath.act(FilePath.java:758) > at hudson.FilePath.act(FilePath.java:740) > at hudson.scm.CVSSCM.getCvsFiles(CVSSCM.java:886) > at hudson.scm.CVSSCM.calculateWorkspaceState(CVSSCM.java:869) > at hudson.scm.CVSSCM.checkout(CVSSCM.java:836) > at hudson.model.AbstractProject.checkout(AbstractProject.java:1193) > at > hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:566) > at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:454) > at hudson.model.Run.run(Run.java:1376) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:230) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12053) Sonar plugin fails execution on m2release execution
[ https://issues.jenkins-ci.org/browse/JENKINS-12053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] domi resolved JENKINS-12053. Resolution: Won't Fix This is unlikely to be fixed in the m2release plugin... But since version 0.9.0, the m2release plugin allows to reuse the normal build parameters: https://issues.jenkins-ci.org/browse/JENKINS-10127 and together with the latest Sonar plugin you are able to skip the sonar execution when ever you like. e.g. this will allow you to define a SKIP_SONAR parameter to skip the sonar analyzes for the release build. > Sonar plugin fails execution on m2release execution > --- > > Key: JENKINS-12053 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12053 > Project: Jenkins > Issue Type: Improvement > Components: m2release >Affects Versions: current > Environment: Jenkins 1.442; Sonar plugin 1.6.1; m2Release plugin 0.8.1 >Reporter: Justin Smith >Assignee: teilo >Priority: Minor > Labels: release, sonar > > Our builds are configured to execute sonar with the Sonar plugin. This > occurs after the initial reactor's build cycle completes, so all of the > artifacts from the build have been installed to the local repo. On executing > a release, the release performs as desired, but sonar executes after it is > finished (as part of the jenkins build, but a separate reactor) with the new > versions in the poms after the release. It fails because it cannot find the > dependencies, because they have not been build/installed yet. > Current work-around is to disable sonar for the release, execute release, > enable sonar, run another build. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8664) m2release fails if no existing build exists for the job
[ https://issues.jenkins-ci.org/browse/JENKINS-8664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] domi resolved JENKINS-8664. --- Assignee: domi (was: teilo) Resolution: Fixed solved since version 0.9.0 > m2release fails if no existing build exists for the job > --- > > Key: JENKINS-8664 > URL: https://issues.jenkins-ci.org/browse/JENKINS-8664 > Project: Jenkins > Issue Type: Bug > Components: m2release >Reporter: Steven Zhu >Assignee: domi >Priority: Critical > > I installed m2release plugin into Hudson and got the below error information > after start to perform maven release. > ERROR: Processing failed due to a bug in the code. Please report this to > hudson-us...@googlegroups.com > java.lang.NullPointerException > at > org.jvnet.hudson.plugins.m2release.M2ReleaseBuildWrapper.getReleaseVersion(M2ReleaseBuildWrapper.java:345) > at > org.jvnet.hudson.plugins.m2release.M2ReleaseBuildWrapper.setUp(M2ReleaseBuildWrapper.java:161) > at > hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:516) > at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:417) > at hudson.model.Run.run(Run.java:1362) > at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:400) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:145) > project=hudson.maven.MavenModuleSet@3fcf59[Test] > project.getModules()=[] > project.getRootModule()=null > FATAL: null > java.lang.NullPointerException > at > org.jvnet.hudson.plugins.m2release.M2ReleaseBuildWrapper.getReleaseVersion(M2ReleaseBuildWrapper.java:345) > at > org.jvnet.hudson.plugins.m2release.M2ReleaseBuildWrapper.setUp(M2ReleaseBuildWrapper.java:161) > at > hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:516) > at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:417) > at hudson.model.Run.run(Run.java:1362) > at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:400) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:145) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8608) release plugin changes maven goals if an error occurs
[ https://issues.jenkins-ci.org/browse/JENKINS-8608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] domi resolved JENKINS-8608. --- Assignee: domi (was: teilo) Resolution: Fixed this is fixed since version 0.9.0 > release plugin changes maven goals if an error occurs > - > > Key: JENKINS-8608 > URL: https://issues.jenkins-ci.org/browse/JENKINS-8608 > Project: Jenkins > Issue Type: Bug > Components: m2release >Affects Versions: current > Environment: linux hudson running stand-alone, proxied behind apache. > Hudson version 1.394, release plugin 0.6.1 >Reporter: scooper4711 >Assignee: domi > > We set up a new project and performed a build which succeeded. After that, I > scheduled a maven release. it failed with this error: > Found mavenVersion 2.2.1 from file > jar:file:/var/lib/hudson/tools/Maven2/lib/maven-2.2.1-uber.jar!/META-INF/maven/org.apache.maven/maven-core/pom.properties > ERROR: Processing failed due to a bug in the code. Please report this to > hudson-us...@googlegroups.com > java.lang.NullPointerException > at > org.jvnet.hudson.plugins.m2release.M2ReleaseBuildWrapper.getReleaseVersion(M2ReleaseBuildWrapper.java:345) > at > org.jvnet.hudson.plugins.m2release.M2ReleaseBuildWrapper.setUp(M2ReleaseBuildWrapper.java:161) > at > hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:521) > at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:417) > at hudson.model.Run.run(Run.java:1362) > at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:405) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:145) > project=hudson.maven.MavenModuleSet@528e75f2[ften-common-ui_3.0_bugfix] > project.getModules()=[hudson.maven.MavenModule@63d8f452[ften-common-ui_3.0_bugfix/com.ften.ui:ften-common-ui][ften-common-ui_3.0_bugfix/com.ften.ui:ften-common-ui][relativePath:]] > project.getRootModule()=null > FATAL: null > This error may have been because we switched from one shared repository to a > separate repository for each project. Not sure. But that's not why I'm > creating this issue. > What happened is that the maven goals for the project changed from what they > were to the maven release goals. - release:clean release:prepare > release:perform. > I suspect that the code to revert the goals to what they were needs to be > wrapped in a finally block to ensure that regardless of what happens, the > goals are reverted to their original state. > Ironically, the next build actually did a successful release:clean > release:prepare release:perform. *edit* the successful release was because > the goals were changed. I didn't invoke the release plugin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6944) Make passed SCM credentials available to other plugins
[ https://issues.jenkins-ci.org/browse/JENKINS-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] domi resolved JENKINS-6944. --- Assignee: domi (was: teilo) Resolution: Fixed fixed since version 0.9.0 > Make passed SCM credentials available to other plugins > -- > > Key: JENKINS-6944 > URL: https://issues.jenkins-ci.org/browse/JENKINS-6944 > Project: Jenkins > Issue Type: New Feature > Components: m2release > Environment: all >Reporter: domi >Assignee: domi > > By making the passed SCM credentials available to other plugins, it will be > possible to enhance pre/post release build steps with the maven-scm-plugin. > This would allow to do some automated modifications on the source befor the > real release will be triggered. > http://issues.jenkins-ci.org/browse/JENKINS-6601 is a prerequisite. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8524) maven release build exposes users' username and password
[ https://issues.jenkins-ci.org/browse/JENKINS-8524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] domi resolved JENKINS-8524. --- Assignee: domi (was: teilo) Resolution: Fixed fixed with version 0.9.0 > maven release build exposes users' username and password > > > Key: JENKINS-8524 > URL: https://issues.jenkins-ci.org/browse/JENKINS-8524 > Project: Jenkins > Issue Type: Bug > Components: m2release >Affects Versions: current > Environment: Aplies for all versions so for and other OS's. > System info: > Tomcat 5.5 > file.encoding UTF-8 > file.encoding.pkg sun.io > file.separator/ > java.awt.graphicsenv sun.awt.X11GraphicsEnvironment > java.awt.headless true > java.awt.printerjob sun.print.PSPrinterJob > java.class.version50.0 > java.naming.factory.initial org.apache.naming.java.javaURLContextFactory > java.naming.factory.url.pkgs org.apache.naming > java.runtime.name Java(TM) SE Runtime Environment > java.runtime.version 1.6.0_16-b01 > java.specification.name Java Platform API Specification > java.specification.vendor Sun Microsystems Inc. > java.specification.version1.6 > java.util.logging.manager org.apache.juli.ClassLoaderLogManager > java.vendor Sun Microsystems Inc. > java.vendor.url http://java.sun.com/ > java.vendor.url.bug http://java.sun.com/cgi-bin/bugreport.cgi > java.version 1.6.0_16 > java.vm.info mixed mode > java.vm.name Java HotSpot(TM) 64-Bit Server VM > java.vm.specification.nameJava Virtual Machine Specification > java.vm.specification.vendor Sun Microsystems Inc. > java.vm.specification.version 1.0 > java.vm.vendorSun Microsystems Inc. > java.vm.version 14.2-b01 > line.separator > os.arch amd64 > os.name Linux > os.version2.6.28-11-server > sun.arch.data.model 64 > sun.cpu.endianlittle > sun.cpu.isalist > sun.io.unicode.encoding UnicodeLittle > sun.jnu.encoding UTF-8 > sun.management.compiler HotSpot 64-Bit Server Compiler > sun.os.patch.levelunknown > svnkit.ssh2.persistentfalse > tomcat.util.buf.StringCache.byte.enabled true > user.country US > user.language en > user.name hudson > user.timezone Europe/Amsterdam >Reporter: whermeling >Assignee: domi > > When you specify a custom username and password to be used in a maven release > build (using the option 'Specify SCM login/password'), the filled in username > and password can be read by anyone who can Configure the build. If you run a > release build and then, while it is still runnning, you configure the build > plan, the see that the 'Goals and options' have changed to the one which are > currently used for the release build. > So in my case this then shows: -Dpassword=*** -Dusername=*** > -Dproject.rel.:= > -Dproject.dev.:= -Dresume=false > release:prepare release:perform > It seems the m2 release plugin is using the 'Goals and options' field to > manage the parameters the release build. > A workaround could be to mask these credentials in the 'Goals and options' > fields. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8740) Log file filling up disk with connection reset and broken pipe errors
[
https://issues.jenkins-ci.org/browse/JENKINS-8740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159248#comment-159248
]
evernat commented on JENKINS-8740:
--
There was somes fixes in the remoting between master and slaves up to Jenkins
v1.416.
Is your issue reproducible with a recent version of Jenkins?
> Log file filling up disk with connection reset and broken pipe errors
> -
>
> Key: JENKINS-8740
> URL: https://issues.jenkins-ci.org/browse/JENKINS-8740
> Project: Jenkins
> Issue Type: Bug
> Components: master-slave
>Affects Versions: current
> Environment: http://ci.jruby.org/
> Jenkins 1.396
> Linux ip-10-251-193-235 2.6.18-xenU-ec2-v1.0 #2 SMP Tue Feb 19 10:51:53 EST
> 2008 i686 Dual-Core AMD Opteron(tm) Processor 2218 HE AuthenticAMD GNU/Linux
> Java 1.6.0_11-b03
>Reporter: Nick Sieger
>Priority: Critical
> Attachments: ci.jruby.org-jenkins-node.log,
> ci.jruby.org-jenkins-node2.log
>
>
> I have ci.jruby.org running a recent Jenkins build with a master and 3 remote
> nodes started by JNLP. After a while the nodes get disconnected, and the
> master's log starts filling up with these stack traces:
> {noformat}
> Feb 7, 2011 12:22:00 PM hudson.remoting.ProxyOutputStream$Chunk$1 run
> WARNING: Failed to write to stream
> winstone.ClientSocketException: Failed to write to client
> at winstone.ClientOutputStream.write(ClientOutputStream.java:41)
> at winstone.WinstoneOutputStream.commit(WinstoneOutputStream.java:181)
> at winstone.WinstoneOutputStream.commit(WinstoneOutputStream.java:119)
> at winstone.WinstoneOutputStream.write(WinstoneOutputStream.java:112)
> at java.io.OutputStream.write(OutputStream.java:58)
> at
> hudson.remoting.ProxyOutputStream$Chunk$1.run(ProxyOutputStream.java:185)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
> Caused by: java.net.SocketException: Connection reset
> at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:96)
> at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
> at winstone.ClientOutputStream.write(ClientOutputStream.java:39)
> ... 11 more
> Feb 7, 2011 12:22:00 PM hudson.remoting.ProxyOutputStream$Chunk$1 run
> WARNING: Failed to write to stream
> winstone.ClientSocketException: Failed to write to client
> at winstone.ClientOutputStream.write(ClientOutputStream.java:41)
> at winstone.WinstoneOutputStream.commit(WinstoneOutputStream.java:181)
> at winstone.WinstoneOutputStream.commit(WinstoneOutputStream.java:119)
> at winstone.WinstoneOutputStream.write(WinstoneOutputStream.java:112)
> at java.io.OutputStream.write(OutputStream.java:58)
> at
> hudson.remoting.ProxyOutputStream$Chunk$1.run(ProxyOutputStream.java:185)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
> Caused by: java.net.SocketException: Broken pipe
> at java.net.SocketOutputStream.socketWrite0(Native Method)
> at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
> at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
> at winstone.ClientOutputStream.write(ClientOutputStream.java:39)
> ... 11 more
> {noformat}
> I can provide a login to the Jenkins instance on ci.jruby.org if desired.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12824) Master does not build due to version bump
[ https://issues.jenkins-ci.org/browse/JENKINS-12824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] olamy resolved JENKINS-12824. - Assignee: olamy (was: rsandell) Resolution: Fixed > Master does not build due to version bump > - > > Key: JENKINS-12824 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12824 > Project: Jenkins > Issue Type: Bug > Components: gerrit-trigger >Reporter: James Blair >Assignee: olamy > > The recent version bump to build-config 1.2.5-SNAPSHOT is incomplete, so > master doesn't currently build. > The build-config dependency versions in the other subprojects need to be > updated to match. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12457) 'Age' column on 'Test Result' tab may show incorrect value when a test suite divided into multiple junit files
[
https://issues.jenkins-ci.org/browse/JENKINS-12457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
SCM/JIRA link daemon resolved JENKINS-12457.
Resolution: Fixed
> 'Age' column on 'Test Result' tab may show incorrect value when a test suite
> divided into multiple junit files
> --
>
> Key: JENKINS-12457
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12457
> Project: Jenkins
> Issue Type: Improvement
> Components: junit
>Affects Versions: current
>Reporter: Greg Temchenko
>Assignee: Greg Temchenko
>
> Somebody described the problem a year ago here:
> http://jenkins.361315.n4.nabble.com/Problem-with-Age-column-on-Test-Results-tab-td3172208.html
> {quote}
> I have a problem with 'Age' column on 'Test Results' tab. For couple of my
> tests, all the time this column has value equals '1', despite the fact that
> those tests start failing earlier than one build ago. When I switch to
> 'History' tab, in 'Test Result' column there is a 'Regression' value for all
> builds, and it should be 'Regression' value only for the first build and
> 'Failed' for next builds.
> {quote}
> For me this happens because I have many junit xmls that containing the same
> test suite name.
> In this case hudson.tasks.junit.CaseResult.getPreviousResult() gets the only
> last junit xml result and if it's not failed then the Age column won't be
> calculated properly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12457) 'Age' column on 'Test Result' tab may show incorrect value when a test suite divided into multiple junit files
[
https://issues.jenkins-ci.org/browse/JENKINS-12457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159250#comment-159250
]
SCM/JIRA link daemon commented on JENKINS-12457:
Code changed in jenkins
User: Christoph Kutzinski
Path:
core/src/main/java/hudson/tasks/junit/CaseResult.java
core/src/main/java/hudson/tasks/junit/SuiteResult.java
core/src/main/java/hudson/tasks/junit/TestResult.java
core/src/test/java/hudson/tasks/junit/TestResultTest.java
core/src/test/resources/hudson/tasks/junit/eclipse-plugin-test-report.xml
http://jenkins-ci.org/commit/jenkins/a885a2391378bab20ee431f6296f6768a4b3a083
Log:
Merge pull request #367 from kutzi/duplicate-test-results
[FIXED JENKINS-12457] 'Age' column on 'Test Result' tab may show incorre...
Compare: https://github.com/jenkinsci/jenkins/compare/bbcf286...a885a23
> 'Age' column on 'Test Result' tab may show incorrect value when a test suite
> divided into multiple junit files
> --
>
> Key: JENKINS-12457
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12457
> Project: Jenkins
> Issue Type: Improvement
> Components: junit
>Affects Versions: current
>Reporter: Greg Temchenko
>Assignee: Greg Temchenko
>
> Somebody described the problem a year ago here:
> http://jenkins.361315.n4.nabble.com/Problem-with-Age-column-on-Test-Results-tab-td3172208.html
> {quote}
> I have a problem with 'Age' column on 'Test Results' tab. For couple of my
> tests, all the time this column has value equals '1', despite the fact that
> those tests start failing earlier than one build ago. When I switch to
> 'History' tab, in 'Test Result' column there is a 'Regression' value for all
> builds, and it should be 'Regression' value only for the first build and
> 'Failed' for next builds.
> {quote}
> For me this happens because I have many junit xmls that containing the same
> test suite name.
> In this case hudson.tasks.junit.CaseResult.getPreviousResult() gets the only
> last junit xml result and if it's not failed then the Age column won't be
> calculated properly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12457) 'Age' column on 'Test Result' tab may show incorrect value when a test suite divided into multiple junit files
[
https://issues.jenkins-ci.org/browse/JENKINS-12457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159249#comment-159249
]
SCM/JIRA link daemon commented on JENKINS-12457:
Code changed in jenkins
User: Christoph Kutzinski
Path:
core/src/main/java/hudson/tasks/junit/CaseResult.java
core/src/main/java/hudson/tasks/junit/SuiteResult.java
core/src/main/java/hudson/tasks/junit/TestResult.java
core/src/test/java/hudson/tasks/junit/TestResultTest.java
core/src/test/resources/hudson/tasks/junit/eclipse-plugin-test-report.xml
http://jenkins-ci.org/commit/jenkins/05937f5343f844593ebd23ced2f62c4ca7308793
Log:
[FIXED JENKINS-12457] 'Age' column on 'Test Result' tab may show incorrect
value when a test suite divided into multiple junit files
> 'Age' column on 'Test Result' tab may show incorrect value when a test suite
> divided into multiple junit files
> --
>
> Key: JENKINS-12457
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12457
> Project: Jenkins
> Issue Type: Improvement
> Components: junit
>Affects Versions: current
>Reporter: Greg Temchenko
>Assignee: Greg Temchenko
>
> Somebody described the problem a year ago here:
> http://jenkins.361315.n4.nabble.com/Problem-with-Age-column-on-Test-Results-tab-td3172208.html
> {quote}
> I have a problem with 'Age' column on 'Test Results' tab. For couple of my
> tests, all the time this column has value equals '1', despite the fact that
> those tests start failing earlier than one build ago. When I switch to
> 'History' tab, in 'Test Result' column there is a 'Regression' value for all
> builds, and it should be 'Regression' value only for the first build and
> 'Failed' for next builds.
> {quote}
> For me this happens because I have many junit xmls that containing the same
> test suite name.
> In this case hudson.tasks.junit.CaseResult.getPreviousResult() gets the only
> last junit xml result and if it's not failed then the Age column won't be
> calculated properly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12457) 'Age' column on 'Test Result' tab may show incorrect value when a test suite divided into multiple junit files
[
https://issues.jenkins-ci.org/browse/JENKINS-12457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159251#comment-159251
]
SCM/JIRA link daemon commented on JENKINS-12457:
Code changed in jenkins
User: Christoph Kutzinski
Path:
changelog.html
http://jenkins-ci.org/commit/jenkins/fd0d1cbe085daac0c734d446c3009d6b58845ab3
Log:
Changelog for JENKINS-12457 / pull request #367
> 'Age' column on 'Test Result' tab may show incorrect value when a test suite
> divided into multiple junit files
> --
>
> Key: JENKINS-12457
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12457
> Project: Jenkins
> Issue Type: Improvement
> Components: junit
>Affects Versions: current
>Reporter: Greg Temchenko
>Assignee: Greg Temchenko
>
> Somebody described the problem a year ago here:
> http://jenkins.361315.n4.nabble.com/Problem-with-Age-column-on-Test-Results-tab-td3172208.html
> {quote}
> I have a problem with 'Age' column on 'Test Results' tab. For couple of my
> tests, all the time this column has value equals '1', despite the fact that
> those tests start failing earlier than one build ago. When I switch to
> 'History' tab, in 'Test Result' column there is a 'Regression' value for all
> builds, and it should be 'Regression' value only for the first build and
> 'Failed' for next builds.
> {quote}
> For me this happens because I have many junit xmls that containing the same
> test suite name.
> In this case hudson.tasks.junit.CaseResult.getPreviousResult() gets the only
> last junit xml result and if it's not failed then the Age column won't be
> calculated properly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12457) 'Age' column on 'Test Result' tab may show incorrect value when a test suite divided into multiple junit files
[
https://issues.jenkins-ci.org/browse/JENKINS-12457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kutzi reassigned JENKINS-12457:
---
Assignee: kutzi (was: Greg Temchenko)
> 'Age' column on 'Test Result' tab may show incorrect value when a test suite
> divided into multiple junit files
> --
>
> Key: JENKINS-12457
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12457
> Project: Jenkins
> Issue Type: Improvement
> Components: junit
>Affects Versions: current
>Reporter: Greg Temchenko
>Assignee: kutzi
>
> Somebody described the problem a year ago here:
> http://jenkins.361315.n4.nabble.com/Problem-with-Age-column-on-Test-Results-tab-td3172208.html
> {quote}
> I have a problem with 'Age' column on 'Test Results' tab. For couple of my
> tests, all the time this column has value equals '1', despite the fact that
> those tests start failing earlier than one build ago. When I switch to
> 'History' tab, in 'Test Result' column there is a 'Regression' value for all
> builds, and it should be 'Regression' value only for the first build and
> 'Failed' for next builds.
> {quote}
> For me this happens because I have many junit xmls that containing the same
> test suite name.
> In this case hudson.tasks.junit.CaseResult.getPreviousResult() gets the only
> last junit xml result and if it's not failed then the Age column won't be
> calculated properly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12528) Started-By Environment Variable Plugin does not work in manually approved promoted builds
[
https://issues.jenkins-ci.org/browse/JENKINS-12528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159252#comment-159252
]
Gavriil Konovalenko commented on JENKINS-12528:
---
Presence of following string in the build log output: "Legacy code started
this job. No cause information is available" means that username is not
identifiable. Because source for username data is Cause, which is absent.
I'd suggest to reassign this bug to
https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin , asking to
fix absence of build Cause.
> Started-By Environment Variable Plugin does not work in manually approved
> promoted builds
> -
>
> Key: JENKINS-12528
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12528
> Project: Jenkins
> Issue Type: Bug
> Components: promoted-builds, started-by-envvar
>Reporter: Hua Zhang
> Attachments: promoted-build-started-by-not-working.png,
> promoted-build-started-by-working.png
>
>
> Start-By Enviorment Varialbe plugin works olny with "Force Promotion" of
> Promoted Builds plugin.
> In a promotion process, if option "Only when manually approved" (under
> section "Criteria") is selected, and the user promotes the build (on
> "Promotion Status" page) by clicking "Approve" button, JENKINS_STARTED_BY
> will not be correctly populated. In console output:
> {code}
> Legacy code started this job. No cause information is available
> ...
> + echo JENKINS_STARTED_BY=
> JENKINS_STARTED_BY=
> {code}
> If this option is not selected, therefore the user can only promote a build
> by clicking "Force Promotion" (if he has the privilege), then
> JENKINS_STARTED_BY variable is populated correctly. In console output:
> {code}
> Started by user john
> ...
> + echo JENKINS_STARTED_BY=john
> JENKINS_STARTED_BY=john
> {code}
> In attachment are screen-shots of a trivial Jenkins job configuration
> demonstrating the test cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12074) Started-By Environment Variable Plugin does not work
[
https://issues.jenkins-ci.org/browse/JENKINS-12074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159253#comment-159253
]
Stephen Brandwood commented on JENKINS-12074:
-
This plugin is using UserCause to find the user that started the job, but this
has been deprecated and replaced with UserIdCause. I can submit a fix, but I
suggest that people just use the Build User Vars plugin instead
(https://wiki.jenkins-ci.org/display/JENKINS/Build+User+Vars+Plugin)
> Started-By Environment Variable Plugin does not work
>
>
> Key: JENKINS-12074
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12074
> Project: Jenkins
> Issue Type: Bug
> Components: started-by-envvar
> Environment: Jenkins 1.442 with plugin version 1.0
>Reporter: Stephen Brandwood
> Labels: jenkins, plugin
>
> It is expected that the following will print the user that started the job
> when placed in a shell script:
> echo ${JENKINS_STARTED_BY}
> But it does not. It appears that the value is not populated as it should be.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12828) semicolon parameter separator for cloudformation
Matt Fair created JENKINS-12828:
---
Summary: semicolon parameter separator for cloudformation
Key: JENKINS-12828
URL: https://issues.jenkins-ci.org/browse/JENKINS-12828
Project: Jenkins
Issue Type: Improvement
Components: cloudformation
Reporter: Matt Fair
Assignee: edovale
Currently the parameter list is comma delimited and therefore does not support
CommaDelimitedList type parameter values. To fix this the semicolon delimiter
can be added as the primary delimiter. The cfn-create-stack command line
application uses the semicolon as its parameter separator:
{code}
param1=value1;param2=value2;param3=list1,list2,list3,list4;param5=value5
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
