[JIRA] (JENKINS-12427) BuildResultTrigger Plug-in not triggering job

[ https://issues.jenkins-ci.org/browse/JENKINS-12427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois resolved JENKINS-12427. - Resolution: Not A Defect According the config files, there are no build results to check. Therefore, yo

[JIRA] (JENKINS-12427) BuildResultTrigger Plug-in not triggering job

[ https://issues.jenkins-ci.org/browse/JENKINS-12427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois reassigned JENKINS-12427: --- Assignee: gbois > BuildResultTrigger Plug-in not triggering job >

[JIRA] (JENKINS-9084) Regression in jenkins .401 maven plugin - deploy to repository post-task

[ https://issues.jenkins-ci.org/browse/JENKINS-9084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159195#comment-159195 ] manvendra tomar commented on JENKINS-9084: -- Failed to execute goal org.apache.maven

[JIRA] (JENKINS-12810) JUnit test results are getting wrongly attached to all the test cases

[ https://issues.jenkins-ci.org/browse/JENKINS-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159194#comment-159194 ] Bruno P. Kinoshita commented on JENKINS-12810: -- Hello Vignesh, thanks for the q

[JIRA] (JENKINS-11894) All tests {test Methods} of TestNG, belonging to the same class are shown as "FAILURE", if just one of the test is a failure

[ https://issues.jenkins-ci.org/browse/JENKINS-11894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159193#comment-159193 ] Bruno P. Kinoshita commented on JENKINS-11894: -- Hey Venu. The fix is done in

[JIRA] (JENKINS-11894) All tests {test Methods} of TestNG, belonging to the same class are shown as "FAILURE", if just one of the test is a failure

[ https://issues.jenkins-ci.org/browse/JENKINS-11894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-11894 stopped by Bruno P. Kinoshita. > All tests {test Methods} of TestNG, belonging to the same class are shown as > "FAILURE", if just one of the tes

[JIRA] (JENKINS-12810) JUnit test results are getting wrongly attached to all the test cases

[ https://issues.jenkins-ci.org/browse/JENKINS-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159192#comment-159192 ] Vignesh Senapathy commented on JENKINS-12810: - Hi Bruno, I am using JUnit proje

[JIRA] (JENKINS-11894) All tests {test Methods} of TestNG, belonging to the same class are shown as "FAILURE", if just one of the test is a failure

[ https://issues.jenkins-ci.org/browse/JENKINS-11894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159191#comment-159191 ] SCM/JIRA link daemon commented on JENKINS-11894: Code changed in jenkins Use

[JIRA] (JENKINS-12806) Perforce Plugin causes config page to throw error if workspace mapping exceeds 2974 bytes

[ https://issues.jenkins-ci.org/browse/JENKINS-12806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Petti updated JENKINS-12806: Priority: Minor (was: Major) > Perforce Plugin causes config page to throw error if workspac

[JIRA] (JENKINS-12806) Perforce Plugin causes config page to throw error if workspace mapping exceeds 2974 bytes

[ https://issues.jenkins-ci.org/browse/JENKINS-12806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159190#comment-159190 ] Rob Petti commented on JENKINS-12806: - I'm able to reproduce the problem, but clicking o

[JIRA] (JENKINS-12810) JUnit test results are getting wrongly attached to all the test cases

[ https://issues.jenkins-ci.org/browse/JENKINS-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159189#comment-159189 ] Bruno P. Kinoshita commented on JENKINS-12810: -- Hi Vignesh! Glad to hear that

[JIRA] (JENKINS-12806) Perforce Plugin causes config page to throw error if workspace mapping exceeds 2974 bytes

[ https://issues.jenkins-ci.org/browse/JENKINS-12806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159188#comment-159188 ] Mike Henderson commented on JENKINS-12806: -- I get a "Invalid mapping:" followed by

[JIRA] (JENKINS-12806) Perforce Plugin causes config page to throw error if workspace mapping exceeds 2974 bytes

[ https://issues.jenkins-ci.org/browse/JENKINS-12806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Petti updated JENKINS-12806: Assignee: Rob Petti > Perforce Plugin causes config page to throw error if workspace mapping

[JIRA] (JENKINS-12806) Perforce Plugin causes config page to throw error if workspace mapping exceeds 2974 bytes

[ https://issues.jenkins-ci.org/browse/JENKINS-12806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159187#comment-159187 ] Rob Petti commented on JENKINS-12806: - Can you post the parsing error?

[JIRA] (JENKINS-12742) XML Reader feature

[ https://issues.jenkins-ci.org/browse/JENKINS-12742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159186#comment-159186 ] Joshua Niehus edited comment on JENKINS-12742 at 2/17/12 12:06 AM: ---

[JIRA] (JENKINS-12742) XML Reader feature

[ https://issues.jenkins-ci.org/browse/JENKINS-12742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159186#comment-159186 ] Joshua Niehus commented on JENKINS-12742: - I extended the token macro plugin on my f

[JIRA] (JENKINS-12809) Injecting from file removes backslashes on ${WORKSPACE}

[ https://issues.jenkins-ci.org/browse/JENKINS-12809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois closed JENKINS-12809. --- Resolution: Not A Defect I think the problem is due to this action echo AAAFILEVAR=${WORKSPACE} > temp.conf

[JIRA] (JENKINS-12814) CLI doesn't support upgrading Jenkins itself

apgray created JENKINS-12814: Summary: CLI doesn't support upgrading Jenkins itself Key: JENKINS-12814 URL: https://issues.jenkins-ci.org/browse/JENKINS-12814 Project: Jenkins Issue Type: Bug

[JIRA] (JENKINS-12037) CLI - I/O error in channel Chunked connection/Unexpected termination of the channel - still occurring in Jenkins 1.449

[ https://issues.jenkins-ci.org/browse/JENKINS-12037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159184#comment-159184 ] Richard Mortimer commented on JENKINS-12037: I'm still max'd out with $dayjob an

[JIRA] (JENKINS-7733) System Message - Doesnt appear on any view other than the default view

[ https://issues.jenkins-ci.org/browse/JENKINS-7733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159183#comment-159183 ] dogfood commented on JENKINS-7733: -- Integrated in !http://ci.jenkins-ci.org/images/16x16/blu

[JIRA] (JENKINS-11926) Warnings plugin does not work on a slave

[ https://issues.jenkins-ci.org/browse/JENKINS-11926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159182#comment-159182 ] torbent commented on JENKINS-11926: --- Wild guesses; maybe helpful, maybe confusing: * Permi

[JIRA] (JENKINS-12788) Missing variables when executing EnvInject script

[ https://issues.jenkins-ci.org/browse/JENKINS-12788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois resolved JENKINS-12788. - Resolution: Fixed > Missing variables when executing EnvInject script > ---

[JIRA] (JENKINS-12788) Missing variables when executing EnvInject script

[ https://issues.jenkins-ci.org/browse/JENKINS-12788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159181#comment-159181 ] SCM/JIRA link daemon commented on JENKINS-12788: Code changed in jenkins Use

[JIRA] (JENKINS-12813) Resolving variable that does not exist

Jason May created JENKINS-12813: --- Summary: Resolving variable that does not exist Key: JENKINS-12813 URL: https://issues.jenkins-ci.org/browse/JENKINS-12813 Project: Jenkins Issue Type: Improve

[JIRA] (JENKINS-4500) Make it possible to select a node to do the release on

[ https://issues.jenkins-ci.org/browse/JENKINS-4500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] domi resolved JENKINS-4500. --- Resolution: Fixed > Make it possible to select a node to do the release on > ---

[JIRA] (JENKINS-4690) Be able to arbitrary paramterize m2 releases

[ https://issues.jenkins-ci.org/browse/JENKINS-4690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] domi resolved JENKINS-4690. --- Resolution: Fixed > Be able to arbitrary paramterize m2 releases > -

[JIRA] (JENKINS-12812) dryRun switch failes

[ https://issues.jenkins-ci.org/browse/JENKINS-12812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] domi reassigned JENKINS-12812: -- Assignee: domi (was: teilo) > dryRun switch failes > > > Ke

[JIRA] (JENKINS-10127) M2 Release plugin ignores parameters from a parameterized build

[ https://issues.jenkins-ci.org/browse/JENKINS-10127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] domi resolved JENKINS-10127. Resolution: Fixed > M2 Release plugin ignores parameters from a parameterized build > ---

[JIRA] (JENKINS-12812) dryRun switch failes

domi created JENKINS-12812: -- Summary: dryRun switch failes Key: JENKINS-12812 URL: https://issues.jenkins-ci.org/browse/JENKINS-12812 Project: Jenkins Issue Type: Bug Components: m2release

[JIRA] (JENKINS-1144) email-ext plugin causes NullPointerException when sending email for successful build

[ https://issues.jenkins-ci.org/browse/JENKINS-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitesh Shakya reopened JENKINS-1144: Assignee: abayer (was: kdsweeney) I am having similar issue again can you help me?

[JIRA] (JENKINS-1144) email-ext plugin causes NullPointerException when sending email for successful build

[ https://issues.jenkins-ci.org/browse/JENKINS-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159179#comment-159179 ] Nitesh Shakya commented on JENKINS-1144: I have following specification details Jenk

[JIRA] (JENKINS-1144) email-ext plugin causes NullPointerException when sending email for successful build

[ https://issues.jenkins-ci.org/browse/JENKINS-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159178#comment-159178 ] Nitesh Shakya commented on JENKINS-1144: I am using a new version of jenkins and stil

[JIRA] (JENKINS-12811) Pick the default resolution for the target when none is specified

[ https://issues.jenkins-ci.org/browse/JENKINS-12811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159177#comment-159177 ] Christopher Orr commented on JENKINS-12811: --- Default skin (i.e. resolution) is det

[JIRA] (JENKINS-12811) Pick the default resolution for the target when none is specified

Jørgen Tjernø created JENKINS-12811: --- Summary: Pick the default resolution for the target when none is specified Key: JENKINS-12811 URL: https://issues.jenkins-ci.org/browse/JENKINS-12811 Project: J

[JIRA] (JENKINS-12810) JUnit test results are getting wrongly attached to all the test cases

Vignesh Senapathy created JENKINS-12810: --- Summary: JUnit test results are getting wrongly attached to all the test cases Key: JENKINS-12810 URL: https://issues.jenkins-ci.org/browse/JENKINS-12810

[JIRA] (JENKINS-12806) Perforce Plugin causes config page to throw error if workspace mapping exceeds 2974 bytes

[ https://issues.jenkins-ci.org/browse/JENKINS-12806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159176#comment-159176 ] Mike Henderson commented on JENKINS-12806: -- If I remove security by allowing everyo

[JIRA] (JENKINS-12809) Injecting from file removes backslashes on ${WORKSPACE}

[ https://issues.jenkins-ci.org/browse/JENKINS-12809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159175#comment-159175 ] pixman20 commented on JENKINS-12809: The current workaround appears to be manually defin

[JIRA] (JENKINS-12809) Injecting from file removes backslashes on ${WORKSPACE}

pixman20 created JENKINS-12809: -- Summary: Injecting from file removes backslashes on ${WORKSPACE} Key: JENKINS-12809 URL: https://issues.jenkins-ci.org/browse/JENKINS-12809 Project: Jenkins Issu

[JIRA] (JENKINS-12808) cobertura-maven-plugin: cannot be deactivated + fails with NullPointerException + version 2.5.1 cannot be overwritten

[ https://issues.jenkins-ci.org/browse/JENKINS-12808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159174#comment-159174 ] Marco Schulze commented on JENKINS-12808: - I found out how to make the 2nd surefire-

[JIRA] (JENKINS-11622) ChannelPinger fails while Free Swap Space checker is running on Windows Slaves

[ https://issues.jenkins-ci.org/browse/JENKINS-11622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159173#comment-159173 ] Sam Talebbeik edited comment on JENKINS-11622 at 2/16/12 8:05 PM:

[JIRA] (JENKINS-12808) cobertura-maven-plugin: cannot be deactivated + fails with NullPointerException + version 2.5.1 cannot be overwritten

Marco Schulze created JENKINS-12808: --- Summary: cobertura-maven-plugin: cannot be deactivated + fails with NullPointerException + version 2.5.1 cannot be overwritten Key: JENKINS-12808 URL: https://issues.jenkins

[JIRA] (JENKINS-11622) ChannelPinger fails while Free Swap Space checker is running on Windows Slaves

[ https://issues.jenkins-ci.org/browse/JENKINS-11622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159173#comment-159173 ] Sam Talebbeik commented on JENKINS-11622: - One more piece of information. This issue

[JIRA] (JENKINS-12807) CVS plugin throwing Exception every time

Mark Trinh created JENKINS-12807: Summary: CVS plugin throwing Exception every time Key: JENKINS-12807 URL: https://issues.jenkins-ci.org/browse/JENKINS-12807 Project: Jenkins Issue Type: Bug

[JIRA] (JENKINS-12806) Perforce Plugin causes config page to throw error if workspace mapping exceeds 2974 bytes

Mike Henderson created JENKINS-12806: Summary: Perforce Plugin causes config page to throw error if workspace mapping exceeds 2974 bytes Key: JENKINS-12806 URL: https://issues.jenkins-ci.org/browse/JENKINS-128

[JIRA] (JENKINS-11926) Warnings plugin does not work on a slave

[ https://issues.jenkins-ci.org/browse/JENKINS-11926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159172#comment-159172 ] Massimo Rossello commented on JENKINS-11926: Ok, I will try to parse your attach

[JIRA] (JENKINS-4714) Login into hudson failed from IE6/8 (hudson own user database)

[ https://issues.jenkins-ci.org/browse/JENKINS-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159171#comment-159171 ] evernat commented on JENKINS-4714: -- @wohauser And I have not reproduced the issue using "IE

[JIRA] (JENKINS-12805) Let Jenkins user to stop/start/restart Selenium grid server (hub)

Tetiana Tvardovska created JENKINS-12805: Summary: Let Jenkins user to stop/start/restart Selenium grid server (hub) Key: JENKINS-12805 URL: https://issues.jenkins-ci.org/browse/JENKINS-12805

[JIRA] (JENKINS-12184) role management or view configuration leads to server Error 500, and the configuration works in memory but not in Jenkins's config.xml

[ https://issues.jenkins-ci.org/browse/JENKINS-12184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159170#comment-159170 ] pixman20 edited comment on JENKINS-12184 at 2/16/12 5:21 PM: - I

[JIRA] (JENKINS-12184) role management or view configuration leads to server Error 500, and the configuration works in memory but not in Jenkins's config.xml

[ https://issues.jenkins-ci.org/browse/JENKINS-12184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159170#comment-159170 ] pixman20 commented on JENKINS-12184: I have a similar issue that is occurring. I'm not

[JIRA] (JENKINS-8159) hudson debian pkg install failed on ubuntu 10.04 LTS due to java-virtual-machine dependency

[ https://issues.jenkins-ci.org/browse/JENKINS-8159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] evernat resolved JENKINS-8159. -- Resolution: Fixed finally fixed according to the last comment > hudson debian pkg ins

[JIRA] (JENKINS-11926) Warnings plugin does not work on a slave

[ https://issues.jenkins-ci.org/browse/JENKINS-11926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159168#comment-159168 ] Ulli Hafner edited comment on JENKINS-11926 at 2/16/12 5:11 PM: --

[JIRA] (JENKINS-11926) Warnings plugin does not work on a slave

[ https://issues.jenkins-ci.org/browse/JENKINS-11926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner updated JENKINS-11926: -- Attachment: issue11926.txt Massimo, I think that the problem must be somewhere else. Maybe th

[JIRA] (JENKINS-9041) Analysis Core / SSL Problem

[ https://issues.jenkins-ci.org/browse/JENKINS-9041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159167#comment-159167 ] recampbell commented on JENKINS-9041: - I can confirm this solves the issue for me as well

[JIRA] (JENKINS-12390) Jira plugin cannot be configured to connect to Atlassian on demand instances

[ https://issues.jenkins-ci.org/browse/JENKINS-12390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159166#comment-159166 ] Henry Cavillones commented on JENKINS-12390: This seems to be an easy fix..Be ni

[JIRA] (JENKINS-12280) Warnings plugin does strange things with a custom parser

[ https://issues.jenkins-ci.org/browse/JENKINS-12280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159165#comment-159165 ] torbent commented on JENKINS-12280: --- Sorry about the delay. Just checked. Running Jenkins

[JIRA] (JENKINS-11926) Warnings plugin does not work on a slave

[ https://issues.jenkins-ci.org/browse/JENKINS-11926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159164#comment-159164 ] Massimo Rossello edited comment on JENKINS-11926 at 2/16/12 2:05 PM: -

[JIRA] (JENKINS-11926) Warnings plugin does not work on a slave

[ https://issues.jenkins-ci.org/browse/JENKINS-11926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159164#comment-159164 ] Massimo Rossello commented on JENKINS-11926: Hi, I confirm that the Windows mast

[JIRA] (JENKINS-12804) Promote "When the following upstream promotions are promoted" does not happen

Ed Randall created JENKINS-12804: Summary: Promote "When the following upstream promotions are promoted" does not happen Key: JENKINS-12804 URL: https://issues.jenkins-ci.org/browse/JENKINS-12804 Pro

[JIRA] (JENKINS-11749) Included regions feature for GitSCM plugin

[ https://issues.jenkins-ci.org/browse/JENKINS-11749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159163#comment-159163 ] Gregory Pakosz edited comment on JENKINS-11749 at 2/16/12 1:19 PM: ---

[JIRA] (JENKINS-11749) Included regions feature for GitSCM plugin

[ https://issues.jenkins-ci.org/browse/JENKINS-11749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159163#comment-159163 ] Gregory Pakosz commented on JENKINS-11749: -- I would love to see this added to GitSC

[JIRA] (JENKINS-12685) There is no way to escape a $ so that it can be used without an exception

[ https://issues.jenkins-ci.org/browse/JENKINS-12685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sogabe resolved JENKINS-12685. -- Resolution: Fixed > There is no way to escape a $ so that it can be used without an exception > -

[JIRA] (JENKINS-12803) Installing plugin (without restarting) is broken with other non-refreshable extension.

[ https://issues.jenkins-ci.org/browse/JENKINS-12803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159162#comment-159162 ] Gavriil Konovalenko commented on JENKINS-12803: --- In the code, I see that Exten

[JIRA] (JENKINS-12802) Initial select box validation fails when default value is provided.

[ https://issues.jenkins-ci.org/browse/JENKINS-12802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159161#comment-159161 ] Ben Ripkens commented on JENKINS-12802: --- I should note that the validation is done two

[JIRA] (JENKINS-12803) Installing plugin (without restarting) is broken with other non-refreshable extension.

Gavriil Konovalenko created JENKINS-12803: - Summary: Installing plugin (without restarting) is broken with other non-refreshable extension. Key: JENKINS-12803 URL: https://issues.jenkins-ci.org/browse/JENK

[JIRA] (JENKINS-12802) Initial select box validation fails when default value is provided.

Ben Ripkens created JENKINS-12802: - Summary: Initial select box validation fails when default value is provided. Key: JENKINS-12802 URL: https://issues.jenkins-ci.org/browse/JENKINS-12802 Project: Jen

[JIRA] (JENKINS-12761) tfs plugin :failed to record scm polling

[ https://issues.jenkins-ci.org/browse/JENKINS-12761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-12761 stopped by jlin sai. > tfs plugin :failed to record scm polling > - > > Key: JENKINS-1276

[JIRA] (JENKINS-12761) tfs plugin :failed to record scm polling

[ https://issues.jenkins-ci.org/browse/JENKINS-12761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-12761 started by drewrm. > tfs plugin :failed to record scm polling > - > > Key: JENKINS-12761

[JIRA] (JENKINS-12801) When there are 2 PMD warnings on 1 line the Jenkins report does only report 1

Cees Bos created JENKINS-12801: -- Summary: When there are 2 PMD warnings on 1 line the Jenkins report does only report 1 Key: JENKINS-12801 URL: https://issues.jenkins-ci.org/browse/JENKINS-12801 Project:

[JIRA] (JENKINS-1519) PMD: plugin tries to read files from master in stead of slave

[ https://issues.jenkins-ci.org/browse/JENKINS-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cees Bos closed JENKINS-1519. - Resolution: Fixed This is fixed a long time ago > PMD: plugin tries to read files from

[JIRA] (JENKINS-12800) Can't add xcodebuild parameters including whitespace

Sven Weidauer created JENKINS-12800: --- Summary: Can't add xcodebuild parameters including whitespace Key: JENKINS-12800 URL: https://issues.jenkins-ci.org/browse/JENKINS-12800 Project: Jenkins

[JIRA] (JENKINS-12799) When project configuration is changed, Promoted Builds Plugin continues to use "old" configuration data

[ https://issues.jenkins-ci.org/browse/JENKINS-12799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ed Randall updated JENKINS-12799: - Attachment: jenkins-job-promotion-config.png > When project configuration is changed, Promo

[JIRA] (JENKINS-12799) When project configuration is changed, Promoted Builds Plugin continues to use "old" configuration data

Ed Randall created JENKINS-12799: Summary: When project configuration is changed, Promoted Builds Plugin continues to use "old" configuration data Key: JENKINS-12799 URL: https://issues.jenkins-ci.org/browse/JENKI

[JIRA] (JENKINS-12688) Build hangs on Windows 2008 x64 slave

[ https://issues.jenkins-ci.org/browse/JENKINS-12688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159159#comment-159159 ] Costin Caraivan commented on JENKINS-12688: --- Upgraded to 1.450, same issue.

[JIRA] (JENKINS-12688) Build hangs on Windows 2008 x64 slave

[ https://issues.jenkins-ci.org/browse/JENKINS-12688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Costin Caraivan updated JENKINS-12688: -- Environment: Jenkins 1.437 and 1.450 Master - Windows 2008 x64, Java 1.6.0_29 Slave -

[JIRA] (JENKINS-12798) Plugin does not generate test-reports

Robert Labus created JENKINS-12798: -- Summary: Plugin does not generate test-reports Key: JENKINS-12798 URL: https://issues.jenkins-ci.org/browse/JENKINS-12798 Project: Jenkins Issue Type: Bu

[JIRA] (JENKINS-12797) "Don't Keep this build forever" button doesn't work on matrix job and prevent removing old build

stibbons created JENKINS-12797: -- Summary: "Don't Keep this build forever" button doesn't work on matrix job and prevent removing old build Key: JENKINS-12797 URL: https://issues.jenkins-ci.org/browse/JENKINS-12797

[JIRA] (JENKINS-12797) "Don't Keep this build forever" button doesn't work on some matrix job and prevent removing old build

[ https://issues.jenkins-ci.org/browse/JENKINS-12797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stibbons updated JENKINS-12797: --- Summary: "Don't Keep this build forever" button doesn't work on some matrix job and prevent removin

[JIRA] (JENKINS-12796) support templating build steps

[ https://issues.jenkins-ci.org/browse/JENKINS-12796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guy Rozendorn closed JENKINS-12796. --- Resolution: Cannot Reproduce Didn't see the option before. it works. > sup

[JIRA] (JENKINS-7883) Stopped (as opposed to terminated) slaves are counted against the active instance count for the purpose of launching; can prevent launching of instances

[ https://issues.jenkins-ci.org/browse/JENKINS-7883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159157#comment-159157 ] francis Upton commented on JENKINS-7883: @akostadinov - please open a new JIRA reques

[JIRA] (JENKINS-12796) support templating build steps

Guy Rozendorn created JENKINS-12796: --- Summary: support templating build steps Key: JENKINS-12796 URL: https://issues.jenkins-ci.org/browse/JENKINS-12796 Project: Jenkins Issue Type: New Fea

[JIRA] (JENKINS-7883) Stopped (as opposed to terminated) slaves are counted against the active instance count for the purpose of launching; can prevent launching of instances

[ https://issues.jenkins-ci.org/browse/JENKINS-7883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159156#comment-159156 ] akostadinov commented on JENKINS-7883: -- It's important to count only jenkins instances b

[JIRA] (JENKINS-9939) Publisher hudson.tasks.Mailer aborted due to exception

[ https://issues.jenkins-ci.org/browse/JENKINS-9939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159155#comment-159155 ] Matti Linnanvuori commented on JENKINS-9939: I got the Mailer NullPointException

[JIRA] (JENKINS-12781) Jenkins hangs after printing Recording test results

[ https://issues.jenkins-ci.org/browse/JENKINS-12781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159154#comment-159154 ] Matti Linnanvuori commented on JENKINS-12781: - When I took the remote node offli

[JIRA] (JENKINS-12781) Jenkins hangs after printing Recording test results

[ https://issues.jenkins-ci.org/browse/JENKINS-12781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159152#comment-159152 ] Matti Linnanvuori commented on JENKINS-12781: - I started the job again after sto

[JIRA] (JENKINS-12669) ec2 plugin fails to launch slave with "The instance ID 'i-xxxx' does not exist" about 50% of the time

[ https://issues.jenkins-ci.org/browse/JENKINS-12669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159153#comment-159153 ] Sam He commented on JENKINS-12669: -- I always encounter this issue when I have > 2 EC Region

[JIRA] (JENKINS-12598) In 2.0 update you need to specify branch for every module

[ https://issues.jenkins-ci.org/browse/JENKINS-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159151#comment-159151 ] Ulli Hafner commented on JENKINS-12598: --- I think that would be a good idea. This will

[JIRA] (JENKINS-12795) Log/Report link in Job page is broken when Jenkins is started with a specific prefix

Jose Sa created JENKINS-12795: - Summary: Log/Report link in Job page is broken when Jenkins is started with a specific prefix Key: JENKINS-12795 URL: https://issues.jenkins-ci.org/browse/JENKINS-12795 Pro

[JIRA] (JENKINS-12793) Why the Post Steps and Post-build Actions are not executed after the build finished

[ https://issues.jenkins-ci.org/browse/JENKINS-12793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner updated JENKINS-12793: -- Assignee: (was: Ulli Hafner) Component/s: postbuild-task (was:

[JIRA] (JENKINS-12693) urltrigger cannot start: claims "bad major version at offset=6"

[ https://issues.jenkins-ci.org/browse/JENKINS-12693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois closed JENKINS-12693. --- Resolution: Won't Fix Unfortunately, URLTrigger have to run on Java6+. Therefore, Java5 is not supported.