[JIRA] (JENKINS-13437) Gradle-Artifactory Integration should allow to specify separate repositories for release and snapshot deployment

Jochen Kemnade created JENKINS-13437: Summary: Gradle-Artifactory Integration should allow to specify separate repositories for release and snapshot deployment Key: JENKINS-13437 URL:

[JIRA] (JENKINS-12124) random NoClassDefFoundError: hudson/plugins/analysis/core/AbstractProjectAction - Not all jobs loaded

[ https://issues.jenkins-ci.org/browse/JENKINS-12124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161556#comment-161556 ] jacekw edited comment on JENKINS-12124 at 4/13/12 6:37 AM: ---

[JIRA] (JENKINS-13432) ec2 plugin - support for the new amazon instance types - especially medium

[ https://issues.jenkins-ci.org/browse/JENKINS-13432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-13432. Resolution: Fixed ec2 plugin - support for the new amazon instance

[JIRA] (JENKINS-13432) ec2 plugin - support for the new amazon instance types - especially medium

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

[JIRA] (JENKINS-13432) ec2 plugin - support for the new amazon instance types - especially medium

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

[JIRA] (JENKINS-13438) Open an issue when a build breaks

Rafael Tavares created JENKINS-13438: Summary: Open an issue when a build breaks Key: JENKINS-13438 URL: https://issues.jenkins-ci.org/browse/JENKINS-13438 Project: Jenkins Issue Type:

[JIRA] (JENKINS-13432) ec2 plugin - support for the new amazon instance types - especially medium

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

[JIRA] (JENKINS-13379) jenkins ver. 1.458 crash with analysis-collector 1.24

[ https://issues.jenkins-ci.org/browse/JENKINS-13379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] vjuranek resolved JENKINS-13379. Resolution: Duplicate Duplicates JENKINS-12970 jenkins ver. 1.458 crash with

[JIRA] (JENKINS-12970) NPE in disk-usage during jenkins startup

[ https://issues.jenkins-ci.org/browse/JENKINS-12970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161561#comment-161561 ] vjuranek commented on JENKINS-12970: I tried to reproduce and was able to reproduce only

[JIRA] (JENKINS-8107) Use Hudson login (already possible) and password (not yet possible) to release in maven

[ https://issues.jenkins-ci.org/browse/JENKINS-8107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161563#comment-161563 ] Sebastian Hegewald commented on JENKINS-8107: - ??Use Hudson login (already

[JIRA] (JENKINS-13440) Plugin uses only the first location in subversion SCM settings for scanning for ivy.xml.

Fedja Shtrom created JENKINS-13440: -- Summary: Plugin uses only the first location in subversion SCM settings for scanning for ivy.xml. Key: JENKINS-13440 URL: https://issues.jenkins-ci.org/browse/JENKINS-13440

[JIRA] (JENKINS-11922) Parametrised Build Trigger Plugin takes build params from the old build not from the current

[ https://issues.jenkins-ci.org/browse/JENKINS-11922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161564#comment-161564 ] Thomas Dingler commented on JENKINS-11922: -- I have the same problem and would like

[JIRA] (JENKINS-12404) Mercurial poller triggers new build if workspace doesn't exist

[ https://issues.jenkins-ci.org/browse/JENKINS-12404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161566#comment-161566 ] Aldo Brucale commented on JENKINS-12404: I'm getting the same behaviour for jobs

[JIRA] (JENKINS-9913) Concurrent builds getting batched/nodes not getting released when jobs are completed

[ https://issues.jenkins-ci.org/browse/JENKINS-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161568#comment-161568 ] Sergey Smirnov commented on JENKINS-9913: - Jenkins ver. 1.458 Still have problem:

[JIRA] (JENKINS-13416) On demand slave provisioning is starting all available slaves

[ https://issues.jenkins-ci.org/browse/JENKINS-13416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Meneguello updated JENKINS-13416: --- Attachment: jenkins-1.459.diff Description: I'm using on demand slaves (on

[JIRA] (JENKINS-12970) NPE in disk-usage during jenkins startup

[ https://issues.jenkins-ci.org/browse/JENKINS-12970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161569#comment-161569 ] Bernd Krumböck commented on JENKINS-12970: -- I confirm: Dashboard view plugin 2.2

[JIRA] (JENKINS-10674) Publish over CIFS performance is slow

[ https://issues.jenkins-ci.org/browse/JENKINS-10674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161570#comment-161570 ] Edwin Renner commented on JENKINS-10674: i tried it with the package stated above,

[JIRA] (JENKINS-10674) Publish over CIFS performance is slow

[ https://issues.jenkins-ci.org/browse/JENKINS-10674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161570#comment-161570 ] Edwin Renner edited comment on JENKINS-10674 at 4/13/12 12:16 PM:

[JIRA] (JENKINS-13441) Slave status information shouldn't be stored in main config file

Andreas Kotes created JENKINS-13441: --- Summary: Slave status information shouldn't be stored in main config file Key: JENKINS-13441 URL: https://issues.jenkins-ci.org/browse/JENKINS-13441 Project:

[JIRA] (JENKINS-13441) Slave status information shouldn't be stored in main config file

[ https://issues.jenkins-ci.org/browse/JENKINS-13441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Kotes updated JENKINS-13441: Component/s: master-slave Slave status information shouldn't be stored in main

[JIRA] (JENKINS-13443) Start using the concept of template or group for jobs, so we can edit a simple configuration for a group of jobs.

Rafael Chies created JENKINS-13443: -- Summary: Start using the concept of template or group for jobs, so we can edit a simple configuration for a group of jobs. Key: JENKINS-13443 URL:

[JIRA] (JENKINS-12970) NPE in disk-usage during jenkins startup

[ https://issues.jenkins-ci.org/browse/JENKINS-12970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161575#comment-161575 ] vjuranek commented on JENKINS-12970: Please note, that this is just a fix which allows

[JIRA] (JENKINS-13411) Klocwork XML output is deprecated

[ https://issues.jenkins-ci.org/browse/JENKINS-13411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161576#comment-161576 ] Jacob Larfors commented on JENKINS-13411: - Hello again, I have contacted Klocwork

[JIRA] (JENKINS-12970) NPE in disk-usage during jenkins startup

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

[JIRA] (JENKINS-13381) Jenkins stopped after updating plugins

[ https://issues.jenkins-ci.org/browse/JENKINS-13381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161578#comment-161578 ] vjuranek commented on JENKINS-13381: If you don't want to remove analysis-collector,

[JIRA] (JENKINS-13411) Klocwork XML output is deprecated

[ https://issues.jenkins-ci.org/browse/JENKINS-13411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161580#comment-161580 ] Krzysztof Malinowski commented on JENKINS-13411: Great, but CTO does not

[JIRA] (JENKINS-11889) Suspended slave do not start accepting tasks when policy changed

[ https://issues.jenkins-ci.org/browse/JENKINS-11889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161581#comment-161581 ] Nick Parrish commented on JENKINS-11889: I am seeing this too. It is very annoying.

[JIRA] (JENKINS-11889) Suspended slave do not start accepting tasks when policy changed

[ https://issues.jenkins-ci.org/browse/JENKINS-11889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161582#comment-161582 ] Nick Parrish commented on JENKINS-11889: Deleting and re-creating the slave was the

[JIRA] (JENKINS-13444) Workspace Cleanup plugin seems to be following symlinks and deleting files outside its workspace

Gary Yund created JENKINS-13444: --- Summary: Workspace Cleanup plugin seems to be following symlinks and deleting files outside its workspace Key: JENKINS-13444 URL: https://issues.jenkins-ci.org/browse/JENKINS-13444

[JIRA] (JENKINS-13444) Workspace Cleanup plugin seems to be following symlinks and deleting files outside its workspace

[ https://issues.jenkins-ci.org/browse/JENKINS-13444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161584#comment-161584 ] Gary Yund commented on JENKINS-13444: - I had a similar issue with the SVN plugin a while

[JIRA] (JENKINS-13445) join trigger doesn't work in a promotion process

Brian Murrell created JENKINS-13445: --- Summary: join trigger doesn't work in a promotion process Key: JENKINS-13445 URL: https://issues.jenkins-ci.org/browse/JENKINS-13445 Project: Jenkins

[JIRA] (JENKINS-13446) Dependency graph points to localhost:8080

Tim Landscheidt created JENKINS-13446: - Summary: Dependency graph points to localhost:8080 Key: JENKINS-13446 URL: https://issues.jenkins-ci.org/browse/JENKINS-13446 Project: Jenkins

[JIRA] (JENKINS-13447) Show link to promotion jobs archived artifacts

[ https://issues.jenkins-ci.org/browse/JENKINS-13447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devin Linnington updated JENKINS-13447: --- Description: I have a script that copies some QA test results (simple txt files)

[JIRA] (JENKINS-13446) Dependency graph points to localhost:8080

[ https://issues.jenkins-ci.org/browse/JENKINS-13446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161585#comment-161585 ] Richard Mortimer commented on JENKINS-13446:

[JIRA] (JENKINS-13446) Dependency graph points to localhost:8080

[ https://issues.jenkins-ci.org/browse/JENKINS-13446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161586#comment-161586 ] Richard Mortimer commented on JENKINS-13446: I think that this is likely cause

[JIRA] (JENKINS-13447) Show link to promotion jobs archived artifacts

[ https://issues.jenkins-ci.org/browse/JENKINS-13447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161587#comment-161587 ] Devin Linnington commented on JENKINS-13447: The work around for this is to use

[JIRA] (JENKINS-13448) Guice injector failure can cause failure of whole Jenkins

vjuranek created JENKINS-13448: -- Summary: Guice injector failure can cause failure of whole Jenkins Key: JENKINS-13448 URL: https://issues.jenkins-ci.org/browse/JENKINS-13448 Project: Jenkins

[JIRA] (JENKINS-13449) version number of ipa and dSYM.zip is incorrect

Joshua Moody created JENKINS-13449: -- Summary: version number of ipa and dSYM.zip is incorrect Key: JENKINS-13449 URL: https://issues.jenkins-ci.org/browse/JENKINS-13449 Project: Jenkins

[JIRA] (JENKINS-13227) CVS plugin 2.1 does not detect changes

[ https://issues.jenkins-ci.org/browse/JENKINS-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161588#comment-161588 ] Amir Isfy commented on JENKINS-13227: - I am having the same exact problem with the

[JIRA] (JENKINS-13449) version number of ipa and dSYM.zip is incorrect

[ https://issues.jenkins-ci.org/browse/JENKINS-13449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161589#comment-161589 ] Joshua Moody commented on JENKINS-13449: Using ${BUILD_NUMBER} in the Marketing and

[JIRA] (JENKINS-13450) Store the output it tried to parse

Bruno P. Kinoshita created JENKINS-13450: Summary: Store the output it tried to parse Key: JENKINS-13450 URL: https://issues.jenkins-ci.org/browse/JENKINS-13450 Project: Jenkins

[JIRA] (JENKINS-13451) Enhance tap-plugin UI

Bruno P. Kinoshita created JENKINS-13451: Summary: Enhance tap-plugin UI Key: JENKINS-13451 URL: https://issues.jenkins-ci.org/browse/JENKINS-13451 Project: Jenkins Issue Type:

[JIRA] (JENKINS-13452) Include an option to include TAP Stream in the console output or somewhere in Jenkins UI

Bruno P. Kinoshita created JENKINS-13452: Summary: Include an option to include TAP Stream in the console output or somewhere in Jenkins UI Key: JENKINS-13452 URL: