[JIRA] [ircbot] (JENKINS-24685) When a build fails, and IRC Notification is set up as a Post-build Action, the build is marked SUCCESS instead of FAILED
kutzi commented on JENKINS-24685 When a build fails, and IRC Notification is set up as a Post-build Action, the build is marked SUCCESS instead of FAILED Console doesn't say that the irc notifier is changing the build status. What is the build result if you remove irc notifier? 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] [gerrit-trigger] (JENKINS-19477) Gerrit trigger stores KeyFile password as clear text
rin_ne resolved JENKINS-19477 as Fixed Gerrit trigger stores KeyFile password as clear text Change By: rin_ne (12/Sep/14 5:47 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [gerrit-trigger] (JENKINS-19477) Gerrit trigger stores KeyFile password as clear text
rin_ne updated JENKINS-19477 Gerrit trigger stores KeyFile password as clear text Change By: rin_ne (12/Sep/14 5:46 AM) URL: https://github.com/jenkinsci/gerrit-trigger-plugin/pull/157 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] (JENKINS-23794) Artifactory Plugin guava dependency problem
Shridhar Patil commented on JENKINS-23794 Artifactory Plugin guava dependency problem I am using Jenkins 1.578 and my plugin works on guava-17.0.jar. In Jenkins lib folder we have guava-11.0.1.jar. Scenario 1. On Windows 7 Enterprise 64-bit : I replaced the 11.0.0 jar with 17.0 version and my plugin and Jenkins both works fine. Scenario 2. On Linux x86_64 I replaced the 11.0.0 jar with 17.0 version and my plugin works fine. but after successfully running the job on Jenkins, I get error while opening the output console and I have to view the output on Plain text option. Exception javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.578.jar!/hudson/model/Run/console.jelly:65:27: com.google.common.io.Closeables.closeQuietly(Ljava/io/Closeable;)V at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) 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] [gerrit-trigger] (JENKINS-21064) Form too large if there are many patchsets in the selection list (manual trigger)
rin_ne commented on JENKINS-21064 Form too large if there are many patchsets in the selection list (manual trigger) Solution: JENKINS-20327 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] [gerrit-trigger] (JENKINS-21064) Form too large if there are many patchsets in the selection list (manual trigger)
rin_ne resolved JENKINS-21064 as Won't Fix Form too large if there are many patchsets in the selection list (manual trigger) Change By: rin_ne (12/Sep/14 5:29 AM) Status: Open Resolved Resolution: Won't 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] [gerrit-trigger] (JENKINS-21407) additional trigger button at the top or floating trigger button
rin_ne updated JENKINS-21407 additional trigger button at the top or floating trigger button Change By: rin_ne (12/Sep/14 4:53 AM) URL: https://github.com/jenkinsci/gerrit-trigger-plugin/pull/180 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] [gerrit-trigger] (JENKINS-21407) additional trigger button at the top or floating trigger button
rin_ne resolved JENKINS-21407 as Fixed additional trigger button at the top or floating trigger button Change By: rin_ne (12/Sep/14 4:54 AM) Status: Open Resolved Assignee: rin_ne rsandell 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] [gerrit-trigger] (JENKINS-24295) Gerrit Cancel doesn't work for Matrix jobs
rin_ne assigned JENKINS-24295 to rsandell Gerrit Cancel doesn't work for Matrix jobs Change By: rin_ne (12/Sep/14 4:48 AM) Assignee: rin_ne rsandell 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] [gerrit-trigger] (JENKINS-21407) additional trigger button at the top or floating trigger button
rin_ne stopped work on JENKINS-21407 additional trigger button at the top or floating trigger button Change By: rin_ne (12/Sep/14 4:46 AM) Status: In Progress Open 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] [gerrit-trigger] (JENKINS-21407) additional trigger button at the top or floating trigger button
rin_ne updated JENKINS-21407 additional trigger button at the top or floating trigger button Change By: rin_ne (12/Sep/14 4:43 AM) Assignee: rsandell rin_ne 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] [gerrit-trigger] (JENKINS-21407) additional trigger button at the top or floating trigger button
rin_ne started work on JENKINS-21407 additional trigger button at the top or floating trigger button Change By: rin_ne (12/Sep/14 4:43 AM) Status: Open In Progress 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-23868) Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported
sharon xia commented on JENKINS-23868 Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported We have set up another jenkins in another server in US (windows server 2008 r2), jenkins version 1.565.1, and the same thing happen if I download from Shanghai. The file downloaded is not complete but no error is reported. I asked other people in US to download it and they do not see this issue. I will do another experiment to check whether it will exist on linux jenkins server. I would not be a good idea to place the files on other server because we have a large collection of customers. If we change the places, it is a big impact. 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-23868) Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported
Mark Waite commented on JENKINS-23868 Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported I'm not aware of any change to Jenkins which would alter that behavior. Since you were able to place your large binary on another server, and download from that other server, you could consider making that a permanent work around. Since you're running on a Windows computer as your Jenkins server, you might also check to see if the same behavior appears when running Jenkins from a Linux server. 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-23868) Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported
sharon xia commented on JENKINS-23868 Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported Is there any related code change for jenkins download?? 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] [ircbot] (JENKINS-24685) When a build fails, and IRC Notification is set up as a Post-build Action, the build is marked SUCCESS instead of FAILED
apotek updated JENKINS-24685 When a build fails, and IRC Notification is set up as a Post-build Action, the build is marked SUCCESS instead of FAILED Change By: apotek (12/Sep/14 12:07 AM) Environment: Jenkins IRC Plugin org.jvnet.hudson.plugins:ircbot:2.25pircbotx org.pircbotx:pircbotx: 1. 9Jenkins 1. 550 Ubuntu LTS 12 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] [ircbot] (JENKINS-24685) When a build fails, and IRC Notification is set up as a Post-build Action, the build is marked SUCCESS instead of FAILED
apotek updated JENKINS-24685 When a build fails, and IRC Notification is set up as a Post-build Action, the build is marked SUCCESS instead of FAILED Change By: apotek (12/Sep/14 12:06 AM) Environment: Jenkins v 1.550 Ubuntu LTS 12 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] [ircbot] (JENKINS-24685) When a build fails, and IRC Notification is set up as a Post-build Action, the build is marked SUCCESS instead of FAILED
apotek created JENKINS-24685 When a build fails, and IRC Notification is set up as a Post-build Action, the build is marked SUCCESS instead of FAILED Issue Type: Bug Assignee: kutzi Components: ircbot Created: 12/Sep/14 12:01 AM Description: This is from the console. The IRC Notifier plugin marks the build as a success even if it failed. BUILD FAILED /apps/mags/util/bouwer/bouw.xml:120:22: Execution of the target buildfile failed. Aborting. Total time: 1 minutes 0.46 seconds Bouwer is cleaning up... Done. Errors were encountered. Goodbye IRC notifier plugin: Sending notification to: #mslo Finished: SUCCESS Environment: Jenkins v Ubuntu LTS 12 Project: Jenkins Priority: Major Reporter: apotek 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] [parameterized-trigger] (JENKINS-22125) FATAL: Illegal choice: incremental caused by Parameterized Trigger Plugin 2.23
ikedam resolved JENKINS-22125 as Fixed FATAL: Illegal choice: incremental caused by Parameterized Trigger Plugin 2.23 No details. Looks an invalid reopen. Change By: ikedam (11/Sep/14 11:34 PM) Status: Reopened 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] [docker-build-step] (JENKINS-24414) Port bindings are ignored with Docker v1.2
Harald Albers edited a comment on JENKINS-24414 Port bindings are ignored with Docker v1.2 Same docker-java spike works with docker-java 0.10.0. So upgrading docker build step plugin to use docker-java 0.10.0 should solve the issue. Sadly, docker-java api significantly changed in 0.10.0 I'm working on the upgrade, see WIP 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] [gerrit-trigger] (JENKINS-24648) Git poll always finds changes when there is none when used with Gerrit trigger strategy
eguess74 commented on JENKINS-24648 Git poll always finds changes when there is none when used with Gerrit trigger strategy So the only issue i have now is that on the direct push to ther repository git plugin keeps showing me only one commit in changelist even if there were more then one commits pushed. I'm not sure why it is not just taking last built revision and builds the rev-list from there to the currently checked out revision. 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] [deploy] (JENKINS-24675) Deploy plugin does not store hostname for Glassfish 2 container
Peter Kolínek updated JENKINS-24675 Deploy plugin does not store hostname for Glassfish 2 container Change By: Peter Kolínek (11/Sep/14 8:21 PM) Environment: Jenkins 1.554.2 LTSDeploy to conatiner container Plugin 1.10 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] [docker-build-step] (JENKINS-24071) Docker build step tries to build on master and not slave
vjuranek reopened JENKINS-24071 Docker build step tries to build on master and not slave Sorry, it wasn't intended to resolve this issue (I just reverted previous commit which makes it potentially even worse) Change By: vjuranek (11/Sep/14 8:02 PM) Resolution: Fixed Status: Resolved Reopened 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-24625) style.css should define background color for input fields
Ceesjan Luiten commented on JENKINS-24625 style.css should define background color for input fields Thanks for the help Daniel, made the pull request. For those who want to reproduce the bug: After switching your theme you might need to restart your browser before the color scheme becomes fully active (the window decoration changes right away). Also, Chrome/Chromium isn't affected by it because they seem to ignore the user's theme completely. There's no testcase; if these kinds of issues should be intercepted in the future Jenkins could incorporate some kind of CSS Lint in the validation process. 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] [docker-build-step] (JENKINS-24071) Docker build step tries to build on master and not slave
SCM/JIRA link daemon resolved JENKINS-24071 as Fixed Docker build step tries to build on master and not slave Change By: SCM/JIRA link daemon (11/Sep/14 7:41 PM) Status: Reopened 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] [docker-build-step] (JENKINS-24071) Docker build step tries to build on master and not slave
SCM/JIRA link daemon commented on JENKINS-24071 Docker build step tries to build on master and not slave Code changed in jenkins User: Vojtech Juranek Path: src/main/java/org/jenkinsci/plugins/dockerbuildstep/DockerBuilder.java http://jenkins-ci.org/commit/docker-build-step-plugin/471393e7c36faf40d34a1a8744fe66222769fcee Log: Revert "[FIXED JENKINS-24071] Execute command remotely on slaves, not on master (+formating)" This reverts commit 9f6f42df0a667c6b7bc28793b04955991dd29864. Actually didn't fix the issue (see JENKINS-24071) and potentially makes it even worse. 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] [gradle] (JENKINS-24682) Gradle Wrapper not working when gradle version was previously selected
Mario Mohr commented on JENKINS-24682 Gradle Wrapper not working when gradle version was previously selected From my point of view the plugin should not consider the installed tools at all if gradle wrapper is selected. If created a pull request here: https://github.com/jenkinsci/gradle-plugin/pull/23 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] [docker-build-step] (JENKINS-24684) Add support for container linking
Harald Albers started work on JENKINS-24684 Add support for container linking Change By: Harald Albers (11/Sep/14 7:25 PM) Status: Open In Progress 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] [docker-build-step] (JENKINS-24683) Add support for bind mounting volumes
Harald Albers started work on JENKINS-24683 Add support for bind mounting volumes Change By: Harald Albers (11/Sep/14 7:25 PM) Status: Open In Progress 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] [docker-build-step] (JENKINS-24684) Add support for container linking
Harald Albers
updated JENKINS-24684
Add support for container linking
Change By:
Harald Albers
(11/Sep/14 7:24 PM)
Description:
Docker Build Step Plugin should support the {{--link
=
}} option of the {{docker run}} CLI command.
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] [docker-build-step] (JENKINS-24684) Add support for container linking
Harald Albers created JENKINS-24684 Add support for container linking Issue Type: Improvement Assignee: Harald Albers Components: docker-build-step Created: 11/Sep/14 7:23 PM Description: Docker Build Step Plugin should support the --link= option of the docker run CLI command. Project: Jenkins Priority: Minor Reporter: Harald Albers 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] [docker-build-step] (JENKINS-24683) Add support for bind mounting volumes
Harald Albers created JENKINS-24683 Add support for bind mounting volumes Issue Type: Improvement Assignee: Harald Albers Components: docker-build-step Created: 11/Sep/14 7:22 PM Description: Docker Build Step Plugin should support the -volume and -volumes-from options of the docker run CLI command. Project: Jenkins Priority: Minor Reporter: Harald Albers 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] [docker-build-step] (JENKINS-24414) Port bindings are ignored with Docker v1.2
Harald Albers assigned JENKINS-24414 to Harald Albers Port bindings are ignored with Docker v1.2 Change By: Harald Albers (11/Sep/14 7:07 PM) Assignee: vjuranek Harald Albers 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] [docker-build-step] (JENKINS-24414) Port bindings are ignored with Docker v1.2
Harald Albers commented on JENKINS-24414 Port bindings are ignored with Docker v1.2 Same docker-java spike works with docker-java 0.10.0. So upgrading docker build step plugin to use docker-java 0.10.0 should solve the issue. Sadly, docker-java api significantly changed in 0.10.0 I'm working on the upgrade. 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] [docker-build-step] (JENKINS-24414) Port bindings are ignored with Docker v1.2
Harald Albers started work on JENKINS-24414 Port bindings are ignored with Docker v1.2 Change By: Harald Albers (11/Sep/14 7:07 PM) Status: Open In Progress 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] [gradle] (JENKINS-24682) Gradle Wrapper not working when gradle version was previously selected
Mario Mohr created JENKINS-24682 Gradle Wrapper not working when gradle version was previously selected Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: gradle Created: 11/Sep/14 7:04 PM Description: If the gradlew script is not in the root of the project and the build configuration is changed from using a specific version to using the gradle wrapper the build fails with: Can't retrieve the Gradle executable. Project: Jenkins Labels: gradle Priority: Major Reporter: Mario Mohr 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] [parallel-test-executor] (JENKINS-24681) Providing Environment variable to spawned jobs
Omer Weissman created JENKINS-24681 Providing Environment variable to spawned jobs Issue Type: Improvement Assignee: Unassigned Components: parallel-test-executor Created: 11/Sep/14 7:00 PM Description: My suggestion is to add another mode in which 2 environment variables will be passed to every sub-build and instead of the exclusion list. PARALLELIZATION_DEGREE PARALLELIZATION_PART It will let users to use their own calculation and not count on the exclusion list which is not tolerant to missing/partial results ( i.e.every added test is not excluded from any sub-job and is executed on all) I am using this plugin to execute a home grown UI integration testing in my workplace. every test takes from ~30 seconds to more than 5 minutes. full un-parallelized execution takes more than 3.5 hours, breakdown to 15 parts takes 11-12 minutes, but if we add a new test that is a long one we get big time addition penalty. but we also have a way to breakdown to files containing the parts and the jobs can load the tests from a file but I need the vars to get it, i.e. /path-to/$PARALLELIZATION_DEGREE/$PARALLELIZATION_PART.json currently I do it with export PARALLEL=`printenv "exclusion.txt" | grep -o -m1 -P '(\d+)' ` WDYT ? Project: Jenkins Priority: Major Reporter: Omer Weissman 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] [openid] (JENKINS-23431) Google is phasing out OpenID endpoint. Need to move on to G+ sign-in
owenmehegan commented on JENKINS-23431 Google is phasing out OpenID endpoint. Need to move on to G+ sign-in Has anyone who is watching this ticket done any research into a solution? If not, I can try to do some. As Kohsuke points out, if we don't get a solution in place early enough, people will end up locked out of their Jenkins installs and working around that is annoying. Let's try to collaborate on a solution so we don't all get burned. 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] [build-alias-setter] (JENKINS-24680) Assign an alias to a build manually
Patrice Matignon created JENKINS-24680 Assign an alias to a build manually Issue Type: New Feature Assignee: Oliver Gondža Components: build-alias-setter Created: 11/Sep/14 6:49 PM Description: The idea would be to select a build via the standard Jenkins UI, and assign an arbitrary (subject to input validation) alias to it, i.e. the build page is now available thru a url utilizing the new alias (as you would expect from an alias that has been automatically assigned during the actual build). Fancy: detect if this alias is already used (by another build), offer to move it to the present build. (btw, it would be nice to be able to "revoke" an existing alias, whether previously assigned manually or automatically). This feature would be useful for manual processes around build promotion or build marking. Project: Jenkins Priority: Minor Reporter: Patrice Matignon 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] [docker-build-step] (JENKINS-24414) Port bindings are ignored with Docker v1.2
Harald Albers commented on JENKINS-24414 Port bindings are ignored with Docker v1.2 I can confirm that this is also the case when using docker-java 1.9.1 directly. Both StartContainerCmd.withPortBindings() and StartContainerCmd.withPublishAllPorts() stop working after upgrading Docker from 1.1.2 to 1.2.0. 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] [build-environment] (JENKINS-24679) Executor_Number variable doesn't align with the build executor status
Fadel Wanssa created JENKINS-24679 Executor_Number variable doesn't align with the “build executor status” Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: BuildExecutorStatus.png, Freestyle1Job.png, Freestyle2Job.png, Freestyle3Job.png Components: build-environment Created: 11/Sep/14 6:29 PM Description: After cancelling a build on an agent, the EXECUTOR_NUMBER variable gets out of sync with the "build executor status" number. Please check attached screenshots. Project: Jenkins Priority: Major Reporter: Fadel Wanssa 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-24678) Canceling a build during artifact archiving fails build
Chris Jenkins
updated JENKINS-24678
Canceling a build during artifact archiving fails build
Change By:
Chris Jenkins
(11/Sep/14 6:04 PM)
Description:
When I try to cancel a build that is running the "Archive the Artifacts" post build action, the build fails with a large stack trace.I noticed this on version 1.553 and was able to reproduce on the current version. Steps to take are as follows:1. Start a build on a slave that will archive artifacts.2. When the build reaches the archiving step, cancel it.3. See console output for error and build is now failed.Stack trace:ERROR: Failed to archive artifacts: **
*
/*
*
java.io.IOException: java.io.IOException: Failed to extract /home/jenkins/workspace/{job}/transfer of 29 files at hudson.FilePath.readFromTar(FilePath.java:2111) at hudson.FilePath.copyRecursiveTo(FilePath.java:2023) at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:217) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:74) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1770) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240)Caused by: java.io.IOException at hudson.remoting.FastPipedInputStream.read(FastPipedInputStream.java:177) at hudson.util.HeadBufferingStream.read(HeadBufferingStream.java:61) at com.jcraft.jzlib.InflaterInputStream.fill(InflaterInputStream.java:175) at com.jcraft.jzlib.InflaterInputStream.read(InflaterInputStream.java:106) at org.apache.tools.tar.TarBuffer.readBlock(TarBuffer.java:257) at org.apache.tools.tar.TarBuffer.readRecord(TarBuffer.java:223) at hudson.org.apache.tools.tar.TarInputStream.read(TarInputStream.java:345) at java.io.FilterInputStream.read(FilterInputStream.java:107) at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1792) at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1769) at org.apache.commons.io.IOUtils.copy(IOUtils.java:1744) at hudson.util.IOUtils.copy(IOUtils.java:40) at hudson.FilePath.readFromTar(FilePath.java:2101) ... 13 more at hudson.FilePath.copyRecursiveTo(FilePath.java:2030) at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:217) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:74) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1770) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240)Caused by: java.util.concurrent.ExecutionException: java.io.IOException: Pipe is already closed at hudson.remoting.Channel$3.adapt(Channel.java:772) at hudson.remoting.Channel$3.adapt(Channel.java:767) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) at hudson.FilePath.copyRecursiveTo(FilePath.java:2026) ... 12 moreCaused by: java.io.IOException: Pipe is already closed at hudson.remoting.PipeWindow.checkDeath(PipeWindow.java:108) at hudson.remoting.PipeWindow$Real.get(PipeWindow.java:203) at hudson.remoting.ProxyOutputStream._write(ProxyOutputStream.java:141) at hudson.remoting.ProxyOutputStream.write(ProxyOutputStream.java:109) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:93) at java.io.BufferedOutputStream.write(BufferedOu
[JIRA] [core] (JENKINS-24678) Canceling a build during artifact archiving fails build
Chris Jenkins
created JENKINS-24678
Canceling a build during artifact archiving fails build
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
11/Sep/14 6:03 PM
Description:
When I try to cancel a build that is running the "Archive the Artifacts" post build action, the build fails with a large stack trace.
I noticed this on version 1.553 and was able to reproduce on the current version. Steps to take are as follows:
1. Start a build on a slave that will archive artifacts.
2. When the build reaches the archiving step, cancel it.
3. See console output for error and build is now failed.
Stack trace:
ERROR: Failed to archive artifacts: */
java.io.IOException: java.io.IOException: Failed to extract /home/jenkins/workspace/{job}/transfer of 29 files
at hudson.FilePath.readFromTar(FilePath.java:2111)
at hudson.FilePath.copyRecursiveTo(FilePath.java:2023)
at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61)
at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:217)
at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:74)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734)
at hudson.model.Build$BuildExecution.post2(Build.java:183)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683)
at hudson.model.Run.execute(Run.java:1770)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
Caused by: java.io.IOException
at hudson.remoting.FastPipedInputStream.read(FastPipedInputStream.java:177)
at hudson.util.HeadBufferingStream.read(HeadBufferingStream.java:61)
at com.jcraft.jzlib.InflaterInputStream.fill(InflaterInputStream.java:175)
at com.jcraft.jzlib.InflaterInputStream.read(InflaterInputStream.java:106)
at org.apache.tools.tar.TarBuffer.readBlock(TarBuffer.java:257)
at org.apache.tools.tar.TarBuffer.readRecord(TarBuffer.java:223)
at hudson.org.apache.tools.tar.TarInputStream.read(TarInputStream.java:345)
at java.io.FilterInputStream.read(FilterInputStream.java:107)
at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1792)
at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1769)
at org.apache.commons.io.IOUtils.copy(IOUtils.java:1744)
at hudson.util.IOUtils.copy(IOUtils.java:40)
at hudson.FilePath.readFromTar(FilePath.java:2101)
... 13 more
at hudson.FilePath.copyRecursiveTo(FilePath.java:2030)
at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61)
at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:217)
at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:74)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734)
at hudson.model.Build$BuildExecution.post2(Build.java:183)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683)
at hudson.model.Run.execute(Run.java:1770)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
Caused by: java.util.concurrent.ExecutionException: java.io.IOException: Pipe is already closed
at hudson.remoting.Channel$3.adapt(Channel.java:772)
at hudson.remoting.Channel$3.adapt(Channel.java:767)
at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59)
at hudson.FilePath.copyRecursiveTo(FilePath.java:2026)
... 12 more
Caused by: java.io.IOException: Pipe is already closed
at hudson.remoting.PipeWindow.checkDeath(PipeWindow.java:108)
at hudson.remoting.PipeWindow$Real.get(PipeWindow.java:203)
at hudson.remoting.ProxyOutputStream._write
[JIRA] [ec2] (JENKINS-24676) Region list not being populated when keys are entered
Layton Whiteley updated JENKINS-24676 Region list not being populated when keys are entered Change By: Layton Whiteley (11/Sep/14 4:52 PM) Summary: Getting a NPE Region list not being populated when configuring Cloud keys are entered Description: Currently on jenkins Jenkins ver. 1.579ec2 version 1.24entered credentials + RSA key and No regions are populated in the list to be selected got the following error when I clicked `test Connection`Stack tracejavax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:202) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:180) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:89) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:86) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(Character
[JIRA] [ec2] (JENKINS-24676) Getting a NPE when configuring Cloud
Layton Whiteley commented on JENKINS-24676 Getting a NPE when configuring Cloud so it seems that the region list is not being populated when they keys are added 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-24656) Delete project fails with stack trace
Leslie Giles closed JENKINS-24656 as Fixed Delete project fails with stack trace Change By: Leslie Giles (11/Sep/14 4:36 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-24656) Delete project fails with stack trace
Leslie Giles resolved JENKINS-24656 as Fixed Delete project fails with stack trace Resolved by upgrading the conditional-buildstep plugin from 1.3.2 to 1.3.3 Change By: Leslie Giles (11/Sep/14 4:35 PM) Status: Open Resolved Fix Version/s: current 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] [core] (JENKINS-24677) Allow to manipulate workspace from the job page
Kat Lim Ruiz created JENKINS-24677 Allow to manipulate workspace from the job page Issue Type: Improvement Assignee: Unassigned Components: core Created: 11/Sep/14 4:21 PM Description: allow to do simple operations on the workspace: delete file, set/clear readonly flag. These two are all it is really needed for tweaking the workspace for minor failures while building. For example, TFS has a problem with files without readonly flag, therefore it would be easier to just go to workspace and set the flag (right now I have to do it thru Windows Explorer, and at some point I may not have direct access to that folder). Project: Jenkins Labels: workspace Priority: Minor Reporter: Kat Lim Ruiz 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] [perforce] (JENKINS-24674) P4CLIENT wrong when using CloudBees Folder plugin
Rob Petti closed JENKINS-24674 as Duplicate P4CLIENT wrong when using CloudBees Folder plugin This was fixed in another issue, but it hasn't been released yet. Change By: Rob Petti (11/Sep/14 4:10 PM) Status: Open Closed Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [ssh-credentials] (JENKINS-24273) Presence of ECDSA SSH keys breaks SSH credentials plugin
Hendrik Halkow reopened JENKINS-24273 Presence of ECDSA SSH keys breaks SSH credentials plugin This didn't solve the problem and I still can't connect to any SSH slave when ECDSA keys are present. Even with SSH agent plugin installed I don't see any difference. I suggest that we release version 1.10 by reverting the code to 1.7 and only release ECDSA updates when they are really implemented. This is the slave connection log: [09/11/14 18:01:36] [SSH] Opening SSH connection to xx:22. ERROR: Server rejected the 1 private key(s) for xx (credentialId:101b6fd0-3bb9---c5dbb6f7d966/method:publickey) ERROR: Server rejected the 2 private key(s) for xx (credentialId:101b6fd0-3bb9---c5dbb6f7d966/method:publickey) ERROR: Failed to authenticate as xx with credential=101b6fd0---8e7d-c5dbb6f7d966 java.io.IOException: Publickey authentication failed. at com.trilead.ssh2.auth.AuthenticationManager.authenticatePublicKey(AuthenticationManager.java:315) at com.trilead.ssh2.Connection.authenticateWithPublicKey(Connection.java:467) at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPublicKeyAuthenticator.doAuthenticate(TrileadSSHPublicKeyAuthenticator.java:109) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.authenticate(SSHAuthenticator.java:408) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.authenticate(SSHAuthenticator.java:428) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1138) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:648) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:642) 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.io.IOException: Invalid PEM structure, '-BEGIN...' missing at com.trilead.ssh2.crypto.PEMDecoder.parsePEM(PEMDecoder.java:138) at com.trilead.ssh2.crypto.PEMDecoder.decode(PEMDecoder.java:313) at com.trilead.ssh2.auth.AuthenticationManager.authenticatePublicKey(AuthenticationManager.java:224) ... 11 more ERROR: Failed to authenticate as xx with credential=101b6fd0---8e7d-c5dbb6f7d966 java.io.IOException: Publickey authentication failed. at com.trilead.ssh2.auth.AuthenticationManager.authenticatePublicKey(AuthenticationManager.java:315) at com.trilead.ssh2.Connection.authenticateWithPublicKey(Connection.java:467) at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPublicKeyAuthenticator.doAuthenticate(TrileadSSHPublicKeyAuthenticator.java:109) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.authenticate(SSHAuthenticator.java:408) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.authenticate(SSHAuthenticator.java:428) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1138) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:648) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:642) 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.io.IOException: Sorry, this connection is closed. at com.trilead.ssh2.transport.TransportManager.sendMessage(TransportManager.java:647) at com.trilead.ssh2.auth.AuthenticationManager.authenticatePublicKey(AuthenticationManager.java:283) ... 11 more Caused by: java.io.IOException: Invalid PEM structure, '-BEGIN...' missing at com.trilead.ssh2.crypto.PEMDecoder.parsePEM(PEMDecoder.java:138) at com.trilead.ssh2.crypto.PEMDecoder.decode(PEMDecoder.java:313) at com.trilead.ssh2.auth.AuthenticationManager.authenticatePublicKey(AuthenticationManager.java:224) ... 11 more [09/11/14 18:01:47] [SSH] Authentication failed. hudson.AbortException: Authentication failed. at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1143) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:648) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:642) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java
[JIRA] [git] (JENKINS-24516) git polling results exception because ssh is not found
Allan Lei commented on JENKINS-24516 git polling results exception because ssh is not found Was there a preceding job for the failing job? If so, was the preceding job executed on a different platform? This problem didn't cause failing jobs as it was not triggering jobs at all. It was failing when there was a github webhook and scheduled git polling. Yes there were preceding jobs. Yes, it was executed on a Windows 7 slave node launched via Java Web Start. Are you using the EnvInject plugin? If so, could you insert a step in the build which reports the value of the PATH environment variable and post its value here? Yes, 1.89. I will have to try out the PATH env at a later time. Master Node (Ubuntu 14.04, Jenkins 1.579, git 2.2.5, envinject 1.89) Slave Node (Windows 7, via Java Web start) Things I tried/observed: After upgrading to git plugin 2.2.5 and Jenkins 1.579, this problem did not initially happen, and everything worked as expected. I had 3 separate jobs building from the same git repo, but with a different build script(production, staging, development). After the upgrades, I changed the credentials for development and staging jobs. Those jobs had an error in the build script which caused the job to fail. At this time, git polling for these 2 jobs will result in this error, but the production job still polled correctly. Jobs duplicated from the production job will work correctly until there's a build error. Copied the ssh*.sh and ssh*key files that are generated from "git ls-remote -h ...", set GIT_SSH to ssh*.sh and ran it as the jenkins process user successfully Manually triggering a build via Build Now button works fine 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] [ec2] (JENKINS-24676) Getting a NPE when configuring Cloud
Layton Whiteley created JENKINS-24676 Getting a NPE when configuring Cloud Issue Type: Bug Assignee: Francis Upton Components: ec2 Created: 11/Sep/14 3:37 PM Description: Currently on jenkins Jenkins ver. 1.579 ec2 version 1.24 entered credentials + RSA key and got the following error when I clicked `test Connection` Stack trace javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:202) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:180) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:89) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:86) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org
[JIRA] [extended-choice-parameter] (JENKINS-24652) Unable to fetch all user selected values from "Multi-Level Single Select" and "Multi-Level Multi Select"
Jonathan Langevin updated JENKINS-24652 Unable to fetch all user selected values from "Multi-Level Single Select" and "Multi-Level Multi Select" This is a blocker for me, as I need each selected value in the chain, not simply the final resulting value... Change By: Jonathan Langevin (11/Sep/14 3:27 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] [core] (JENKINS-24050) All slaves disconnect and no new slaves can connect due to CancelledKeyException in org.jenkinsci.remoting
Daniel Beck commented on JENKINS-24050 All slaves disconnect and no new slaves can connect due to CancelledKeyException in org.jenkinsci.remoting Patricia Wright: The stack traces and log size are a completely unrelated issue (note that this is about HTTP and the Python API), see JENKINS-24458 and issues linked from there. 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-24625) style.css should define background color for input fields
Daniel Beck commented on JENKINS-24625 style.css should define background color for input fields That would probably be a good idea (Tom, who's working on Jenkins UX, is currently on vacation). For advice related to that, see: https://wiki.jenkins-ci.org/display/JENKINS/Governance+Document#GovernanceDocument-Usingpullrequests https://wiki.jenkins-ci.org/display/JENKINS/Pull+Request+to+Repositories 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-24213) Jenkins slaves repeatable disconnect and connect during startup, related to remoting/nio or swarm plugin
Michael Prokop commented on JENKINS-24213 Jenkins slaves repeatable disconnect and connect during startup, related to remoting/nio or swarm plugin Hi Kohsuke, I've uploaded the whole Jenkins log for you (be warned, it's 19MB): http://michael-prokop.at/sipwise/jenkins.log (I'll keep the file around until you've had a chance to investigate, then I'll remove it again) 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] [deploy] (JENKINS-24675) Deploy plugin does not store hostname for Glassfish 2 container
Peter Kolínek created JENKINS-24675 Deploy plugin does not store hostname for Glassfish 2 container Issue Type: Bug Assignee: Unassigned Components: deploy Created: 11/Sep/14 3:08 PM Description: Saving job settings with Glassfish 2 container does not save hostname to config, so deployment is impossible. Environment: Jenkins 1.554.2 LTS Deploy to conatiner Plugin 1.10 Project: Jenkins Priority: Major Reporter: Peter Kolínek 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-24050) All slaves disconnect and no new slaves can connect due to CancelledKeyException in org.jenkinsci.remoting
Patricia Wright commented on JENKINS-24050 All slaves disconnect and no new slaves can connect due to CancelledKeyException in org.jenkinsci.remoting After this change, the slaves no longer disconnect.Instead, the underlying issue causes the slaves to just stop doing whatever they were doing. Running jobs on those slaves hang forever and can not be cancelled. The Jenkins server starts to spam this in the logs until the filesystem fills up: Sep 11, 2014 10:38:13 AM org.kohsuke.stapler.export.Property writeValue WARNING: null org.kohsuke.stapler.export.NotExportableException: class hudson.plugins.parameterizedtrigger.CapturedEnvironmentAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions at org.kohsuke.stapler.export.Model.(Model.java:73) at org.kohsuke.stapler.export.ModelBuilder.get(ModelBuilder.java:51) at org.kohsuke.stapler.export.Property.writeValue(Property.java:231) at org.kohsuke.stapler.export.Property.writeValue(Property.java:187) at org.kohsuke.stapler.export.Property.writeValue(Property.java:139) at org.kohsuke.stapler.export.Property.writeTo(Property.java:116) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:190) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185) at org.kohsuke.stapler.export.Model.writeTo(Model.java:157) at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:267) at hudson.model.Api.doPython(Api.java:216) at sun.reflect.GeneratedMethodAccessor387.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSec
[JIRA] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Cuong Thai edited a comment on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb I have been around this issue for two days. Here is my configuration that is working at least 4 times continously Here is the log: http://pastebin.com/2fgMhp0S Hopefully you guys can find the real cause 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] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Cuong Thai edited a comment on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb I have been around this issue for two days. Here is my configuration that is working at least 4 times continuously. Here is the log: http://pastebin.com/2fgMhp0S Hopefully you guys can find the real cause 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-24625) style.css should define background color for input fields
Ceesjan Luiten commented on JENKINS-24625 style.css should define background color for input fields I can submit a pull request with the fixed CSS if that would help. 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] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Cuong Thai edited a comment on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb I have been around this issue for two days. Here is my configuration that is working at least 4 times in a row Here is the log: http://pastebin.com/2fgMhp0S Hopefully you guys can find the real cause 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] [perforce] (JENKINS-24674) P4CLIENT wrong when using CloudBees Folder plugin
Morne Joubert created JENKINS-24674 P4CLIENT wrong when using CloudBees Folder plugin Issue Type: Bug Assignee: Rob Petti Components: perforce Created: 11/Sep/14 2:18 PM Description: I can see from the log that the plugin correctly replaces the / fields in the job name with - characters. Using remote perforce client: SDMOS-dev-mjou-__sdmos_sdmos-int-ucom-build-Build_SDMOS_ucom_CDC_arm.local_jenkins_mlb-2062542078 But the P4CLIENT is still set to using a client with / p4 info User name: jenkins Client name: SDMOS/dev/mjou/__sdmos_sdmos-int/ucom/build/Build_SDMOS_ucom_CDC_arm.local_jenkins_mlb-2062542078 (illegal) Any call i then do that needs P4CLIENT fails with an error about slashes not allowed in P4CLIENT Project: Jenkins Priority: Major Reporter: Morne Joubert 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] [gerrit-trigger] (JENKINS-24648) Git poll always finds changes when there is none when used with Gerrit trigger strategy
eguess74 commented on JENKINS-24648 Git poll always finds changes when there is none when used with Gerrit trigger strategy the problem is not exactly in constant rebulds, but in the fact that when poll was set to daily and configured with the gerrit trigger the polls were happening a bit more often and they were always finding one commit as a recent change. Just because we are using the ivy build trigger and there are several projects that most of other projects are depending from it eventually was becoming full server rebuild. 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] (JENKINS-23493) Unable to checkout from svn
minal silimkar commented on JENKINS-23493 Unable to checkout from svn Issue Description: --- We are trying to use Jenkins (version: 1.563) for building Maven and ANT based Projects using Java 1.7. We have Jenkins & Collabnet SVN (Ver: 1.8) setup on Solaris 11. Jenkins Subversion plugin version is 1.54. We are able to checkout and build some projects successfully; whereas facing issues for some projects. Our observation is: When number of files in project is more than 200, build fails; because it cannot complete SVN code checkout. Does anyone know if it has got any limit set for maximum number of files to be checked out and if it is yes, what are those settings? One more thing is, while investigating this issue, we did same setup on Windows and it works perfectly fine. We don't face any issue over there. So is this Solaris platform compatibility related issue? Below is the stacktrace: ERROR: Failed to check out http://XX.XXX.XX.XX:18080/svn/Test/branches/ApplicationName org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT /svn/Test/!svn/vcc/default failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:388) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:334) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1291) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:839) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.update(SVNUpdateClient16.java:507) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doCheckout(SVNUpdateClient16.java:915) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldCheckout.run(SvnOldCheckout.java:19) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldCheckout.run(SvnOldCheckout.java:8) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:777) at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:99) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:161) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:908) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:889) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:872) at hudson.FilePath.act(FilePath.java:920) at hudson.FilePath.act(FilePath.java:893) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:848) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:786) at hudson.model.AbstractProject.checkout(AbstractProject.java:1251) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:513) at hudson.model.Run.execute(Run.java:1706) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: svn: E175002: REPORT /svn/Test/!svn/vcc/default failed at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97) ... 32 more Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT request failed on '/svn/Test/!svn/vcc/default' svn: E175002: chunked stream ended unexpectedly at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:777) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382) ... 31 more Caused by: svn: E175002:
[JIRA] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Cuong Thai commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb I have been around this issue for two days. Here is my configuration that is working at least 4 times Here is the log: http://pastebin.com/2fgMhp0S 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] [hp-application-automation-tools-plugin] (JENKINS-23180) How to use "HP Application Automation Tools" (Jenkins plugin) through proxy
JY Cr. commented on JENKINS-23180 How to use "HP Application Automation Tools" (Jenkins plugin) through proxy As I understand, "HP Application Automation Tools" (Jenkins plugin) calls ALM with the HpToolsLauncher component ( https://github.com/jenkinsci/hp-applications-automatisation-tools-plugin/tree/master/HpToolsLauncher ) which does not seem to support HTTP connection through a proxy. Indeed, in our context, HTTP connections between Jenkins (and "HP Application Automation Tools" plug-in) and ALM must always go through a proxy. 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] [shiningpanda] (JENKINS-16176) ShiningPanda PATH update uses wrong separator on Windows
Doug Goldstein
commented on JENKINS-16176
ShiningPanda PATH update uses wrong separator on Windows
For a solution that uses Python (which we know we've already got installed) and doesn't need sed, the following worked for me. No guarantees.
REM Fix for Jenkins bug #16176 (Wrong PATH separator used on Windows)
for /f "delims=" %%a in ('%PYTHON_EXE% -c "import os; print(os.environ['PATH'].replace(':c:', ';c:').replace(':C:', ';C:'))"') do @set "PATH=%%a"
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] [git] (JENKINS-24516) git polling results exception because ssh is not found
Jesse Cheng commented on JENKINS-24516 git polling results exception because ssh is not found Reverting to git plugin 2.0 (my installed version before upgrade) resolved the issue. There was no preceding job. 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] [workflow] (JENKINS-24673) Build wrappers in Workflow plugin
Marcus Jacobsson created JENKINS-24673 Build wrappers in Workflow plugin Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: workflow Created: 11/Sep/14 1:08 PM Description: This may be something that I've missed but how are you planing on adding support to add build wrappers to the Workflow plugin. We depend a lot on a few plugins to modify the console output to for example color code, find match patterns and to filter out password. Project: Jenkins Priority: Major Reporter: Marcus Jacobsson 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] [workflow] (JENKINS-24672) GitSCM in Workflow runs git.exe if master is run on Windows and slave is a Linux
Marcus Jacobsson created JENKINS-24672 GitSCM in Workflow runs git.exe if master is run on Windows and slave is a Linux Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: workflow Created: 11/Sep/14 1:05 PM Description: I don't know if it could be something with the os version is taken from the master instead of the node and thus trying to run a .exe file on a Linux server. Console output Running on WSAB101036 (10.158.238.104) in /home/ci/ci-build/workspace/My-First-Workflow Running: Allocate node : Body : Start Running: Git Cloning the remote Git repository Cloning repository https://github.com/jenkinsci/lucene-search-plugin.git > git.exe init /home/ci/ci-build/workspace/My-First-Workflow # timeout=10 ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Could not init /home/ci/ci-build/workspace/My-First-Workflow at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$4.execute(CliGitAPIImpl.java:485) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:388) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: hudson.plugins.git.GitException: Error performing command: git.exe init /home/ci/ci-build/workspace/My-First-Workflow at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1414) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1383) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1379) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1093) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$4.execute(CliGitAPIImpl.java:483) ... 11 more Caused by: java.io.IOException: Cannot run program "git.exe" (in directory "/home/ci/ci-build/workspace/My-First-Workflow"): error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1047) at hudson.Proc$LocalProc.(Proc.java:244) at hudson.Proc$LocalProc.(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:802) at hudson.Launcher$ProcStarter.start(Launcher.java:380) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1403) ... 15 more Caused by: java.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:186) at java.lang.ProcessImpl.start(ProcessImpl.java:130) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1028) ... 20 more Running: Allocate node : Body : End Running: Allocate node : End Running: End of Workflow java.lang.RuntimeException: hudson.AbortException at org.jenkinsci.plugins.workflow.cps.CpsStepContext.replay(CpsStepContext.java:388) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:156) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:79) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:45) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:15) at Script1.run(Script1.groovy:2) at Unknown.Unknown(Unknown) at __cps.transform__(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup$1.call(ContinuationGr
[JIRA] [scoverage] (JENKINS-24659) Error in Publishing Scoverage XML and HTML report
Daniel Beck resolved JENKINS-24659 as Not A Defect Error in Publishing Scoverage XML and HTML report Not a bug. Learn regular _expression_ syntax. Change By: Daniel Beck (11/Sep/14 1:05 PM) Status: Open Resolved Resolution: Not A Defect 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] (JENKINS-23493) Unable to checkout from svn
Daniel Beck commented on JENKINS-23493 Unable to checkout from svn Are you sure what you're using is actually a Subversion server, and not some other software with an incomplete SVN protocol implementation? 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] [security] (JENKINS-24668) Security Authentication Lockout
Daniel Beck resolved JENKINS-24668 as Not A Defect Security Authentication Lockout This is a request for help, not an issue report or feature request. Please use Jira only for the latter. To request assistance, use the jenkinsci-users mailing list, or ask in #jenkins on Freenode. That said, if you use Jenkins user database, go to the /signup URL – if no user exists yet, it should allow registering one (that should get admin privileges). Other than that, there's only https://wiki.jenkins-ci.org/display/JENKINS/Disable+security Change By: Daniel Beck (11/Sep/14 12:51 PM) Status: Open Resolved Resolution: Not A Defect 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] [support-core] (JENKINS-24671) Obtain username that made call to url
Daniel Beck commented on JENKINS-24671 Obtain username that made call to url Referer might be useful as well if not already recorded. Some API use is due to plugins (one of the wall displays does that) so users might not even be aware of that. 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] [release] (JENKINS-22339) Enable environment variables for M2 Release Plugin
Dan Albu commented on JENKINS-22339 Enable environment variables for M2 Release Plugin As a fix you can always use this in your M2 Release Plugin Release goals and options : -DreleaseVersions=$MVN_RELEASE_VERSION -DsnapshotVersions=$MVN_DEV_VERSION This way you have access to the variables in the job 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] [support-core] (JENKINS-24671) Obtain username that made call to url
Steven Christou created JENKINS-24671 Obtain username that made call to url Issue Type: New Feature Assignee: Steven Christou Components: support-core Created: 11/Sep/14 12:12 PM Description: In the support core plugin we currently obtain the url that made a slow-request call. We should also be able to record the user who made the request. If someone makes a request to `JENKINS_URL/api/xml`, we should record that information. Project: Jenkins Priority: Major Reporter: 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] [parameterized-trigger] (JENKINS-24622) Upstream jobs have disapeared from job main page
ikedam commented on JENKINS-24622 Upstream jobs have disapeared from job main page Thanks for details. I'll test reproduction in my environment and see changes of codes in 2.17. 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] [plot] (JENKINS-24666) No data on the plot when using matrix project
Oliver Gondža commented on JENKINS-24666 No data on the plot when using matrix project Proposed fix: https://github.com/jenkinsci/plot-plugin/pull/13 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [valgrind] (JENKINS-13745) Valgrind Plugin: Any Configuration of the "publish valgrind results" part triggers exception
Artem Popov edited a comment on JENKINS-13745 Valgrind Plugin: Any Configuration of the "publish valgrind results" part triggers exception I didn't tested which one of XMLs cause a crash, but it is someone from "valgrind.tar.gz" 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] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Tobias Schumacher commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb I think my adb is broken. I see the adb start-server two times. $ adb start-server failed to start daemon * daemon not running. starting it now on port 5801 * $ adb start-server The adb log starts with: remote local: read terminated (message) adb: offline check_header(): invalid magic bad header: terminated (data) adb: offline After this output there is only the sockel level log. So at the first adb start-server the log is correct. But not at the second one. I will look into it. I can see this at the process too. One adb process appears. Then appears a second one. After 1 second the first (I'm not 100% sure) disappears. This phenomenon started one month ago. The android emulator had the problem befor this change too. Maybe my adb installation is broken. I will reinstall/reconfigure it. I'm coming back on Thursday. I can't work on this issue until then. 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] [gerrit-trigger] (JENKINS-24295) Gerrit Cancel doesn't work for Matrix jobs
SCM/JIRA link daemon commented on JENKINS-24295 Gerrit Cancel doesn't work for Matrix jobs Code changed in jenkins User: rinrinne Path: src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger.java http://jenkins-ci.org/commit/gerrit-trigger-plugin/8b0e9be7c5be6c70c53aeb25c8a1a258ac3d54da Log: Add one-off executor to search list for cancel job By "Build Current Pathcset Only" feature, running and queued jobs with the same change are canceled. These are found in queue items and executors. But MatrixJob uses one-off executor. It is not included in executors. So it cannot be canceled. This patch adds one-off executors to executor's list. Fix for JENKINS-24295 Task-Url: https://issues.jenkins-ci.org/browse/JENKINS-24295 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] [gerrit-trigger] (JENKINS-24648) Git poll always finds changes when there is none when used with Gerrit trigger strategy
Mark Waite edited a comment on JENKINS-24648 Git poll always finds changes when there is none when used with Gerrit trigger strategy I think you've used the correct technique for your case. Defining a poll with no polling interval definition is a common technique to declare that a job will only be launched by a polling hook. I believe that is what Kohsuke described in his "polling must die" blog posting. That doesn't justify the non-stop rebuilds, but I don't know how to duplicate those non-stop rebuilds. 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] [gerrit-trigger] (JENKINS-24648) Git poll always finds changes when there is none when used with Gerrit trigger strategy
Mark Waite commented on JENKINS-24648 Git poll always finds changes when there is none when used with Gerrit trigger strategy Defining a poll with no polling interval definition is a common technique to declare that a job will only be launched by a polling hook. I believe that is what Kohsuke described in his "polling must die" blog posting 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] [git] (JENKINS-24516) git polling results exception because ssh is not found
Mark Waite commented on JENKINS-24516 git polling results exception because ssh is not found Allan Lei can you provide answers to the same questions that were asked of the original person who reported the problem? Specifically: Was there a preceding job for the failing job? If so, was the preceding job executed on a different platform? 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] [git] (JENKINS-24516) git polling results exception because ssh is not found
Allan Lei edited a comment on JENKINS-24516 git polling results exception because ssh is not found I had a very similar problem getting "ssh: not found" when it was doing github polling. This also happened around the time Jenkins was upgraded to 1.579 along with the git plugin, but not sure which one caused it. Downgrading the git plugin from 2.2.5 to 2.2.4 solved the problem. Ubuntu 14.04 Jenkins: 1.579 Git client: 1.10.1 EnvInject: 1.89 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] [git] (JENKINS-24516) git polling results exception because ssh is not found
Allan Lei commented on JENKINS-24516 git polling results exception because ssh is not found I had a very similar problem getting "ssh: not found" when it was doing github polling. This also happened around the time Jenkins was upgraded to 1.579 along with the git plugin, but not sure which one caused it. Downgrading the git plugin from 2.2.5 to 2.2.4 solved the problem. Ubuntu 14.04 Jenkins: 1.579 Git client: 1.10.1 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] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Richard Mortimer commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb You should only need to set the ADB_TRACE environment variable in Jenkins. The android-emulator-plugin starts ADB from within the job and kills it at the end. Ideally you should make sure that no other ADB server/emulator instance is running outside of jenkins to avoid complicating things. It does make sense to ensure that /tmp/adb.log does not exist before the jenkins job starts to ensure that there are no file permissions issues when the ADB server tries to open the log. I don't think that the emulator loglevel change would be useful at this time. 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] [rqm] (JENKINS-24670) The plugin stops executing when testcase has no script (our case 11971)
Mads Nielsen created JENKINS-24670 The plugin stops executing when testcase has no script (our case 11971) Issue Type: Bug Assignee: Praqma Support Components: rqm Created: 11/Sep/14 10:06 AM Project: Jenkins Priority: Minor Reporter: Mads Nielsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [rqm] (JENKINS-24669) Multiple builders overwrite build result links (our case 11973)
Mads Nielsen created JENKINS-24669 Multiple builders overwrite build result links (our case 11973) Issue Type: Bug Assignee: Praqma Support Components: rqm Created: 11/Sep/14 10:05 AM Project: Jenkins Priority: Minor Reporter: Mads Nielsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [security] (JENKINS-24668) Security Authentication Lockout
Christopher Scharer created JENKINS-24668 Security Authentication Lockout Issue Type: Task Affects Versions: current Assignee: Unassigned Components: security Created: 11/Sep/14 9:57 AM Description: I recently installed jenkins and it's up and running and when I went into Configuration I set up the security and now I don't have access to the Configuration or Build areas. I thought I set myself up as a user with all access, but I can't seem to login either? Any suggestions on how to resolve this? Due Date: 11/Sep/14 12:00 AM Environment: Windows 7 Fix Versions: current Project: Jenkins Labels: security Priority: Trivial Reporter: Christopher Scharer 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] [gui] (JENKINS-24589) Build History - name and links overlap if build names are long
Kirill Merkushev edited a comment on JENKINS-24589 Build History - name and links overlap if build names are long In 579 it can look like this attachement: 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] [gui] (JENKINS-24589) Build History - name and links overlap if build names are long
Kirill Merkushev updated JENKINS-24589 Build History - name and links overlap if build names are long In 579 it can look like this attachement: Change By: Kirill Merkushev (11/Sep/14 9:39 AM) Attachment: 2014-09-11_1334.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] [gerrit-trigger] (JENKINS-24295) Gerrit Cancel doesn't work for Matrix jobs
rin_ne resolved JENKINS-24295 as Fixed Gerrit Cancel doesn't work for Matrix jobs Change By: rin_ne (11/Sep/14 9:26 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [cli] (JENKINS-21772) Use of CLI login command resets Jenkins after restart when using default JENKINS_HOME
Daniel Beck commented on JENKINS-21772 Use of CLI login command resets Jenkins after restart when using default JENKINS_HOME minal silimkar: You realize this issue has been resolved, right? Why did you assign it to yourself? 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] [gerrit-trigger] (JENKINS-24295) Gerrit Cancel doesn't work for Matrix jobs
rin_ne commented on JENKINS-24295 Gerrit Cancel doesn't work for Matrix jobs I can reproduce then find root cause. New PR is created. 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] [gerrit-trigger] (JENKINS-24295) Gerrit Cancel doesn't work for Matrix jobs
rin_ne updated JENKINS-24295 Gerrit Cancel doesn't work for Matrix jobs Change By: rin_ne (11/Sep/14 9:23 AM) URL: https://github.com/jenkinsci/gerrit-trigger-plugin/pull/178 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] [cli] (JENKINS-21772) Use of CLI login command resets Jenkins after restart when using default JENKINS_HOME
minal silimkar assigned JENKINS-21772 to minal silimkar Use of CLI login command resets Jenkins after restart when using default JENKINS_HOME Change By: minal silimkar (11/Sep/14 9:21 AM) Assignee: Daniel Beck minal silimkar 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] [gerrit-trigger] (JENKINS-24295) Gerrit Cancel doesn't work for Matrix jobs
rin_ne stopped work on JENKINS-24295 Gerrit Cancel doesn't work for Matrix jobs Change By: rin_ne (11/Sep/14 9:20 AM) Status: In Progress Open 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] [build-failure-analyzer] (JENKINS-15948) Analyzer Icons aren't displayed if Jenkins isn't installed at root context.
Andi Scharfstein commented on JENKINS-15948 Analyzer Icons aren't displayed if Jenkins isn't installed at root context. Can confirm that this still is an issue. 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.
