[JIRA] [parameterized-trigger-plugin] (JENKINS-12290) Lockup when using trigger/call builds on other projects and Block until the triggered projects finish their builds is used with only 1 executo
Marcin Hawraniak commented on JENKINS-12290 Lockup when using trigger/call builds on other projects and Block until the triggered projects finish their builds is used with only 1 executor Really looking forward to see this resolved. Due to this we receive jobs results later than expected (executors are blocked by idle upstream projects) and we can't run others at the same time because of the executors limit. I wonder also if there is any workaround for this at the moment. 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] [config-rotator-plugin] (JENKINS-27215) Subscribe mode for other results (case 12579)
Mads Nielsen created JENKINS-27215 Subscribe mode for other results (case 12579) Issue Type: Improvement Assignee: Praqma Support Components: config-rotator-plugin Created: 03/Mar/15 8:18 AM Project: Jenkins Priority: Critical 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] [integrity-plugin] (JENKINS-27217) Replace Derby DB by MapDB
Matthias Rump created JENKINS-27217 Replace Derby DB by MapDB Issue Type: Improvement Assignee: Cletus DSouza Components: integrity-plugin Created: 03/Mar/15 12:33 PM Description: I propose to change the Database solution used in the integrity plugin from Derby to MapDB PROs: MapDB is well known for it's performance and successfully used in several Jenkins plugins. The original approach of "one database per job" would still be usable. This includes the handling of different credentials on Job-level it is independent of the targeted Integrity-Server version Project: Jenkins Labels: mapDb Priority: Minor Reporter: Matthias Rump 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] [maven-plugin] (JENKINS-26947) Maven job stuck when slave channel get disconnected
Yoann Dubreuil updated JENKINS-26947 Maven job stuck when slave channel get disconnected Change By: Yoann Dubreuil (03/Mar/15 12:41 PM) Summary: Unattendedwaitintheremotingcode Mavenjobstuckwhenslavechannelgetdisconnected Component/s: maven-plugin Component/s: remoting 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-27218) Can't rely on hudson.TcpSlaveAgentListener.hostName to run JNLP slave with a reverse proxy
Nicolas De Loof created JENKINS-27218 Cant rely on hudson.TcpSlaveAgentListener.hostName to run JNLP slave with a reverse proxy Issue Type: Bug Assignee: Unassigned Components: core, remoting Created: 03/Mar/15 12:52 PM Description: `hudson.TcpSlaveAgentListener.hostName` can be used to set X-Jenkins-CLI-Host header, which is used by jenkins CLI to determine the TCP channel target host. When jenkins is hosted with a reverse proxy and you try to setup a Java Web Start slave, this one tries to connect to reverse proxy for TCP channel, even when this parameter is set on master. JNLP slave do run the remoting lib (downloaded as "slave.jar") which doesn't handle X-Jenkins-CLI-Host. Arguably this header is for CLI, not JNLP I suggest to introduce a new X-Jenkins-JNLP-Host (to match X-Hudson-JNLP-Port) that would be exposed by hudson/TcpSlaveAgentListener/index.jelly to reflect configured hudson.TcpSlaveAgentListener.hostName Project: Jenkins Priority: Minor Reporter: Nicolas De Loof This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27226) Clicking More button on build history makes web page unresponsive and never loads
Lorelei McCollum created JENKINS-27226 Clicking More button on build history makes web page unresponsive and never loads Issue Type: Bug Assignee: Unassigned Attachments: bug.png Components: core Created: 03/Mar/15 2:58 PM Description: We just upgraded to 1.599. We are using Chrome 40. We have a lot of downstream jobs that are very parametrized and called A LOT throughout the day, so the build history is very large. We keep about 7 days of builds.. so that is QUITE large and from the picture you can see we set the build names as well for the params. What we notice is that now clicking the More button never actually loads. the web page just times out and hangs and becomes un responsive. No error thrown it just never comes back If there are logs I could collect let me know, but as of now since the upgrade we cannot access the build history anymore for most of our jobs If we open another Jenkins window, Jenkins is still responsive and works, its just that one page that is loading the build history stops working Project: Jenkins Priority: Minor Reporter: Lorelei McCollum 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-plugin] (JENKINS-26363) Input step should permit cancellation from anyone with build abort permission
Tom FENNELLY assigned JENKINS-26363 to Tom FENNELLY Input step should permit cancellation from anyone with build abort permission Change By: Tom FENNELLY (03/Mar/15 2:58 PM) Assignee: JesseGlick TomFENNELLY This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactory-plugin] (JENKINS-27221) Artifactory-plugin destination path for .rpm, .deb
Ludovic Roucoux updated JENKINS-27221 Artifactory-plugin destination path for .rpm, .deb Change By: Ludovic Roucoux (03/Mar/15 3:05 PM) Summary: Artifactory-plugin define destination path inrepository for.rpm,.deb 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-plugin] (JENKINS-26363) Input step should permit cancellation from anyone with build abort permission
Tom FENNELLY started work on JENKINS-26363 Input step should permit cancellation from anyone with build abort permission Change By: Tom FENNELLY (03/Mar/15 2:56 PM) Status: Open InProgress 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] [buildtriggerbadge-plugin] (JENKINS-21923) Provide icons for build causes
Baptiste Mathus commented on JENKINS-21923 Provide icons for build causes Just added two screenshots to keep the information here, if the links above are wiped out as old builds. IIUC, you'd like to have a dedicated icon, like the ones provided by the BTB plugin where the red arrow I added points (yeah, beautiful, I know)? If so, that's indeed a good idea. At least I like it. I don't know if there's already an extension to be able to override that image, I doubt it. But I guess that could be the part needed in core (adding the EP), and keep indeed the icon handling part in BTB. I'll try to have a look. Thanks for the feedback 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] [buildtriggerbadge-plugin] (JENKINS-21923) Provide icons for build causes
Baptiste Mathus updated JENKINS-21923 Provide icons for build causes Change By: Baptiste Mathus (03/Mar/15 3:02 PM) Attachment: JENKINS-21923-illustration1.png Attachment: JENKINS-21923-illustration2.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] [sauce-ondemand-plugin] (JENKINS-25236) Add support for cainfo and capath in Sauce global settings
Ross Rowe commented on JENKINS-25236 Add support for cainfo and capath in Sauce global settings Thanks for letting me know, I've just released version 1.118 which should fix the issue, please let me know how it goes. Cheers, Ross 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-26582) ISE from RunMap.put after reloading config
Mark Sinclair commented on JENKINS-26582 ISE from RunMap.put after reloading config I don't have a specific way to reproduce. Here are some conditions that were true both times the failure occured: -Multiple slaves all busy and about 50 jobs in the build queue. Some jobs have been sitting in the build queue for 12+ hours. -Implement configuration changes across many jobs by editing the config.xml files directly in linux/emacs. config.xml is the only file touched. -reload configuration via jenkins-url/reload from my browser. Jenkins asks me to 'POST' the command, which I hit the "tryPOSTing" button and then it reloads. After the reload, when an executor becomes free, it picks up a job from the queue and immediately fails with the dead indicator in the executor status sidebar. When the thread is restarted, it picks up another job from the queue and dies again. The process repeats until the queue is empty. It is unclear if jobs that were not in the queue at the time of reload would die. I'm not sure if after the reload all jobs need to die one time or just the jobs that were in the queue at the time of the reload. It is true that the problem is self correcting, after a job dies one time, the build number gets corrected and it will run properly the next time. This doesn't happen every time I reload config. 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-plugin] (JENKINS-25890) Deadlock between RunMap and Queue after restart; StepContext.isReady impl acquires lock
Jesse Glick reopened JENKINS-25890 Deadlock between RunMap and Queue after restart; StepContext.isReady impl acquires lock The fix just caused another deadlock: consumption of Timer threads and thus starvation of pickle resolvers. Change By: Jesse Glick (03/Mar/15 4:06 PM) Resolution: Fixed Status: Resolved Reopened Assignee: KohsukeKawaguchi JesseGlick 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-plugin] (JENKINS-25890) Deadlock between RunMap and Queue after restart; StepContext.isReady impl acquires lock
Jesse Glick updated JENKINS-25890 Deadlock between RunMap and Queue after restart; StepContext.isReady impl acquires lock Change By: Jesse Glick (03/Mar/15 4:07 PM) Status: Reopened 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] [workflow-plugin] (JENKINS-25890) Deadlock between RunMap and Queue after restart; StepContext.isReady impl acquires lock
Jesse Glick started work on JENKINS-25890 Deadlock between RunMap and Queue after restart; StepContext.isReady impl acquires lock Change By: Jesse Glick (03/Mar/15 4:07 PM) Status: Open InProgress 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] [slave-setup-plugin] (JENKINS-13091) java.io.StreamCorruptedException: invalid stream header: B055002D
Rick Patterson commented on JENKINS-13091 java.io.StreamCorruptedException: invalid stream header: B055002D @Xavier Nodet - re: your EBCDIC comment. The original problem description shows a parameter -Dfile.encoding=ISO8859-1 to tell the zos Java engine that the slave.jar is an ASCII file: /usr/lpp/java/J6.0/bin/java -Dfile.encoding=ISO8859-1 -jar slave.jar, so the originator's issue should not be due to the EBCDIC encoding. I had an error message very similar to this one until I added the -Dfile.encoding: Exception in thread "main" java.io.StreamCorruptedException: invalid stream header: B055002D After adding that parameter to the Java invocation line, I was able to get the slave to connect okay. After getting the slave to connect, there is a second issue: Jenkins generates a /tmp/hudsonx.sh script, which contains ASCII text and not EBCDIC text(due to the use of the same -Dfile.encoding parameter named above, which sets file encoding for both input and output files.) After creating the /tmp/hudsonx.sh file, Jenkins invokes the sh (shell command) on the generated /tmp/hudsonx.sh, but since the file contains ASCII text but it is not tagged as ASCII (chtag command), the shell attempts to read it as EBCDIC, and so gets messed up. If the following environment variables are added to the environment, then any file generated by the Java engine (such as Jenkins creating the /tmp/hudsonx.sh file), will be tagged ASCII: IBM_JAVA_ENABLE_ASCII_FILETAG ON IBM_JAVA_OPTIONS "-Dfile.encoding=ISO8859-1 -Xnoargsconversion" (I'm not sure about the need of the -Xnoargsconversion in this case, but we require it for our application). My slave is connecting to a userid running tcsh, so I update the environment variable by setting Jenkin's "Prefix Start Slave Command" to: setenv IBM_JAVA_ENABLE_ASCII_FILETAG ON setenv IBM_JAVA_OPTIONS "-Dfile.encoding=ISO8859-1 -Xnoargsconversion" env I am running Jenkins 1.592, the zos version via uname is: OS/390 23.0. the Java is: IBM J9 VM (build 2.6, JRE 1.7.0 z/OS s390x-64 20130617_152572 (JIT enabled, AOT enabled) My logon userid also sets the following environment variables at logon time to indicate to programs (other than Java) about the autotagging of ASCII files: _BPXK_AUTOCVT=ON _CEE_RUNOPTS=POSIX(ON),FILETAG(AUTOCVT,AUTOTAG) 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-27226) Clicking More button on build history makes web page unresponsive and never loads
Daniel Beck updated JENKINS-27226 Clicking More button on build history makes web page unresponsive and never loads Tom FENNELLY Not sure whether we already have a report about this, could well be a duplicate. Change By: Daniel Beck (03/Mar/15 4:40 PM) Labels: user-experience Assignee: TomFENNELLY 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-client-plugin] (JENKINS-27180) Upgrade to version 1.600 broke GIT plugin
Chris Pattersonc commented on JENKINS-27180 Upgrade to version 1.600 broke GIT plugin It appears that deleting previous builds and nextBuildNumber file fixes the 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.
[JIRA] [core] (JENKINS-27218) Can't rely on hudson.TcpSlaveAgentListener.hostName to run JNLP slave with a reverse proxy
Nicolas De Loof updated JENKINS-27218 Cant rely on hudson.TcpSlaveAgentListener.hostName to run JNLP slave with a reverse proxy Change By: Nicolas De Loof (03/Mar/15 1:03 PM) Description: `hudson.TcpSlaveAgentListener.hostName`canbeusedtosetX-Jenkins-CLI-Hostheader,whichisusedbyjenkinsCLItodeterminetheTCPchanneltargethost.WhenjenkinsishostedwithareverseproxyandyoutrytosetupaJavaWebStartslave,thisonetriestoconnecttoreverseproxyforTCPchannel,evenwhenthisparameterissetonmaster.JNLPslavedoruntheremotinglib(downloadedasslave.jar)whichdoesnthandleX-Jenkins-CLI-Host.ArguablythisheaderisforCLI,notJNLPIsuggesttointroduceanewX-Jenkins-JNLP-Host(tomatchX- Hudson Jenkins -JNLP-Port)thatwouldbeexposedbyhudson/TcpSlaveAgentListener/index.jellytoreflectconfiguredhudson.TcpSlaveAgentListener.hostName 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-27218) Can't rely on hudson.TcpSlaveAgentListener.hostName to run JNLP slave with a reverse proxy
Daniel Beck commented on JENKINS-27218 Cant rely on hudson.TcpSlaveAgentListener.hostName to run JNLP slave with a reverse proxy Isn't this covered by the Advanced 'Tunnel Options' (or similar) of JNLP slaves? 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-27219) Job generator config loses Custom Workspace everytime the configuration is edited
Karsten Günther updated JENKINS-27219 Job generator config loses Custom Workspace everytime the configuration is edited Change By: Karsten Günther (03/Mar/15 1:25 PM) Summary: Jobgeneratorconfigloses Costom Custom Workspaceeverytimetheconfigurationisedited 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] [sauce-ondemand-plugin] (JENKINS-25236) Add support for cainfo and capath in Sauce global settings
Tony Andrascik commented on JENKINS-25236 Add support for cainfo and capath in Sauce global settings Will do. When it shows up for update, I will test it 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-27189) In IE11, name of running job extends into main dashboard area
davida2009 commented on JENKINS-27189 In IE11, name of running job extends into main dashboard area One more comment: links on the dashboard are disabled (the cursor remains an arrow when hovered over the links) in a region extending vertically from a little above the build number message to well below it. Are there any IE11 settings that you can suggest I should adjust? 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-27219) Job generator config loses Costom Workspace everytime the configuration is edited
Karsten Günther created JENKINS-27219 Job generator config loses Costom Workspace everytime the configuration is edited Issue Type: Bug Assignee: Unassigned Components: core, jobgenerator-plugin Created: 03/Mar/15 1:25 PM Description: I updated my Jenkins LTS installation from version 1.580.3 (LTS) to 1.596.1 (LTS). With both version I used/use the Job Generator plugin 1.22. After the update I am facing the problem, that everytime I configure a Job Generator via the web interface, the Job Generator loses its "Custom Workspace" setting. This bug is fully reproducible with 1.596.1: Just create a Job Generator and configure a Custom Workspace for it. When you save the configuration, the config.xml has the correct element and value. When you configure it again, the value is not loaded into the configuration formular. When hitting "Save", the value disappears from the config.xml. It is not reproducible with 1.580.3. For me this is a real showstopper as I cannot edit my Job Generators without copying the value of "Custom Workspace" from the config.xml into the formular everytime (my whole project setup depends on it). This bug may be related to https://issues.jenkins-ci.org/browse/JENKINS-23390. Environment: Jenkins LTS 1.596.1, Job Generator 1.22, Windows 2008 Server Project: Jenkins Priority: Blocker Reporter: Karsten Günther 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] [maven-plugin] (JENKINS-26923) Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy in Maven Job
gurkirat singh commented on JENKINS-26923 Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy in Maven Job i am also facing the same issue. Tried running on java 1.7 as well as 1.8 with maven 3.2.3 with checkstyle 2.13 plugin and same issue for org.apache.commons.io.IOUtils.lineIterator(Ljava/io/InputStream;Ljava/nio/charset/Charset;)Lorg/apache/commons/io/LineIterator 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-27226) Clicking More button on build history makes web page unresponsive and never loads
Lorelei McCollum commented on JENKINS-27226 Clicking More button on build history makes web page unresponsive and never loads I did not see anything with my search, sorry if I created a 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] [core] (JENKINS-27226) Clicking More button on build history makes web page unresponsive and never loads
Daniel Beck resolved JENKINS-27226 as Duplicate Clicking More button on build history makes web page unresponsive and never loads Found the original report: JENKINS-26445 Change By: Daniel Beck (03/Mar/15 5:03 PM) Status: Open Resolved 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] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException Request has expired
martinfr62 commented on JENKINS-26854 EC2 slave launch stops working after a while with AmazonServiceException Request has expired Here's the stack trace I get using us-east-1 with instance profile enabled - hit test connection and get this in the log. Process I followed - clone master repo, sync to head, pull down 131 patch and apply using tortoisegit (using windows).Build plugin and deploy to working jenkins. Hit test connection and it fails as below. Failed to check EC2 credential com.amazonaws.AmazonServiceException: AWS was not able to validate the provided access credentials (Service: AmazonEC2; Status Code: 401; Error Code: AuthFailure; Request ID: 43877fc7-b5e0-43ac-8dda-b9f802645343) at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1032) at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:687) at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:441) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:292) at com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:9225) at com.amazonaws.services.ec2.AmazonEC2Client.describeInstances(AmazonEC2Client.java:4541) at com.amazonaws.services.ec2.AmazonEC2Client.describeInstances(AmazonEC2Client.java:8665) at hudson.plugins.ec2.EC2Cloud$DescriptorImpl.doTestConnection(EC2Cloud.java:598) at hudson.plugins.ec2.AmazonEC2Cloud$DescriptorImpl.doTestConnection(AmazonEC2Cloud.java:159) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) 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:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) 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:123) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) 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:135) at
[JIRA] [cloudfoundry-plugin] (JENKINS-26546) Deploy all applications defined in manifest.yml file
William Gautier closed JENKINS-26546 as Fixed Deploy all applications defined in manifest.yml file Change By: William Gautier (03/Mar/15 5:26 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] [cloudfoundry-plugin] (JENKINS-25882) Integrate with credentials plugin
William Gautier closed JENKINS-25882 as Fixed Integrate with credentials plugin Change By: William Gautier (03/Mar/15 5:26 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] [cloudfoundry-plugin] (JENKINS-26182) Services Are Not Persisted In Configuration
William Gautier closed JENKINS-26182 as Fixed Services Are Not Persisted In Configuration Change By: William Gautier (03/Mar/15 5:26 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] [cloudfoundry-plugin] (JENKINS-26598) CloudFoundry client needs proxy configuration for deployment
William Gautier closed JENKINS-26598 as Fixed CloudFoundry client needs proxy configuration for deployment Change By: William Gautier (03/Mar/15 5:26 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-10258) Allow users unicity
Jonathan Langevin commented on JENKINS-10258 Allow users unicity Even with the Additional Identities Plugin, this is still an issue for me. I have multiple emails that I use for commits with Github, for some personal projects and then work projects. I viewed the People list in Jenkins, deleted the "automatic" users created by Jenkins (I presume based on commits across various projects), added the email address for each user to my Additional Identities on my primary account (tried with and without Realm), yet upon revisiting the People list, I see the previously deleted users have again returned. 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] [google-login-plugin] (JENKINS-26279) google login plugin just shows a alert message on top asking username password
recampbell commented on JENKINS-26279 google login plugin just shows a alert message on top asking username password Sorry, I guess I meant curl -L http://localhost:8080/jenkins/ 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] [xcode-plugin] (JENKINS-26368) Technical Version / Marketing Version Not Updating
Mark Edington commented on JENKINS-26368 Technical Version / Marketing Version Not Updating We were running into this at the end of last year. Installing xcproj (via homebrew) solved the problem for us. If you update the latest Cocoapods (0.36) supposedly that will fix the issue as well. See the comments here: https://github.com/CocoaPods/CocoaPods/issues/1723 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] [template-project-plugin] (JENKINS-26548) Jenkins scheduled build jobs fails randomly with java.lang.NullPointerException
Sebastien Besson commented on JENKINS-26548 Jenkins scheduled build jobs fails randomly with java.lang.NullPointerException Hi Ramakrishna, we hit the same issue after upgrading Jenkins to 1.580.3 and the Template Project plugin to 1.4.1. As far as I can tell, this seems to happen when the RepositoryBrowser is set to (Auto). In our case, modifying the parent project SCMs which are inherited via the template project plugin to use a non-auto repository browser seems to have solved transient failures. Hope this helps, Sebastien 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-plugin] (JENKINS-26093) Code snippet generation for BuildTriggerStep.parameters
Jesse Glick started work on JENKINS-26093 Code snippet generation for BuildTriggerStep.parameters Change By: Jesse Glick (03/Mar/15 6:46 PM) Status: Open InProgress 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] [clone-workspace-scm-plugin] (JENKINS-25462) Failed to extract workspace.tar.gz when cloning workspace
Deepu Sudhakar commented on JENKINS-25462 Failed to extract workspace.tar.gz when cloning workspace I've also been seeing the same issue sporadically in my jobs. It's a similar structure: We have one multi-job in which the first job does a checkout and archive of the workspace 9using the clone plugin). In the subsequent phases, we unarchive the workspace and build. However, the downstream jobs in those phases occasionally hit this exception. 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-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException Request has expired
martinfr62 commented on JENKINS-26854 EC2 slave launch stops working after a while with AmazonServiceException Request has expired So having worked with Ximon offline, the signing step was the issue. I didnt notice it so didnt have it set. Would prefer that test connection generate an error and indicate to try changing the signing to see if that works - or test both if flag isnt set and indicate that it requires setting. So user 'has control'. 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] [cmakebuilder-plugin] (JENKINS-27203) Broken env variable replacing
SCM/JIRA link daemon commented on JENKINS-27203 Broken env variable replacing Code changed in jenkins User: André Klitzing Path: src/main/java/hudson/plugins/cmake/EnvVarReplacer.java src/test/java/hudson/plugins/cmake/EnvVarReplacerTest.java http://jenkins-ci.org/commit/cmakebuilder-plugin/2542acd21fed0ee724ba5f3cc13213cfcca7f55b Log: JENKINS-27203 Fix handling of environment variables Replace longer variables first to avoid replacing a partial long name with a short name. Example: NODE = abc NODE_ID = 123 Result "abc_ID" instead of "123" 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] [cmakebuilder-plugin] (JENKINS-27203) Broken env variable replacing
SCM/JIRA link daemon commented on JENKINS-27203 Broken env variable replacing Code changed in jenkins User: volkai Path: src/main/java/hudson/plugins/cmake/EnvVarReplacer.java src/test/java/hudson/plugins/cmake/EnvVarReplacerTest.java http://jenkins-ci.org/commit/cmakebuilder-plugin/d5b88c8354960a97e80e89d6213d992d1d3120e7 Log: Merge pull request #2 from misery/master JENKINS-27203 Fix handling of environment variables Compare: https://github.com/jenkinsci/cmakebuilder-plugin/compare/5276576a5772...d5b88c835496 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] [tap-plugin] (JENKINS-27227) TAP plugin fails to load with java.lang.NoClassDefFoundError: hudson/tasks/test/AbstractTestResultAction
Lionel Sambuc created JENKINS-27227 TAP plugin fails to load with java.lang.NoClassDefFoundError: hudson/tasks/test/AbstractTestResultAction Issue Type: Bug Assignee: Bruno P. Kinoshita Components: tap-plugin Created: 03/Mar/15 9:08 PM Description: Since I upgraded jenkins to the latest revision, the TAP plugin failed with: TAP Reports Processing: START Looking for TAP results report in workspace using pattern: out.tap Saving reports... Processing '/var/lib/jenkins/jobs/testrunner-x86-vm-cross/builds/1/tap-master-files/out.tap' Parsing TAP test result /var/lib/jenkins/jobs/testrunner-x86-vm-cross/builds/1/tap-master-files/out.tap. ERROR: Publisher org.tap4j.plugin.TapPublisher aborted due to exception java.lang.NoClassDefFoundError: hudson/tasks/test/AbstractTestResultAction at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:800) at jenkins.util.AntClassLoader.defineClassFromData(AntClassLoader.java:1138) at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:799) at jenkins.util.AntClassLoader.getClassFromStream(AntClassLoader.java:1309) at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1365) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1325) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1078) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) at org.tap4j.plugin.TapPublisher.perform(TapPublisher.java:263) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:721) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:670) at hudson.model.Run.execute(Run.java:1742) 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.lang.ClassNotFoundException: hudson.tasks.test.AbstractTestResultAction at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1375) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1325) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1078) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) ... 19 more Finished: FAILURE I know my tap file is correct, I checked it validates with the given web service on the wiki page of the plugin. Also this used to work prior a Jenkins upgrade. You can access the full log at http://jenkins.minix3.org/job/testrunner-x86-vm-cross/1/console Environment: OS: Ubuntu Server 2014 LTS 64Bit TAP Plugin version 1.20 Java version: 1.7.0_75 Project: Jenkins Labels: tap plugin java.lang.ClassNotFoundException hudson.tasks.test.AbstractTestResultAction Priority: Blocker Reporter: Lionel Sambuc 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
[JIRA] [core] (JENKINS-27178) Execute shell is terminated randomly
dogfood commented on JENKINS-27178 Execute shell is terminated randomly Integrated in jenkins_main_trunk #3997 JENKINS-27178 Amended merge of #1590. (Revision ef4d1553bf12f5ba8d584491f1c118c8797a3846) Result = SUCCESS jesse glick : ef4d1553bf12f5ba8d584491f1c118c8797a3846 Files : core/src/main/java/hudson/model/Computer.java test/src/test/java/hudson/model/NodeTest.java changelog.html 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] [matrix-project-plugin] (JENKINS-26739) ISE from AbstractLazyLoadRunMap.proposeNewNumber for concurrent matrix builds
dogfood commented on JENKINS-26739 ISE from AbstractLazyLoadRunMap.proposeNewNumber for concurrent matrix builds Integrated in jenkins_main_trunk #3997 JENKINS-26739 Backporting #1592 to rc. (Revision 6ee6fc3b2f7a9bceca1b04c4af5e6f1b024e2ab4) Result = SUCCESS jesse glick : 6ee6fc3b2f7a9bceca1b04c4af5e6f1b024e2ab4 Files : changelog.html core/src/main/java/hudson/model/RunMap.java 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-27230) CronTab FormValidators should be aggregated
Tim Snyder created JENKINS-27230 CronTab FormValidators should be aggregated Issue Type: Improvement Assignee: Tim Snyder Attachments: crontab_sanity_use_formValidator_aggregate.png, current_crontab_sanity.png, possible_crontab_sanity.png Components: core Created: 04/Mar/15 6:14 AM Description: I've been lazy about adopting the H syntax and consequently haven't noticed the awesome previous and next build information that the validator prints out: This is because anytime there is a warning type FormValidator, the ok type FormValidator is thrown away. It would be useful to have both the warning message and the previous and next build time message. Project: Jenkins Priority: Minor Reporter: Tim Snyder 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] [fingerprint-plugin] (JENKINS-19066) Do not spawn multiple files for fingerprints
trejkaz commented on JENKINS-19066 Do not spawn multiple files for fingerprints We have huge problems with fingerprint files - taking up 50 gigabytes of disk space on a machine which is already stressed for storage, taking a long time to copy anywhere, taking Jenkins itself a long time to compact the fingerprints... Storing them in one file certainly seems to be a good fix. I'd almost suggest using a relational database for it, since a lot of time seems to be spent figuring out the links from a project which used the file to the project which generated the file. Our build generates at least 100 artifacts, so presumably the workaround for us would be to zip some of them together into a larger file which would be uncompressed at the next build. 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-plugin] (JENKINS-27228) Input result should log who made the change
J Knurek
created JENKINS-27228
Input result should log who made the change
Issue Type:
Improvement
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
03/Mar/15 10:50 PM
Description:
When using the Input step of the workflow, the run pauses until a user proceeds/aborts. There should be a log indicating which user proceeded/aborted.
I think this functionality would be best in InputStepExecution.doSubmit(StaplerRequest request), but I'm not sure, nor am I sure if the request object will have the user info.
sample workflow:
try {
input "who will be clicking?"
echo 'echo: who proceeded?'
} catch (e) {
echo "echo: who aborted it? "
}
sample of desired output: note: Proceed by user Knurek
Started by user Knurek
Running: Input
who will be clicking?
Proceed or Abort
Proceed by user Knurek
Running: Print Message
echo: who proceeded?
Running: End of Workflow
Finished: SUCCESS
Project:
Jenkins
Priority:
Minor
Reporter:
J Knurek
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-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Christopher Orr commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb Erik Ingman: I tried this change a month or so ago after somebody mentioned that documentation to me, but I found that it made no difference. From re-reading the Android source code, I couldn't see any obvious technical reason why the ports have to be in that form (and only the "-port" flag, not "-ports" enforces it anyway), the "maximum" port number hasn't been 5584 for a long time, adb does recognise emulators started on high ports, and I also looked through lots of build logs for evidence that the user port being even and in that range makes a difference — I didn't find anything conclusive (in fact, emulator startup was more likely to fail in that case). In addition, the code in this pull request doesn't guarantee that the first port will be even, so I'll have to be skeptical about your claims But if it turns out that this change nevertheless helps, then that's good to know. So what are the results you are seeing? Which OS are the emulator builds running on, and what is the emulator config? How many builds were failing previously, compared to now, and is that with builds whose user port is actually even? 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-publish-plugin] (JENKINS-27229) Docker publish plugin throws error Please login prior to push after publishing the image
Maneesh M P updated JENKINS-27229 Docker publish plugin throws error Please login prior to push after publishing the image Change By: Maneesh M P (04/Mar/15 3:19 AM) Environment: Ubuntu64bit12.04 pluginversion:0.11 Component/s: docker-build-publish-plugin Component/s: core 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-27229) Docker publish plugin throws error Please login prior to push after publishing the image
Maneesh M P created JENKINS-27229 Docker publish plugin throws error Please login prior to push after publishing the image Issue Type: Bug Assignee: Unassigned Components: core Created: 04/Mar/15 3:13 AM Description: abc-docker-image-test $ docker build -t admin/abc:3.2.4-1137 abc/xyz/3.2.4 Sending build context to Docker daemon 9.728 kB Sending build context to Docker daemon Step 0 : FROM ubuntu:precise --- 1f80e9ca2ac3 ... Successfully built 0bfa936c91ea abc-docker-image-test $ docker tag --force=true 0bfa936c91ea admin/abc:latest abc-docker-image-test $ docker push admin/abc:3.2.4-1137 The push refers to a repository admin/abc (len: 1) Sending image list Please login prior to push: Username: EOF Build step 'Docker build and publish' marked build as failure Environment: Ubuntu 64 bit 12.04 Project: Jenkins Labels: docker Priority: Blocker Reporter: Maneesh M P 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-10474) Cron syntax error check improvement
Tim Snyder resolved JENKINS-10474 as Cannot Reproduce Cron syntax error check improvement Change By: Tim Snyder (04/Mar/15 5:00 AM) Status: Open Resolved Resolution: CannotReproduce 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-10474) Cron syntax error check improvement
Tim Snyder updated JENKINS-10474 Cron syntax error check improvement This appears to have been fixed between creation and da43ffc872fd2473685ccfb75f9f2b8174c18ff8 (1.602-SNAPSHOT) If you see this in places other than the build trigger cron, please reopen. See cronTabMissingWhitespaceError.png for an example of it being handled more nicely. Change By: Tim Snyder (04/Mar/15 5:00 AM) Attachment: cronTabMissingWhitespaceError.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] [cloudfoundry-plugin] (JENKINS-25884) configure name of manifest.yml
William Gautier resolved JENKINS-25884 as Fixed configure name of manifest.yml Token macros expansion now implemented in https://github.com/jenkinsci/cloudfoundry/commit/bdf318f12da0a27f49f619226a625be1ca1add59 Will be available in v1.3 Change By: William Gautier (03/Mar/15 5:33 PM) Status: InProgress 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] [cloudfoundry-plugin] (JENKINS-27146) Deploying an applicatin w/ no-route fails because route deletion fails
William Gautier resolved JENKINS-27146 as Fixed Deploying an applicatin w/ no-route fails because route deletion fails Fixed in https://github.com/jenkinsci/cloudfoundry/commit/559ceb0ffad960cc058026f2edbf9da6f1cf08e3 Will be available in v1.3 Change By: William Gautier (03/Mar/15 5:31 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudfoundry-plugin] (JENKINS-27119) path attribute in manifest.yml is not evaluated relative to the manifest.yml file
William Gautier started work on JENKINS-27119 path attribute in manifest.yml is not evaluated relative to the manifest.yml file Change By: William Gautier (03/Mar/15 5:37 PM) Status: Open InProgress 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-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException Request has expired
Ximon Eighteen commented on JENKINS-26854 EC2 slave launch stops working after a while with AmazonServiceException Request has expired martinfr62 contacted me privately, we'll work out what the problem is. Separately to that, it occurred to me that end users won't want to know or care about request signing mechanism, or even having to specify whether or not instance profile credentials should be used. Instead both could be determined by the plugin by testing the connection, checking if it works with instance profile credentials, checking if it works with old or new signing algorithm, and just use what works. 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-plugin] (JENKINS-25890) Deadlock between RunMap and Queue after restart; StepContext.isReady impl acquires lock
SCM/JIRA link daemon commented on JENKINS-25890 Deadlock between RunMap and Queue after restart; StepContext.isReady impl acquires lock Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowTest.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsBodySubContext.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsStepContext.java step-api/src/main/java/org/jenkinsci/plugins/workflow/steps/StepContext.java http://jenkins-ci.org/commit/workflow-plugin/790a5453ef094da16e906acc5b5cc512ac1bde60 Log: FIXED JENKINS-25890 isReady should not block, so getProgramPromise may not block on getFlowExecution. 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-plugin] (JENKINS-25890) Deadlock between RunMap and Queue after restart; StepContext.isReady impl acquires lock
SCM/JIRA link daemon commented on JENKINS-25890 Deadlock between RunMap and Queue after restart; StepContext.isReady impl acquires lock Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowTest.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsBodySubContext.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsStepContext.java step-api/src/main/java/org/jenkinsci/plugins/workflow/steps/StepContext.java http://jenkins-ci.org/commit/workflow-plugin/8740a01d48c36289efaca6d2af7714cc7718594e Log: Merge pull request #65 from jglick/isReady-JENKINS-25890 JENKINS-25890 Deadlock Compare: https://github.com/jenkinsci/workflow-plugin/compare/8fe11e081785...8740a01d48c3 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-plugin] (JENKINS-25890) Deadlock between RunMap and Queue after restart; StepContext.isReady impl acquires lock
SCM/JIRA link daemon resolved JENKINS-25890 as Fixed Deadlock between RunMap and Queue after restart; StepContext.isReady impl acquires lock Change By: SCM/JIRA link daemon (03/Mar/15 2:13 PM) Status: InProgress 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] [fitnesse-plugin] (JENKINS-27205) Jenkins raised java.net.SocketTimeoutException: Read timed out when start FitNesse on remote VM
Heng Wang updated JENKINS-27205 Jenkins raised java.net.SocketTimeoutException: Read timed out when start FitNesse on remote VM Change By: Heng Wang (03/Mar/15 2:25 PM) Description: ImhavingaslavenodetoruntheFitNessetestcasesusingtheFitNesseplugin.Howeverwhentheexecutingtimeoftestsuiteislong(over20minutes),JenkinswillraisetheJavareadtimedoutExceptionduringtheexecutingtime,andthejenkinsjobisfailed. Theerrorisasfollow:Connected:200/OKjava.net.SocketTimeoutException:Readtimedout atjava.net.SocketInputStream.socketRead0(NativeMethod) atjava.net.SocketInputStream.read(SocketInputStream.java:150) atjava.net.SocketInputStream.read(SocketInputStream.java:121) atjava.io.BufferedInputStream.fill(BufferedInputStream.java:235) atjava.io.BufferedInputStream.read1(BufferedInputStream.java:275) atjava.io.BufferedInputStream.read(BufferedInputStream.java:334) atsun.net.www.http.ChunkedInputStream.readAheadBlocking(ChunkedInputStream.java:543) atsun.net.www.http.ChunkedInputStream.readAhead(ChunkedInputStream.java:600) atsun.net.www.http.ChunkedInputStream.read(ChunkedInputStream.java:687) atjava.io.FilterInputStream.read(FilterInputStream.java:133) atsun.net.www.protocol.http.HttpURLConnection$HttpInputStream.read(HttpURLConnection.java:2959) atsun.net.www.protocol.http.HttpURLConnection$HttpInputStream.read(HttpURLConnection.java:2953) athudson.plugins.fitnesse.FitnesseExecutor.getHttpBytes(FitnesseExecutor.java:249) athudson.plugins.fitnesse.FitnesseExecutor$1.run(FitnesseExecutor.java:226) atjava.lang.Thread.run(Thread.java:722)Forcecloseofinputstream. ThisseemstobeaknownissueintheFitNesseplugin,andithasbeenraisedforalongtime.HopethisbugcouldberesolvedASAP. Issueraisedbefore:https://issues.jenkins-ci.org/browse/JENKINS-18501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel 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] [sauce-ondemand-plugin] (JENKINS-25236) Add support for cainfo and capath in Sauce global settings
SCM/JIRA link daemon commented on JENKINS-25236 Add support for cainfo and capath in Sauce global settings Code changed in jenkins User: Ross Rowe Path: src/main/java/hudson/plugins/sauce_ondemand/SauceOnDemandBuildWrapper.java http://jenkins-ci.org/commit/sauce-ondemand-plugin/8a73f11cca88a6c49af01a20a40bfb9a845e0fb0 Log: JENKINS-25236 Resolve issue when only common Sauce Connect options were supplied Compare: https://github.com/jenkinsci/sauce-ondemand-plugin/compare/25e213286a19...8a73f11cca88 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] [remoting] (JENKINS-26947) Unattended wait in the remoting code
Yoann Dubreuil commented on JENKINS-26947 Unattended wait in the remoting code Just created a PR: https://github.com/jenkinsci/maven-plugin/pull/39 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] [remoting] (JENKINS-27216) remoting.Channel can not garbage collect
denger tung created JENKINS-27216 remoting.Channel can not garbage collect Issue Type: Bug Assignee: Unassigned Attachments: 1.png, 2.png, 3.png Components: remoting Created: 03/Mar/15 10:44 AM Description: See Heap in MAT Environment: Linux: :core-3.0-amd64:core-3.0-ia32:core-3.0-noarch:graphics-3.0-amd64:graphics-3.0-ia32:graphics-3.0-noarch Jenkins: 1.580.1 JDK: openjdk version 1.7.0-internal OpenJDK Runtime Environment (build 1.7.0-internal-mameili_2014_07_25_10_09-b00) OpenJDK 64-Bit Server VM (build 24.60-b09, mixed mode) Tomcat6.0.41 JAVA_OPTS=-server -Xms20960m -Xmx20960m -XX:PermSize=1024m -XX:MaxPermSize=2048m -Dfile.encoding=UTF-8 -Djava.awt.headless=true -XX:+DisableExplicitGC -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:+UseFastAccessorMethods -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/home/jenkins/tools/tomcat6/logs/ -XX:CMSInitiatingOccupancyFraction=85 Project: Jenkins Priority: Blocker Reporter: denger tung 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] [remoting] (JENKINS-27216) remoting.Channel can not garbage collect
denger tung updated JENKINS-27216 remoting.Channel can not garbage collect Change By: denger tung (03/Mar/15 10:48 AM) Attachment: jstat.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] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Erik Ingman commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb We have solved this on our end, it seems to work every time. According to the Android Emulator docs "The console port number must be an even integer between 5554 and 5584, inclusive. port+1 must also be free and will be reserved for ADB." So we've created a PR, see https://github.com/jenkinsci/android-emulator-plugin/pull/48 /Erik @ www.blocket.se 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-27178) Execute shell is terminated randomly
francisdb edited a comment on JENKINS-27178 Execute shell is terminated randomly Just adding this so people end up here: (restarting Jenkins is a temporary fix as the argument list grows over time) java.io.IOException: Cannot run program "git" (in directory "/var/lib/jenkins/jobs/xxx/workspace"): error=7, Argument list too long java.io.IOException: Cannot run program "/bin/sh" (in directory "/var/lib/jenkins/jobs/xxx/workspace"): error=7, Argument list too long 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] [remoting] (JENKINS-26947) Unattended wait in the remoting code
James Nord commented on JENKINS-26947 Unattended wait in the remoting code FWIW the original report has nothing to do with packet corruption - just the channel dying. You can get the same results with a "kill -9" on the slave. 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-18032) Delete Project link fails with 403 Exception: No valid crumb was included in the request
Roman Pickl commented on JENKINS-18032 Delete Project link fails with 403 Exception: No valid crumb was included in the request I get the same error if I try to delete a job via click in the context menu in the job overview - context menu. Jenkins ver. 1.580.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] [core] (JENKINS-27178) Execute shell is terminated randomly
francisdb commented on JENKINS-27178 Execute shell is terminated randomly Just adding this so people end up here: java.io.IOException: Cannot run program "git" (in directory "/var/lib/jenkins/jobs/xxx/workspace"): error=7, Argument list too long java.io.IOException: Cannot run program "/bin/sh" (in directory "/var/lib/jenkins/jobs/xxx/workspace"): error=7, Argument list too long 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] [remoting] (JENKINS-26947) Unattended wait in the remoting code
Yoann Dubreuil commented on JENKINS-26947 Unattended wait in the remoting code Yes that's right. I found the problem when playing with netem, hence the bug report. It's a bug in the Maven plugin. When upstream channel is closed, Maven channel stays around. Will post a PR shortly. 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] [sauce-ondemand-plugin] (JENKINS-25236) Add support for cainfo and capath in Sauce global settings
SCM/JIRA link daemon commented on JENKINS-25236 Add support for cainfo and capath in Sauce global settings Code changed in jenkins User: Ross Rowe Path: pom.xml http://jenkins-ci.org/commit/sauce-ondemand-plugin/1882195c8954005eeae5a12efacc2e08a85493de Log: JENKINS-25236 Resolve issue when only common Sauce Connect options were supplied 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] [performance-plugin] (JENKINS-27220) Error Column in Performance Trend report is showing as 100% though HTTP Response code is 200.
smruti dehuri created JENKINS-27220 Error Column in Performance Trend report is showing as 100% though HTTP Response code is 200. Issue Type: Bug Assignee: Manuel Carrasco Attachments: Error Column in Jenkins.jpg, Manual Jmeter Test Run Result.JPG Components: performance-plugin Created: 03/Mar/15 2:33 PM Description: 1.I installed performance plugin so i could integrate Apache Jmeter with Jenkins 2.Created New Item and configurd the build 3.After the build is completed,in the performance Trend report,the error column displays as 100% error whereas the HTTP Response code is 200(Successful) Expected Result:-Report should show 0% error in error column. Environment: Jenkins v1.6000,Installed Plugin-Performance Plugin-v1.13,Windows 7,Google Chrome Project: Jenkins Priority: Major Reporter: smruti dehuri 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] [script-security-plugin] (JENKINS-25784) Select sandbox mode by default if current user lacks RUN_SCRIPTS
Jesse Glick assigned JENKINS-25784 to Tom FENNELLY Select sandbox mode by default if current user lacks RUN_SCRIPTS Change By: Jesse Glick (03/Mar/15 2:41 PM) Assignee: JesseGlick TomFENNELLY This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactory-plugin] (JENKINS-27221) Artifactory-plugin define path in repository
Ludovic Roucoux created JENKINS-27221 Artifactory-plugin define path in repository Issue Type: New Feature Assignee: yossis Components: artifactory-plugin Created: 03/Mar/15 2:39 PM Description: We use your artifactory plugin for Jenkins and we don’t find functionality for our requirement. The plugin is working fine to deploy classic java artifacts, but to deploy RPM, Deb (…) we must define the destination path, so for now the only way is to use “curl”. When we choose the “Target releases repository” and the “Target snapshots repository” in the project build configuration, it’s ok, all our repository of Artifactory can be chosen. But we would like to add a path in the repository chosen. For example, we choose “RPM-release” in “Target releases repository” and we would like to have the path “EL6/noarch/RPMS/myfile-5.3.2.noarch.rpm”. We would like to choose this path directly by the plugin UI. So, how can we do that? It’s possible? Otherwise, we propose to fork the plugin, add this functionality and then do a pull request to you. Are you ok? Thanks. Project: Jenkins Priority: Minor Reporter: Ludovic Roucoux 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] [script-security-plugin] (JENKINS-25784) Select sandbox mode by default if current user lacks RUN_SCRIPTS
Jesse Glick started work on JENKINS-25784 Select sandbox mode by default if current user lacks RUN_SCRIPTS Change By: Jesse Glick (03/Mar/15 2:41 PM) Status: Open InProgress 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] [html5-notifier-plugin] (JENKINS-27222) Settings not persisted after jenkins reboot
Giovanni Toraldo (ClouDesire) created JENKINS-27222 Settings not persisted after jenkins reboot Issue Type: Bug Assignee: Gavin Mogan Components: html5-notifier-plugin Created: 03/Mar/15 2:45 PM Description: Everytime I change some settings under HTML5 Notification Configuration (typically Default Notification Timeout) they get applied, but after a jenkins restart they returns to default values. Project: Jenkins Priority: Minor Reporter: Giovanni Toraldo (ClouDesire) 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] [script-security-plugin] (JENKINS-25784) Select sandbox mode by default if current user lacks RUN_SCRIPTS
SCM/JIRA link daemon commented on JENKINS-25784 Select sandbox mode by default if current user lacks RUN_SCRIPTS Code changed in jenkins User: Jesse Glick Path: .gitignore src/main/resources/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/SecureGroovyScript/config.jelly src/test/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/SecureGroovyScriptTest.java http://jenkins-ci.org/commit/script-security-plugin/6841fe781179924663d8090df5c492436203621c Log: Merge pull request #10 from tfennelly/sandbox-defaulting JENKINS-25784 Defaulting of sandbox mode based on RUN_SCRIPTS privs Compare: https://github.com/jenkinsci/script-security-plugin/compare/6fbcd41dc99a...6841fe781179 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-27223) Clicking Login when you have 30+ slaves defaults you to the bottom of the web page
Lorelei McCollum created JENKINS-27223 Clicking Login when you have 30+ slaves defaults you to the bottom of the web page Issue Type: Bug Assignee: Unassigned Components: core Created: 03/Mar/15 2:45 PM Description: Since we upgraded to 1.599 on the login of Jenkins it scrolls you all the way to the bottom of the page. We have 30 jenkins slaves, so it scrolls you to the bottom of the last slave, so the login UI is not visible. Then you have to scroll all the way back to the top before you can log in to jenkins I can provide more details if necessary, but I think it has to do with the amount of jenkins slaves we have Project: Jenkins Priority: Minor Reporter: Lorelei McCollum 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] [audit2db-plugin] (JENKINS-27224) Generating DDL file does not work
Per Östman updated JENKINS-27224 Generating DDL file does not work Change By: Per Östman (03/Mar/15 2:50 PM) Priority: Minor Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [audit2db-plugin] (JENKINS-27224) Generating DDL file does not work
Per Östman created JENKINS-27224 Generating DDL file does not work Issue Type: Bug Assignee: Unassigned Components: audit2db-plugin Created: 03/Mar/15 2:50 PM Description: Created database for plugin to use Installed the audit2db plugin Copied database driver (SQLServer and Oracle) to plugin_folder/WEB-INF/lib Changed owner and group for the two drivers to the account running Jenkins Verified that plugin home folder is owned by account running Jenkins Restarted Jenkins Configured plugin to use database (tried both Oracle and SQLServer) Verified test connection to database works Clicked on button to generate DDL Result: Error: jenkins_audit2db.dll (No such file or directory) Expected: File to be created and displayed Environment: Jenkins master on CentOS 6.6 Project: Jenkins Priority: Minor Reporter: Per Östman 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] [buildtriggerbadge-plugin] (JENKINS-26186) Last Build Trigger Column does not print author name
Baptiste Mathus commented on JENKINS-26186 Last Build Trigger Column does not print author name Hi, just had a look. If you put your mouse over the icon, the title is there. Indeed, the text seems to be not there anymore (I didn't see since I don't personally use that very feature). Could you tell us a plugin version where it was working, and one when it didn't work anymore? That'd help investigate. Even better, file a Pull Request, I promise I'll have look. HTH 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-27188) BUILDID and BUILD_TAG from previous project
Daniel Beck commented on JENKINS-27188 BUILDID and BUILD_TAG from previous project The cause and fix for this is the same as for JENKINS-27178. This will be fixed in 1.601 (despite what the changelog on the Jenkins website might say). 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] [buildtriggerbadge-plugin] (JENKINS-27225) Support the workflow-plugin
Baptiste Mathus created JENKINS-27225 Support the workflow-plugin Issue Type: Bug Assignee: Baptiste Mathus Components: buildtriggerbadge-plugin Created: 03/Mar/15 2:56 PM Description: Currently, build of a workflow job don't have the buildtriggerbadge icons. Let's add it there too! Project: Jenkins Priority: Minor Reporter: Baptiste Mathus 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.
