[JIRA] (JENKINS-11346) Multi-Configuration Jobs remember deleted slaves
Thomas Fürer closed JENKINS-11346 as Cannot Reproduce Multi-Configuration Jobs remember deleted slaves Change By: Thomas Fürer (20/Jan/13 8:52 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10312) Build Queue and Running Jobs should be removed from view.
Niko Mahle assigned JENKINS-10312 to Niko Mahle Build Queue and Running Jobs should be removed from view. Change By: Niko Mahle (20/Jan/13 9:18 AM) Assignee: JulienRENAUT NikoMahle This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16121) maven-soapui-plugin configurable outputFolder
kutzi assigned JENKINS-16121 to kutzi maven-soapui-plugin configurable outputFolder Change By: kutzi (20/Jan/13 10:55 AM) Assignee: kutzi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16121) maven-soapui-plugin configurable outputFolder
kutzi resolved JENKINS-16121 as Fixed maven-soapui-plugin configurable outputFolder Should also be fixed by fix for JENKINS-8334 https://github.com/jenkinsci/jenkins/commit/79fbe28bb4920d397847f52800f59d0c355038b5 Change By: kutzi (20/Jan/13 10:56 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13678) Maven test failures hide more important errors
kutzi commented on JENKINS-13678 Maven test failures hide more important errors Do you have any test project to reproduce this error? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13678) Maven test failures hide more important errors
kutzi assigned JENKINS-13678 to kutzi Maven test failures hide more important errors Change By: kutzi (20/Jan/13 11:01 AM) Assignee: KohsukeKawaguchi kutzi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13678) Maven test failures hide more important errors
kutzi updated JENKINS-13678 Maven test failures hide more important errors Change By: kutzi (20/Jan/13 11:02 AM) Due Date: 17/Feb/13 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-5130) NPE during Surefire execution of a Maven project without any tests
kutzi commented on JENKINS-5130 NPE during Surefire execution of a Maven project without any tests Can you reproduce this with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-5130) NPE during Surefire execution of a Maven project without any tests
kutzi assigned JENKINS-5130 to kutzi NPE during Surefire execution of a Maven project without any tests Change By: kutzi (20/Jan/13 11:03 AM) Assignee: kutzi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15274) Build fails if there are test failures during Invoke top-level Maven targets build step
kutzi resolved JENKINS-15274 as Not A Defect Build fails if there are test failures during Invoke top-level Maven targets build step Use -Dmaven.test.failure.ignore=true This is not an issue, but a question. Please post such things to the users list. Thanks Change By: kutzi (20/Jan/13 11:06 AM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-3954) OutOfMemoryError on Maven site on SECOND build
kutzi updated JENKINS-3954 OutOfMemoryError on Maven site on SECOND build Change By: kutzi (20/Jan/13 11:08 AM) Due Date: 31/Mar/13 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11721) MavenTestDataPublisher does not work with modules and after restart
kutzi updated JENKINS-11721 MavenTestDataPublisher does not work with modules and after restart Change By: kutzi (20/Jan/13 11:10 AM) Due Date: 31/Mar/13 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11721) MavenTestDataPublisher does not work with modules and after restart
kutzi assigned JENKINS-11721 to kutzi MavenTestDataPublisher does not work with modules and after restart Change By: kutzi (20/Jan/13 11:10 AM) Assignee: kutzi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11721) MavenTestDataPublisher does not work with modules and after restart
kutzi commented on JENKINS-11721 MavenTestDataPublisher does not work with modules and after restart If these are 2 different problems, please post 2 JIRA issues. Do you have a test project to reproduce the problems? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15865) Jenkins build fails with fatal error for Maven 2 build of project with maven-failsafe-plugin
kutzi resolved JENKINS-15865 as Fixed Jenkins build fails with fatal error for Maven 2 build of project with maven-failsafe-plugin Change By: kutzi (20/Jan/13 11:14 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-3654) Intercept the m2 reporter invocation when running the maven site goal
Ulli Hafner commented on JENKINS-3654 Intercept the m2 reporter invocation when running the maven site goal I don't think that this has been changed yet. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16215) Avoid unnecessary downloads in FilePath.installIfNecessaryFrom
SCM/JIRA link daemon commented on JENKINS-16215 Avoid unnecessary downloads in FilePath.installIfNecessaryFrom Code changed in jenkins User: Lars Hvile Path: core/src/main/java/hudson/FilePath.java core/src/test/java/hudson/FilePathTest.java http://jenkins-ci.org/commit/jenkins/35f7653b7b28bb65b116f16282d9bea567405f61 Log: JENKINS-16215 Avoiding unnecessary downloads in FilePath.installIfNecessaryFrom. The updated version uses the locally cached timestamp, '.timestamp', to set the 'If-Modified-Since' header. 304 Not Modified responses are dealt with by aborting the installation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16215) Avoid unnecessary downloads in FilePath.installIfNecessaryFrom
SCM/JIRA link daemon commented on JENKINS-16215 Avoid unnecessary downloads in FilePath.installIfNecessaryFrom Code changed in jenkins User: Christoph Kutzinski Path: core/src/main/java/hudson/FilePath.java core/src/test/java/hudson/FilePathTest.java http://jenkins-ci.org/commit/jenkins/586af3c1ee910e99a50dde8d8b3e7aa68df06716 Log: Merge pull request #660 from larshvile/master FIXED JENKINS-16215 Avoiding unnecessary downloads in FilePath.installIfNecessaryFrom Compare: https://github.com/jenkinsci/jenkins/compare/6b1cc4702417...586af3c1ee91 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16215) Avoid unnecessary downloads in FilePath.installIfNecessaryFrom
SCM/JIRA link daemon resolved JENKINS-16215 as Fixed Avoid unnecessary downloads in FilePath.installIfNecessaryFrom Change By: SCM/JIRA link daemon (20/Jan/13 12:27 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16215) Avoid unnecessary downloads in FilePath.installIfNecessaryFrom
SCM/JIRA link daemon commented on JENKINS-16215 Avoid unnecessary downloads in FilePath.installIfNecessaryFrom Code changed in jenkins User: Christoph Kutzinski Path: changelog.html core/src/main/java/hudson/FilePath.java http://jenkins-ci.org/commit/jenkins/19b31687c870bba50bb181c5d08486151b1839a9 Log: JENKINS-16215 : changelog This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16215) Avoid unnecessary downloads in FilePath.installIfNecessaryFrom
dogfood commented on JENKINS-16215 Avoid unnecessary downloads in FilePath.installIfNecessaryFrom Integrated in jenkins_main_trunk #2202 JENKINS-16215 Avoiding unnecessary downloads in FilePath.installIfNecessaryFrom. (Revision 35f7653b7b28bb65b116f16282d9bea567405f61) Result = SUCCESS lars : 35f7653b7b28bb65b116f16282d9bea567405f61 Files : core/src/main/java/hudson/FilePath.java core/src/test/java/hudson/FilePathTest.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16314) cvs plugin removes sticky branch tag
Michael Clarke closed JENKINS-16314 as Fixed cvs plugin removes sticky branch tag CVS plugin actually only does the cleanup if we're on HEAD, but a bug in the cleanup code meant it didn't select the right folder to clean the tags on if workspace was flattened Change By: Michael Clarke (20/Jan/13 1:36 PM) Status: Open Closed Assignee: MichaelClarke Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15680) I get this error when using maven release plugin: cvs commit: cannot commit with sticky date for file `pom.xml'
Michael Clarke closed JENKINS-15680 as Duplicate I get this error when using maven release plugin: cvs commit: cannot commit with sticky date for file `pom.xml Closing as per last comment Change By: Michael Clarke (20/Jan/13 1:37 PM) Status: Open Closed Assignee: PeterHayes MichaelClarke Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16044) Exception on CVS Log parsing
Michael Clarke commented on JENKINS-16044 Exception on CVS Log parsing You've identified the correct cause of the problem, although I suspect you changelog doesn't quite list the files correctly since the matched string is 2 characters short (the 'd:' of your path). I'll see if I can create a Windows friendly fix that doesn't require users to have forward slashes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16215) Avoid unnecessary downloads in FilePath.installIfNecessaryFrom
dogfood commented on JENKINS-16215 Avoid unnecessary downloads in FilePath.installIfNecessaryFrom Integrated in jenkins_main_trunk #2203 JENKINS-16215 : changelog (Revision 19b31687c870bba50bb181c5d08486151b1839a9) Result = UNSTABLE Christoph Kutzinski : 19b31687c870bba50bb181c5d08486151b1839a9 Files : core/src/main/java/hudson/FilePath.java changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16044) Exception on CVS Log parsing
SCM/JIRA link daemon resolved JENKINS-16044 as Fixed Exception on CVS Log parsing Change By: SCM/JIRA link daemon (20/Jan/13 2:25 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16044) Exception on CVS Log parsing
SCM/JIRA link daemon commented on JENKINS-16044 Exception on CVS Log parsing Code changed in jenkins User: Michael Clarke Path: src/main/java/hudson/scm/CvsLog.java http://jenkins-ci.org/commit/cvs-plugin/a39c6a206d96106620c5eacb91f4e583cd1bb683 Log: FIXED JENKINS-16044 Allow CVS roots with backslashes during log parse This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16386) Please add a button for viewing the console of the latest / current build
SCM/JIRA link daemon commented on JENKINS-16386 Please add a button for viewing the console of the latest / current build Code changed in jenkins User: Fred G Path: src/main/java/jenkins/plugins/extracolumns/LastBuildConsoleColumn.java src/main/resources/jenkins/plugins/extracolumns/LastBuildConsoleColumn/column.jelly src/main/resources/jenkins/plugins/extracolumns/LastBuildConsoleColumn/columnHeader.jelly src/main/resources/jenkins/plugins/extracolumns/LastBuildConsoleColumn/column_de.properties src/main/resources/jenkins/plugins/extracolumns/LastBuildConsoleColumn/config.jelly src/main/resources/jenkins/plugins/extracolumns/LastBuildConsoleColumn/config_de.properties src/main/resources/jenkins/plugins/extracolumns/Messages.properties src/main/resources/jenkins/plugins/extracolumns/Messages_de.properties http://jenkins-ci.org/commit/extra-columns-plugin/ae479218d287d176423b645995cd3a97dcfc5f8c Log: FIXED JENKINS-16386 Please add a button for viewing the console of the latest / current build This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16386) Please add a button for viewing the console of the latest / current build
SCM/JIRA link daemon resolved JENKINS-16386 as Fixed Please add a button for viewing the console of the latest / current build Change By: SCM/JIRA link daemon (20/Jan/13 3:55 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15167) Parsing pom.xml failed due to '\t' character inside pom.xml
kutzi resolved JENKINS-15167 as Incomplete Parsing pom.xml failed due to \t character inside pom.xml No feedback from reporter Change By: kutzi (20/Jan/13 3:57 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15066) Long wait between last build step and first post build step
kutzi updated JENKINS-15066 Long wait between last build step and first post build step Change By: kutzi (20/Jan/13 3:59 PM) Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16381) Disable button should be an overlay of the build button not a separate button.
Fred G commented on JENKINS-16381 Disable button should be an overlay of the build button not a separate button. Sorry, went ahead with the switch icon for now. Pause and play could be misunderstood as an action to pause and continue a build instead of disabling/enabling it. I might change the switch icon in the future, depending on user feedback. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12728) new column: Last successful artifacts?
Fred G closed JENKINS-12728 as Wont Fix new column: Last successful artifacts? Work on this issue can not be started without more user input. User did not respond in almost a year. Closing for now. Please re-open if necessary. Change By: Fred G (20/Jan/13 7:33 PM) Status: Open Closed Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15155) Show total number of tests in test column
Fred G resolved JENKINS-15155 as Fixed Show total number of tests in test column Fixed in version 1.6. Change By: Fred G (20/Jan/13 7:34 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15155) Show total number of tests in test column
Fred G started work on JENKINS-15155 Show total number of tests in test column Change By: Fred G (20/Jan/13 7:34 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16420) Invalid URL in left-hand menu entry of disk-usage plugin
Hakan Tandogan updated JENKINS-16420 Invalid URL in left-hand menu entry of disk-usage plugin Seems to be an issue similiar to JENKINS-12917 ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16421) gerrit-trigger UI elements 404 on jenkins 1.499
Erik LaBianca created JENKINS-16421 gerrit-trigger UI elements 404 on jenkins 1.499 Issue Type: Bug Affects Versions: current Assignee: rsandell Components: gerrit-trigger Created: 20/Jan/13 9:36 PM Description: It appears as if the jenkins plugin is somehow unable to register its URLS with jenkins correct. Clicking the link to retrigger a build or select builds to retrigger takes me to /jenkins/gerrit_manual_trigger, which is 404. Also, the retrigger icon, trying to load from /jenkins/plugin/gerrit-trigger/images/icon_retrigger24.png is also 404. The trigger does appear to work when configured from a job. I tried rebuilding the latest code from github and changing the jenkins-ci dependency to 1.480. By forcing the build to skip tests, I got it to compile but after installation the behavior is the same. Prior to upgrade to 2.7.0 + Jenkins 1.499 I had everything running with the same config with gerrit-trigger 2.5.2 and Jenkins 1.4.463. I'm not seeing anything gerrit-trigger related in the logs. I'm happy to help troubleshoot however I can, but I'm a bit at a loss where to start currently. Any ideas? Thanks! Environment: RHEL5, Sun Java 1.6.33, Jenkins 1.499 Project: Jenkins Priority: Major Reporter: Erik LaBianca This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15570) Coverage report includes classes that have been excluded from Jacoco analysis
Ognjen Bubalo commented on JENKINS-15570 Coverage report includes classes that have been excluded from Jacoco analysis Hi, Hopefully I'll implement this feature and release a new version in the next 2 days. Cheers, Ogi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16406) Environment variables
ping he updated JENKINS-16406 Environment variables Change By: ping he (21/Jan/13 1:02 AM) Attachment: env.png Attachment: env2.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16406) Environment variables
ping he commented on JENKINS-16406 Environment variables in attachments This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15751) Cannot escape dollar sign in Windows environment
Nick Grealy commented on JENKINS-15751 Cannot escape dollar sign in Windows environment Hi Gregory, Sorry for the late reply (I don't have access to a windows Jenkins instance at the moment), but I'll use a similar use case to Vincent's: User Story As a Jenkins user I want to use the environment variable name "win_sys_path" with a value "\\127.0.0.1\c$\WINDOWS" So that I can access a windows system folder from a remote computer. User Scenarios Global: Given a Jenkins Windows instance Given the environment variable "win_sys_path" with value "\\127.0.0.1\c$\WINDOWS" When I echo the variable "win_sys_path" Then the value should be "\\127.0.0.1\c" Given the environment variable "win_sys_path" with value "\\127.0.0.1\c\$\WINDOWS" When I echo the variable "win_sys_path" Then the value should be "\\127.0.0.1\c$\WINDOWS" Given the environment variable "win_sys_path" with value "\\127.0.0.1\c\\$\WINDOWS" When I echo the variable "win_sys_path" Then the value should be "\\127.0.0.1\c\$\WINDOWS" Hope that makes sense. Nick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15751) Cannot escape dollar sign in Windows environment
Nick Grealy commented on JENKINS-15751 Cannot escape dollar sign in Windows environment Update: ignore the "Global: Given a Jenkins Windows instance", this same functionality should apply on ALL operating systems (but in this case, specifically on Windows). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion
Nickolay Martinov commented on JENKINS-15156 Builds Disappear from Build History after Completion Does anyone know version where this bug wasnt introduced yet? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16422) Enabling 'Poll for posted deliveres' breaks the poll self method for all jobs
Mads Nielsen created JENKINS-16422 Enabling Poll for posted deliveres breaks the poll self method for all jobs Issue Type: Bug Affects Versions: current Assignee: Praqma Support Components: clearcase-ucm Created: 21/Jan/13 7:10 AM Project: Jenkins Priority: Major Reporter: Mads Nielsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
