[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-tabpanelfocusedCommentId=159693#comment-159693 ] Jaroslavas D. edited comment on JENKINS-12810 at 3/1/12 8:03 AM:

[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed

[ https://issues.jenkins-ci.org/browse/JENKINS-9104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159695#comment-159695 ] chanti vlad commented on JENKINS-9104: -- Jenkins mustn't kill mspdbsrv.exe to be able to

[JIRA] (JENKINS-3105) Configuration UI to disable process tree killer selectively

[ https://issues.jenkins-ci.org/browse/JENKINS-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159696#comment-159696 ] chanti vlad commented on JENKINS-3105: -- @mdonohue: I think it _does_ apply to enough

[JIRA] (JENKINS-11683) email-ext: user unknown ($PROJECT_DEFAULT_RECIPIENTS) exception

[ https://issues.jenkins-ci.org/browse/JENKINS-11683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159697#comment-159697 ] Niels Wegner commented on JENKINS-11683: According to the value displayed in the

[JIRA] (JENKINS-11683) email-ext: user unknown ($PROJECT_DEFAULT_RECIPIENTS) exception

[ https://issues.jenkins-ci.org/browse/JENKINS-11683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159697#comment-159697 ] Niels Wegner edited comment on JENKINS-11683 at 3/1/12 9:33 AM:

[JIRA] (JENKINS-9589) SSH sessions kept open by Subversion checkout

[ https://issues.jenkins-ci.org/browse/JENKINS-9589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159698#comment-159698 ] Stefan Moj commented on JENKINS-9589: - Did you resolve the issue or find a workaround?

[JIRA] (JENKINS-12943) Intermittent java.io.StreamCorruptedException: invalid type code: 4B when communicating with a slave

Pontus Edvardsson created JENKINS-12943: --- Summary: Intermittent java.io.StreamCorruptedException: invalid type code: 4B when communicating with a slave Key: JENKINS-12943 URL:

[JIRA] (JENKINS-12945) New breadcrumb: relative path should be resolved based on model-link's href

OHTAKE Tomohiro created JENKINS-12945: - Summary: New breadcrumb: relative path should be resolved based on model-link's href Key: JENKINS-12945 URL: https://issues.jenkins-ci.org/browse/JENKINS-12945

[JIRA] (JENKINS-12945) New breadcrumb: relative path should be resolved based on model-link's href

[ https://issues.jenkins-ci.org/browse/JENKINS-12945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-12945 started by OHTAKE Tomohiro. New breadcrumb: relative path should be resolved based on model-link's href

[JIRA] (JENKINS-12946) New breadcrumb: Next/Previous Build does not work

OHTAKE Tomohiro created JENKINS-12946: - Summary: New breadcrumb: Next/Previous Build does not work Key: JENKINS-12946 URL: https://issues.jenkins-ci.org/browse/JENKINS-12946 Project: Jenkins

[JIRA] (JENKINS-12947) update of Perforce plugin fails with IOException

robsimon created JENKINS-12947: -- Summary: update of Perforce plugin fails with IOException Key: JENKINS-12947 URL: https://issues.jenkins-ci.org/browse/JENKINS-12947 Project: Jenkins Issue

[JIRA] (JENKINS-12945) New breadcrumb: relative path should be resolved based on model-link's href

[ https://issues.jenkins-ci.org/browse/JENKINS-12945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159701#comment-159701 ] OHTAKE Tomohiro commented on JENKINS-12945: --- I have raised a pull request to fix

[JIRA] (JENKINS-12945) New breadcrumb: relative path should be resolved based on model-link's href

[ https://issues.jenkins-ci.org/browse/JENKINS-12945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-12945 stopped by OHTAKE Tomohiro. New breadcrumb: relative path should be resolved based on model-link's href

[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-tabpanelfocusedCommentId=159702#comment-159702 ] Jaroslavas D. commented on JENKINS-12810: - I don't really understood why it is JUnit

[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-tabpanelfocusedCommentId=159702#comment-159702 ] Jaroslavas D. edited comment on JENKINS-12810 at 3/1/12 1:14 PM:

[JIRA] (JENKINS-12929) Is it possible to have a QTP only plugin or perhaps enhance the QC plugin to do this?

[ https://issues.jenkins-ci.org/browse/JENKINS-12929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159703#comment-159703 ] Nathmie S commented on JENKINS-12929: - I have managed thus far to kick of test(s) and

[JIRA] (JENKINS-12223) Warnings trend graph (type distribution) dashboard portlet is very slow to display when # jobs in view 12 or so

[ https://issues.jenkins-ci.org/browse/JENKINS-12223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner resolved JENKINS-12223. --- Resolution: Fixed Warnings trend graph (type distribution) dashboard portlet is very

[JIRA] (JENKINS-10606) Support Matrix Builds

[ https://issues.jenkins-ci.org/browse/JENKINS-10606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159704#comment-159704 ] Andy Bigos commented on JENKINS-10606: -- Hi, Given the title of this issue - can I ask

[JIRA] (JENKINS-12949) Do not automatically convert post-split Hudson installation to Jenkins

Richard Mortimer created JENKINS-12949: -- Summary: Do not automatically convert post-split Hudson installation to Jenkins Key: JENKINS-12949 URL: https://issues.jenkins-ci.org/browse/JENKINS-12949

[JIRA] (JENKINS-12934) Subversion Tag plugin tries to copy from invalid source path

[ https://issues.jenkins-ci.org/browse/JENKINS-12934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Lillevold updated JENKINS-12934: -- Priority: Critical (was: Blocker) Description: Last week the subversion

[JIRA] (JENKINS-10606) Support Matrix Builds

[ https://issues.jenkins-ci.org/browse/JENKINS-10606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159706#comment-159706 ] Rob Petti commented on JENKINS-10606: - Your matrixruns might be running at the exact

[JIRA] (JENKINS-10606) Support Matrix Builds

[ https://issues.jenkins-ci.org/browse/JENKINS-10606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159707#comment-159707 ] Andy Bigos commented on JENKINS-10606: -- Yes - that was it. Thanks! I'd set all the

[JIRA] (JENKINS-10606) Support Matrix Builds

[ https://issues.jenkins-ci.org/browse/JENKINS-10606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159708#comment-159708 ] Rob Petti commented on JENKINS-10606: - Yeah, I've been thinking about how best to handle

[JIRA] (JENKINS-12947) update of Perforce plugin fails with IOException

[ https://issues.jenkins-ci.org/browse/JENKINS-12947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159709#comment-159709 ] Rob Petti commented on JENKINS-12947: - Updating without restarting isn't supported by

[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-tabpanelfocusedCommentId=159710#comment-159710 ] Bruno P. Kinoshita commented on JENKINS-12810: -- Your understanding is perfect,

[JIRA] (JENKINS-12938) MavenReporters always run, even if unneeded: MavenFingerprinter is slow

[ https://issues.jenkins-ci.org/browse/JENKINS-12938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Atwill updated JENKINS-12938: --- Description: The MavenFingerprinter MavenReporter should not run if fingerprinting the

[JIRA] (JENKINS-12912) URLTtrigger does not poll on jobs which are tied to disconnected slaves

[ https://issues.jenkins-ci.org/browse/JENKINS-12912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159712#comment-159712 ] gbois commented on JENKINS-12912: - The current behavior is to process polling on the target

[JIRA] (JENKINS-11783) SAXParser-related IllegalAccessError on svn update

[ https://issues.jenkins-ci.org/browse/JENKINS-11783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159713#comment-159713 ] Peter Lillevold commented on JENKINS-11783: --- I can confirm the same behavior using

[JIRA] (JENKINS-12950) pom.xml not deploying to Artifactory

[ https://issues.jenkins-ci.org/browse/JENKINS-12950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry Thome updated JENKINS-12950: -- I stumbled across someone else who ran into this issue. The work-around was to run 'mvn

[JIRA] (JENKINS-12951) Freestyle job 'Invoke Maven 3' build step can't find maven home for Maven installation installed from Apache Archives

Andrew Fannin created JENKINS-12951: --- Summary: Freestyle job 'Invoke Maven 3' build step can't find maven home for Maven installation installed from Apache Archives Key: JENKINS-12951 URL:

[JIRA] (JENKINS-12894) Building a scheme including multiple static library test targets fails under jenkins but works with xcodebuild from cli

[ https://issues.jenkins-ci.org/browse/JENKINS-12894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Héritier closed JENKINS-12894. - Building a scheme including multiple static library test targets fails under

[JIRA] (JENKINS-12651) Possibility to select whether to save build or not on m2release

[ https://issues.jenkins-ci.org/browse/JENKINS-12651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] teilo resolved JENKINS-12651. - Resolution: Duplicate Duplicate of JENKINS-12076 Possibility to select whether to

[JIRA] (JENKINS-4958) add switch for -DdryRun=true

[ https://issues.jenkins-ci.org/browse/JENKINS-4958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] teilo resolved JENKINS-4958. Resolution: Fixed fixed in 0.9.1 add switch for -DdryRun=true

[JIRA] (JENKINS-12895) automatically drop nexus stage if build fails

[ https://issues.jenkins-ci.org/browse/JENKINS-12895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159718#comment-159718 ] SCM/JIRA link daemon commented on JENKINS-12895: Code changed in jenkins

[JIRA] (JENKINS-12076) m2 Release Plugin lock builds

[ https://issues.jenkins-ci.org/browse/JENKINS-12076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-12076. Resolution: Fixed m2 Release Plugin lock builds

[JIRA] (JENKINS-12895) automatically drop nexus stage if build fails

[ https://issues.jenkins-ci.org/browse/JENKINS-12895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-12895. Resolution: Fixed automatically drop nexus stage if build fails

[JIRA] (JENKINS-10042) When closing stage failes the plugin causes an exception

[ https://issues.jenkins-ci.org/browse/JENKINS-10042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-10042. Resolution: Fixed When closing stage failes the plugin causes an

[JIRA] (JENKINS-10042) When closing stage failes the plugin causes an exception

[ https://issues.jenkins-ci.org/browse/JENKINS-10042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159719#comment-159719 ] SCM/JIRA link daemon commented on JENKINS-10042: Code changed in jenkins

[JIRA] (JENKINS-12076) m2 Release Plugin lock builds

[ https://issues.jenkins-ci.org/browse/JENKINS-12076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159720#comment-159720 ] SCM/JIRA link daemon commented on JENKINS-12076: Code changed in jenkins

[JIRA] (JENKINS-8082) git plugin multi-repo can't work

[ https://issues.jenkins-ci.org/browse/JENKINS-8082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159724#comment-159724 ] crwong commented on JENKINS-8082: - I am not sure I understand why this is marked as Won't

[JIRA] (JENKINS-12953) SVN Tag failing even though the Remote Module Location Tag Base URL values are correct

Suresh Kurra created JENKINS-12953: -- Summary: SVN Tag failing even though the Remote Module Location Tag Base URL values are correct Key: JENKINS-12953 URL: https://issues.jenkins-ci.org/browse/JENKINS-12953

[JIRA] (JENKINS-12952) Job stuck sending failure email -- perforce plugin

[ https://issues.jenkins-ci.org/browse/JENKINS-12952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159726#comment-159726 ] Rob Petti commented on JENKINS-12952: - Are all of your perforce-based jobs operable? As

[JIRA] (JENKINS-6681) Maven-generated site link gives 404

[ https://issues.jenkins-ci.org/browse/JENKINS-6681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159727#comment-159727 ] Peter Johnson commented on JENKINS-6681: I'm having this same issue with Jenkins

[JIRA] (JENKINS-12954) Configure accurev server per Jenkins node

pickgr1 created JENKINS-12954: - Summary: Configure accurev server per Jenkins node Key: JENKINS-12954 URL: https://issues.jenkins-ci.org/browse/JENKINS-12954 Project: Jenkins Issue Type: New

[JIRA] (JENKINS-12912) URLTtrigger does not poll on jobs which are tied to disconnected slaves

[ https://issues.jenkins-ci.org/browse/JENKINS-12912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159729#comment-159729 ] OHTAKE Tomohiro commented on JENKINS-12912: --- It is sufficient for me, but I think

[JIRA] (JENKINS-12955) Stylecop file report is blank

Marcus Bristol created JENKINS-12955: Summary: Stylecop file report is blank Key: JENKINS-12955 URL: https://issues.jenkins-ci.org/browse/JENKINS-12955 Project: Jenkins Issue Type: Bug

[JIRA] (JENKINS-12944) Env Inject Plugin doesn't substitute ${WORKSPACE} variable at all when used in 'Preparing an environment for the job'

[ https://issues.jenkins-ci.org/browse/JENKINS-12944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159731#comment-159731 ] SCM/JIRA link daemon commented on JENKINS-12944: Code changed in jenkins

[JIRA] (JENKINS-12956) Build all jobs that have not been built in N days

[ https://issues.jenkins-ci.org/browse/JENKINS-12956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Moncreaff updated JENKINS-12956: - Summary: Build all jobs that have not been built in N days (was: Build all jobs that

[JIRA] (JENKINS-12956) Build all jobs that have not been build in N days

Greg Moncreaff created JENKINS-12956: Summary: Build all jobs that have not been build in N days Key: JENKINS-12956 URL: https://issues.jenkins-ci.org/browse/JENKINS-12956 Project: Jenkins

[JIRA] (JENKINS-12957) check AJP request attribute value is null.

Yoshihito Fukuyama created JENKINS-12957: Summary: check AJP request attribute value is null. Key: JENKINS-12957 URL: https://issues.jenkins-ci.org/browse/JENKINS-12957 Project: Jenkins

[JIRA] (JENKINS-12957) check AJP request attribute value is null.

[ https://issues.jenkins-ci.org/browse/JENKINS-12957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yoshihito Fukuyama updated JENKINS-12957: - Priority: Minor (was: Major) check AJP request attribute value is null.

[JIRA] (JENKINS-12957) check AJP request attribute value is null.

[ https://issues.jenkins-ci.org/browse/JENKINS-12957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yoshihito Fukuyama updated JENKINS-12957: - Description: I used jenkins and apache httpd and mod_jk 1.2.32. Jenkins throws

[JIRA] (JENKINS-12958) Deleting an email address from Email Notifications configuration for build projects does not stop emails from being sent to deleted email address

Bryant Kwon created JENKINS-12958: - Summary: Deleting an email address from Email Notifications configuration for build projects does not stop emails from being sent to deleted email address Key: JENKINS-12958

[JIRA] (JENKINS-11618) Prototype 1.7 is missing the instance 'toJSON' method

[ https://issues.jenkins-ci.org/browse/JENKINS-11618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kohsuke Kawaguchi updated JENKINS-11618: Summary: Prototype 1.7 is missing the instance 'toJSON' method (was: Enabling

[JIRA] (JENKINS-11618) Prototype 1.7 is missing the instance 'toJSON' method

[ https://issues.jenkins-ci.org/browse/JENKINS-11618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159737#comment-159737 ] SCM/JIRA link daemon commented on JENKINS-11618: Code changed in jenkins

[JIRA] (JENKINS-11618) Prototype 1.7 is missing the instance 'toJSON' method

[ https://issues.jenkins-ci.org/browse/JENKINS-11618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159738#comment-159738 ] dogfood commented on JENKINS-11618: --- Integrated in