[JIRA] [delivery-pipeline-plugin] (JENKINS-26210) Configure Jobs to be hidden from the delivery pipeline
Marc Popp updated JENKINS-26210 Configure Jobs to be hidden from the delivery pipeline Change By: Marc Popp (15/Feb/15 8:52 AM) Description: It would be cool to be able to configure Jobs to be hidden from the delivery pipeline. I have the problem, that I have multiple Deploy Jobs which are all using the same parameterized MultiJob. The Sub-Tasks of the MultiJob are displayed totally out of order and are not important for the high level pipeline view. 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-26210) Configure Jobs to be hidden from the delivery pipeline
Marc Popp commented on JENKINS-26210 Configure Jobs to be hidden from the delivery pipeline I have a multijob 'Deploy' that is called with parameters to deploy a host. It looks like that: Name: Deploy - Phase 1 - Job Step 1 - Phase 2 - Job Step 2 - Job Step 3 Then I have one multijob per host, that calls the common multijob 'Deploy' with parameters: Deploy_XYZ - Phase 1 - Call Parameterised Job: Deploy If I create the pipeline for one job everything is fine: Deploy_XYZ -> Deploy -+-> Step 1 | +-> Step 2 | +-> Step 3 Also, in the the pipeline view I'm not interested in the common multijob 'Deploy' and the Steps, but just something like: +-+ +-+ | ENV - QS|-->| ENV - PROD | | Deploy_XYZ1 | | Deploy_ABC1 | | Deploy_XYZ2 | | Deploy_ABC2 | | Deploy_XYZ3 | | Deploy_ABC3 | +-+ +-+ I've attached a screenshot of how the pipeline looks like, with 2 ENVs and 1 Deploy Job each. 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-26210) Configure Jobs to be hidden from the delivery pipeline
Marc Popp updated JENKINS-26210 Configure Jobs to be hidden from the delivery pipeline Screenshot with 2 ENVs and 1 Deploy Job each. Change By: Marc Popp (15/Feb/15 9:23 AM) Attachment: Screen Shot 2015-02-15 at 10.19.23.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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [flexible-publish-plugin] (JENKINS-26936) support thrown from publisher job statuses
Kanstantsin Shautsou commented on JENKINS-26936 support thrown from publisher job statuses Bug that is Blocker for person must have Blocker status. This broken behavior is Blocker for me because i decided to pass conditional decides to this plugin instead of implementing build status conditionals in my new plugin. 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [flexible-publish-plugin] (JENKINS-26936) support thrown from publisher job statuses
Kanstantsin Shautsou commented on JENKINS-26936 support thrown from publisher job statuses From "issue tracking documentation" https://issues.jenkins-ci.org/secure/ShowConstantsHelp.jspa#StatusTypes Priority Levels An issue has a priority level which indicates its importance. The currently defined priorities are listed below. In addition, you can add more priority levels in the administration section. Blocker Blocks development and/or testing work, production could not run. 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [flexible-publish-plugin] (JENKINS-26936) support thrown from publisher job statuses
Kanstantsin Shautsou updated JENKINS-26936 support thrown from publisher job statuses Change By: Kanstantsin Shautsou (15/Feb/15 2:03 PM) Priority: Major Blocker 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [flexible-publish-plugin] (JENKINS-26936) support thrown from publisher job statuses
Daniel Beck commented on JENKINS-26936 support thrown from publisher job statuses Bug that is Blocker for person must have Blocker status. This broken behavior is Blocker for me because This makes every bug a blocker, which obviously makes no sense at all. 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23150) Warn users about invalid plugin configurations
Nicolas De Loof assigned JENKINS-23150 to Nicolas De Loof Warn users about invalid plugin configurations Change By: Nicolas De Loof (15/Feb/15 2:35 PM) Assignee: Nicolas De Loof 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [flexible-publish-plugin] (JENKINS-26936) support thrown from publisher job statuses
ikedam commented on JENKINS-26936 support thrown from publisher job statuses @integer This might be a blocker for you, but you didn't explain why it was a blocker, did you? I think you only mentioned that flexible-publish should (or must) handle exceptions, and I agree that (https://github.com/jenkinsci/flexible-publish-plugin/pull/9). But I don't know why this is a blocker, as users first should make publishers not to throw exceptions and flexible publish enables that with conditional executions. I don't care whether this issue is set to a blocker or not, but anyway I don't think I need to work immediately for this issue for now. I'll work in an usual priority. Let's describe the exact problem you yourself face, and that must have others want to help you! 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [flexible-publish-plugin] (JENKINS-26936) support thrown from publisher job statuses
Kanstantsin Shautsou commented on JENKINS-26936 support thrown from publisher job statuses Dear, @Daniel Not every bug is a really blocker. Btw it probably first my bug that i set to blocker. I appreciate your "comment every issue" efforts, but if you think that jenkins should not have such status, then feel free to open INFRA issue. @ikedam I set issue status according to rules. You changed status without asking initial requestor why it was set to Blocker. So i set it back. "But I don't know why this is a blocker, as users first should make publishers not to throw exceptions and flexible publish enables that with conditional executions" - read provided information in PR, boolean is deprecated method for returning publisher statuses and leads for broken flows in post-build actions that depends on correct build statuses. All this statuses is a total mess now, because part of plugins throw exception, part return boolean, part set build status directly, part set status and return failure and etc. Ok, I will rework my initial PR. The only thing that i want to hear from maintainer is what behavior is expected for "On evaluation failure" -> "Failure build" because it influence on how we can catch and process this case. 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [flexible-publish-plugin] (JENKINS-26936) support thrown from publisher job statuses
Daniel Beck commented on JENKINS-26936 support thrown from publisher job statuses if you think that jenkins should not have such status, then feel free to open INFRA issue. The status has merit, but it should be reserved for severe issues that actually make Jenkins really unusable (worse than occasional crashes, data loss and severe memory leak, which are only 'Critical'). This particular issue looks like 'Major loss of functionality' to me. The problem with "This blocks whatever I'm trying to do, so it's a blocker" is that almost every relatively minor bug or unimplemented feature can be considered a blocker because someone, somewhere, planned to use that specific feature, but can't. 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26964) post-build action statuses handling
Kanstantsin Shautsou created JENKINS-26964 post-build action statuses handling Issue Type: Bug Assignee: Unassigned Components: core Created: 15/Feb/15 4:10 PM Description: Nobody will fix it in core, but i will describe a root case. for perform step returning boolean is deprecated now and AbortException with reason message is a new style. In current situation when you have two publishers: 1) If build SUCCESS (build.getResult()) then do action and FAIL the publisher. 2) if build SUCCESS - do action Because of 1) returned boolean build summary result is set to failed. So what status will see 2) publisher? If 1) publisher fail the build with 'return false', then second publisher will still see SUCCESS state and do unexpected action If 1) throw AbortException, then build result will be set to FAILURE and 2) publisher will see correct fail status. The error in this place https://github.com/jenkinsci/jenkins/blob/555e2d593fbb419d2fad7e9cfae5911daf3d30e3/core/src/main/java/hudson/model/AbstractBuild.java#L719-L729 if set build Result immediately for throwen error and later for boolean. Project: Jenkins Priority: Major Reporter: Kanstantsin Shautsou 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26964) post-build action statuses handling
Kanstantsin Shautsou updated JENKINS-26964 post-build action statuses handling Change By: Kanstantsin Shautsou (15/Feb/15 4:12 PM) Description: Nobody will fix it in core, but i will describe a root case. for perform step returning method that return boolean for publisher is deprecated now and AbortException with reason message is a new style.In current situation when you have two publishers:1) If build SUCCESS (build.getResult()) then do action and FAIL the publisher.2) if build SUCCESS - do actionBecause of 1) returned boolean build summary result is set to failed.So what status will see 2) publisher? If 1) publisher fail the build with 'return false', then second publisher will still see SUCCESS state and do unexpected action If 1) throw AbortException, then build result will be set to FAILURE and 2) publisher will see correct fail status.The error in this place https://github.com/jenkinsci/jenkins/blob/555e2d593fbb419d2fad7e9cfae5911daf3d30e3/core/src/main/java/hudson/model/AbstractBuild.java#L719-L729if set build Result immediately for throwen error and later for boolean. 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [flexible-publish-plugin] (JENKINS-26936) support thrown from publisher job statuses
Kanstantsin Shautsou commented on JENKINS-26936 support thrown from publisher job statuses I opened root case https://issues.jenkins-ci.org/browse/JENKINS-26964 and build statuses mess looks like a real blocker, because this is broken and i can't use core flow and can't use flexible publish flow. Fixing core is very dangerous, so fixing and using flexible publish for executing all publishers looks right. So this is blocker for usage. Let's bette concentrate on fix 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [flexible-publish-plugin] (JENKINS-26936) support thrown from publisher job statuses
Kanstantsin Shautsou edited a comment on JENKINS-26936 support thrown from publisher job statuses I opened root case https://issues.jenkins-ci.org/browse/JENKINS-26964 and build statuses mess looks like a real blocker, because this is broken and i can't use core flow and can't use flexible publish flow. Fixing core is very dangerous, so fixing and using flexible publish for executing all publishers looks right. So this is blocker for usage. Let's better concentrate on fix 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26964) post-build action statuses handling
Kanstantsin Shautsou updated JENKINS-26964 post-build action statuses handling Change By: Kanstantsin Shautsou (15/Feb/15 4:39 PM) Description: Nobody will fix it in core (?) , but i will describe a root case.perform method that return boolean for publisher is deprecated now and AbortException with reason message is a new style.In current situation when you have two publishers:1) If build SUCCESS (build.getResult()) then do action and FAIL the publisher.2) if build SUCCESS - do actionBecause of 1) returned boolean build summary result is set to failed.So what status will see 2) publisher? If 1) publisher fail the build with 'return false', then second publisher will still see SUCCESS state and do unexpected action If 1) throw AbortException, then build result will be set to FAILURE and 2) publisher will see correct fail status.The error in this place https://github.com/jenkinsci/jenkins/blob/555e2d593fbb419d2fad7e9cfae5911daf3d30e3/core/src/main/java/hudson/model/AbstractBuild.java#L719-L729if set build Result immediately for throwen error and later for boolean. 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [stashnotifier-plugin] (JENKINS-24967) StashNotifier Plugin does not use Jenkins no-proxy settings
SCM/JIRA link daemon resolved JENKINS-24967 as Fixed StashNotifier Plugin does not use Jenkins no-proxy settings Change By: SCM/JIRA link daemon (15/Feb/15 7:40 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [stashnotifier-plugin] (JENKINS-24967) StashNotifier Plugin does not use Jenkins no-proxy settings
SCM/JIRA link daemon commented on JENKINS-24967 StashNotifier Plugin does not use Jenkins no-proxy settings Code changed in jenkins User: Georg Grütter Path: src/main/java/org/jenkinsci/plugins/stashNotifier/StashNotifier.java http://jenkins-ci.org/commit/stashnotifier-plugin/6db1e023402da95f065df119c5f7b4215a12635c Log: Merge pull request #51 from bbaetz/fix-proxy-exclusions JENKINS-24967 Fix proxy exclusions not working Compare: https://github.com/jenkinsci/stashnotifier-plugin/compare/a5ff8a610c65...6db1e023402d 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [stashnotifier-plugin] (JENKINS-24967) StashNotifier Plugin does not use Jenkins no-proxy settings
SCM/JIRA link daemon commented on JENKINS-24967 StashNotifier Plugin does not use Jenkins no-proxy settings Code changed in jenkins User: Bradley Baetz Path: src/main/java/org/jenkinsci/plugins/stashNotifier/StashNotifier.java http://jenkins-ci.org/commit/stashnotifier-plugin/5a1848f9c1dc4eddfe67027fb4225508c44e44f7 Log: [FIXED JENKINS-24967] Fix proxy exclusions not working Also support proxy authentication Fixes #41 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testexecuter] (JENKINS-26965) Jenkins test on Master instead of slave have permission denied issues
johnson are created JENKINS-26965 Jenkins test on Master instead of slave have permission denied issues Issue Type: Bug Assignee: Unassigned Components: testexecuter Created: 15/Feb/15 11:58 PM Description: I set up my project on jenkins and i noticed when i have a slave and run my automation test on slave, it clones and run the test fine but when i tell jenkins to so the same on Master, i starts to get the git repo and to clone down the xcdoe project but it always fails due to permission denied issues. here is the path to where my master checkout the Jenkins master workspace: /Users/Shared/Jenkins/Home. I guess i need some permissions authentications for root like that. But when i set my Slave to : /Users/seunare/JENKINS_jobs/workspace, if runs, git clone, and runs my test on it. Please could you help me with this issue? Project: Jenkins Priority: Blocker Reporter: johnson are 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [packer-plugin] (JENKINS-26966) Unable to build packer image from subdirectory
Tenyo Grozev created JENKINS-26966 Unable to build packer image from subdirectory Issue Type: Improvement Assignee: Unassigned Components: packer-plugin Created: 16/Feb/15 1:30 AM Description: I've run into a problem using packer-plugin when the json I'm trying to use is in a subdirectory. For example, my Jenkins job is cloning a git repo containing various packer configurations (e.g. centos-6.5, rhel-6.5, etc.). Each one is in a separate folder and has a template.json and a scripts directory. Under the Packer post-build actions I specify Packer Template File "centos-6.5/template.json". When I run the job I get the following error: [workspace] $ /var/lib/jenkins/tools/biz.neustar.jenkins.plugins.packer.PackerInstallation/packer-0.7.5/packer build -_only_=virtualbox-iso -debug "/var/lib/jenkins/jobs/Packer build/workspace/centos-6.5/template.json" 4 error(s) occurred: Bad script 'scripts/base.sh': stat scripts/base.sh: no such file or directory Bad script 'scripts/vagrant.sh': stat scripts/vagrant.sh: no such file or directory Bad script 'scripts/virtualbox.sh': stat scripts/virtualbox.sh: no such file or directory Bad script 'scripts/cleanup.sh': stat scripts/cleanup.sh: no such file or directory It appears that the relative paths (such as scripts/base.sh) in template.json are expected to be in the current directory (which is workspace/) although I'm calling workspace/centos-6.5/template.json. So when I changed the script paths in the json to be "centos-6.5/scripts/base.sh" it ran successfully, however, I don't want to do that as it breaks the script if I then try to run it from within centos-6.5 (which is the recommended way). It would be great to have a "Change directory" parameter for packer-plugin to change the working directory before calling packer. Environment: Jenkins 1.598, packer plugin 1.0 Project: Jenkins Priority: Minor Reporter: Tenyo Grozev 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-26771) Error when using Integrate to upstream upon successful build on branch project
Steven Christou assigned JENKINS-26771 to Steven Christou Error when using Integrate to upstream upon successful build on branch project Change By: Steven Christou (16/Feb/15 6:09 AM) Assignee: Kohsuke Kawaguchi Steven Christou 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-3105) Configuration UI to disable process tree killer selectively
Alexey Larsky commented on JENKINS-3105 Configuration UI to disable process tree killer selectively I've try to use 'set BUILD_ID=DoNotKill && start mspdbsrv -start -spawn -shutdowntime 2147483647', but msbuild always starts your own instance of mspdbsrv with your BUILD_ID and kill it on finish build. Since Jenkins v 1.580.3 glovbal environment settings has been changed and for general node-wide disabling process killing you should add global environment variable 'BUILD_ID' with any value i.e. 'DoNotKill' and additional check 'Prepare jobs environment' checkbox. I don't found way to disable just mspdbsrv killing. 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-3105) Configuration UI to disable process tree killer selectively
Alexey Larsky commented on JENKINS-3105 Configuration UI to disable process tree killer selectively I really wonder why this issue priority is 'Trivial'. For me it's major. 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-3105) Configuration UI to disable process tree killer selectively
Alexey Larsky updated JENKINS-3105 Configuration UI to disable process tree killer selectively Change By: Alexey Larsky (16/Feb/15 6:38 AM) Attachment: Prepare job env.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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactory-plugin] (JENKINS-26967) not running with Maven 3.0.5
podskalsky created JENKINS-26967 not running with Maven 3.0.5 Issue Type: Bug Assignee: yossis Components: artifactory-plugin Created: 16/Feb/15 7:25 AM Description: In a Maven Build JOB which is using Maven 3.0.5 the Artifactory Plugin is not working ... java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:178) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at hudson.maven.Maven3Builder.call(Maven3Builder.java:136) at hudson.maven.Maven3Builder.call(Maven3Builder.java:71) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NoSuchMethodError: org.apache.commons.io.IOUtils.lineIterator(Ljava/io/InputStream;Ljava/nio/charset/Charset;)Lorg/apache/commons/io/LineIterator; at hudson.plugins.analysis.util.JavaPackageDetector.detectPackageName(JavaPackageDetector.java:34) at hudson.plugins.analysis.util.AbstractPackageDetector.detectPackageName(AbstractPackageDetector.java:25) at hudson.plugins.analysis.util.PackageDetectors.detectPackageName(PackageDetectors.java:30) at hudson.plugins.checkstyle.parser.CheckStyleParser.convert(CheckStyleParser.java:96) at hudson.plugins.checkstyle.parser.CheckStyleParser.parse(CheckStyleParser.java:72) at hudson.plugins.analysis.core.AbstractAnnotationParser.parse(AbstractAnnotationParser.java:54) at hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:323) at hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:281) at hudson.plugins.analysis.core.FilesParser.parseSingleFile(FilesParser.java:239) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:198) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31) at hudson.FilePath.act(FilePath.java:989) at hudson.FilePath.act(FilePath.java:967) at hudson.plugins.checkstyle.CheckStyleReporter.perform(CheckStyleReporter.java:129) at hudson.plugins.analysis.core.HealthAwareReporter.postExecute(HealthAwareReporter.java:337) at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoEnded(Maven3Builder.java:634) at hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:615) at org.jfrog.build.extractor.maven.BuildInfoRecorder.mojoSucceeded(BuildInfoRecorder.java:274) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:228) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleMo
[JIRA] [analysis-core-plugin] (JENKINS-26968) No Reports with Maven 3.1.1 or Maven 3.2.5
podskalsky created JENKINS-26968 No Reports with Maven 3.1.1 or Maven 3.2.5 Issue Type: Bug Assignee: Ulli Hafner Components: analysis-core-plugin, core, maven-plugin Created: 16/Feb/15 7:36 AM Description: At a Maven Build JOB ... After the Maven build step the following post build steps "Publish Checkstyle analysis results", "Publish FindBugs analysis results" and "Publish PMD analysis results" are not running ! Maven is building executing all reports at "site" goal. But the reports are not collected to Jenkins. There are also no icons and diagramms for the reports. If I'm using Maven 3.05 in the same configuration the reposrts are here. But no reports at Maven 3.1.1 and Maven 3.2.5 !!! I have to use one of theses versions because it seems that the Artifactory-Plugin is not running with old Maven 3.0.5. Environment: Jenkins ver. 1.597 Latest Maven-Plugin Latest Analysis-Core-Plugin Maven 3.1.1 or Maven 3.2.5 Latest Artifactory-Plugin Project: Jenkins Priority: Blocker Reporter: podskalsky 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ci-game-plugin] (JENKINS-24478) Publisher hudson.plugins.cigame.GamePublisher aborted due to exception NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/Abs
Esben Rasmussen commented on JENKINS-24478 Publisher hudson.plugins.cigame.GamePublisher aborted due to exception NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction Excellent work 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
