[JIRA] [matrix-project] (JENKINS-23902) Matrix parent takes executor slot and blocks children
Oleg Nenashev resolved JENKINS-23902 as Fixed Matrix parent takes executor slot and blocks children Closing as Fixed. Please reopen if upgrading to throttle-concurrents-1.8.4 does not resolve the issue Change By: Oleg Nenashev (13/Oct/14 8:03 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25116) Jenkins won't schedule builds
Daniel Beck resolved JENKINS-25116 as Duplicate Jenkins wont schedule builds Duplicates JENKINS-12875. Change By: Daniel Beck (13/Oct/14 8:13 AM) 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] [core] (JENKINS-17170) Jenkins auto install tools feature floods Nexus of HTTP request
Daniel Beck commented on JENKINS-17170 Jenkins auto install tools feature floods Nexus of HTTP request Kanstantsin Shautsou: AFAIU the difference is that DownloadFromURL installer is for publicly available distributions based on files with specific assigned version numbers, while ZipExtraction can use arbitrary user-provided paths, including e.g. "currentTools.zip", a file updated whenever there's a change. So the former can rather safely assume that something downloaded once doesn't need to be redownloaded, while the latter cannot. 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-25120) Failed to archive artifacts: *.tar.gz NoClassDefFoundError
Aviv Yam created JENKINS-25120 Failed to archive artifacts: *.tar.gz NoClassDefFoundError Issue Type: Bug Assignee: Unassigned Components: core Created: 13/Oct/14 8:39 AM Description: This is critical, since those artifacts will be deleted after the job is finished. 2014-10-10 16:22:32 ERROR: Failed to archive artifacts: *.tar.gz 2014-10-10 16:22:32 java.io.IOException: java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: Could not initialize class jnr.posix.JavaLibCHelper 2014-10-10 16:22:32 at hudson.FilePath.copyRecursiveTo(FilePath.java:2047) 2014-10-10 16:22:32 at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61) 2014-10-10 16:22:32 at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:183) 2014-10-10 16:22:32 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 2014-10-10 16:22:32 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:772) 2014-10-10 16:22:32 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:736) 2014-10-10 16:22:32 at hudson.model.Build$BuildExecution.post2(Build.java:183) 2014-10-10 16:22:32 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:685) 2014-10-10 16:22:32 at hudson.model.Run.execute(Run.java:1757) 2014-10-10 16:22:32 at hudson.matrix.MatrixRun.run(MatrixRun.java:146) 2014-10-10 16:22:32 at hudson.model.ResourceController.execute(ResourceController.java:88) 2014-10-10 16:22:32 at hudson.model.Executor.run(Executor.java:234) 2014-10-10 16:22:32 Caused by: java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: Could not initialize class jnr.posix.JavaLibCHelper 2014-10-10 16:22:32 at hudson.remoting.Channel$3.adapt(Channel.java:772) 2014-10-10 16:22:32 at hudson.remoting.Channel$3.adapt(Channel.java:767) 2014-10-10 16:22:32 at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55) 2014-10-10 16:22:32 at hudson.FilePath.copyRecursiveTo(FilePath.java:2045) 2014-10-10 16:22:32 ... 11 more 2014-10-10 16:22:32 Caused by: java.lang.NoClassDefFoundError: Could not initialize class jnr.posix.JavaLibCHelper 2014-10-10 16:22:32 at jnr.posix.JavaPOSIX.init(JavaPOSIX.java:31) 2014-10-10 16:22:32 at jnr.posix.POSIXFactory.getJavaPOSIX(POSIXFactory.java:91) 2014-10-10 16:22:32 at jnr.posix.POSIXFactory.loadPOSIX(POSIXFactory.java:57) 2014-10-10 16:22:32 at jnr.posix.LazyPOSIX.loadPOSIX(LazyPOSIX.java:33) 2014-10-10 16:22:32 at jnr.posix.LazyPOSIX.posix(LazyPOSIX.java:29) 2014-10-10 16:22:32 at jnr.posix.LazyPOSIX.stat(LazyPOSIX.java:267) 2014-10-10 16:22:32 at hudson.util.IOUtils.mode(IOUtils.java:128) 2014-10-10 16:22:32 at hudson.util.io.TarArchiver.visit(TarArchiver.java:101) 2014-10-10 16:22:32 at hudson.util.DirScanner.scanSingle(DirScanner.java:49) 2014-10-10 16:22:32 at hudson.FilePath$ExplicitlySpecifiedDirScanner.scan(FilePath.java:2571) 2014-10-10 16:22:32 at hudson.FilePath.writeToTar(FilePath.java:2083) 2014-10-10 16:22:32 at hudson.FilePath.access$1000(FilePath.java:180) 2014-10-10 16:22:32 at hudson.FilePath$41.invoke(FilePath.java:2024) 2014-10-10 16:22:32 at hudson.FilePath$41.invoke(FilePath.java:2020) 2014-10-10 16:22:32 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2492) 2014-10-10 16:22:32 at hudson.remoting.UserRequest.perform(UserRequest.java:118) 2014-10-10 16:22:32 at hudson.remoting.UserRequest.perform(UserRequest.java:48) 2014-10-10 16:22:32 at hudson.remoting.Request$2.run(Request.java:328) 2014-10-10 16:22:32 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 2014-10-10 16:22:32 at java.util.concurrent.FutureTask.run(FutureTask.java:262) 2014-10-10 16:22:32 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 2014-10-10 16:22:32 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 2014-10-10 16:22:32 at java.lang.Thread.run(Thread.java:744) 2014-10-10 16:22:32 Sending e-mails to: aviv.yamsim...@emc.com 2014-10-10 16:22:37 Finished: FAILURE
[JIRA] [core] (JENKINS-25120) Failed to archive artifacts: *.tar.gz NoClassDefFoundError
Daniel Beck commented on JENKINS-25120 Failed to archive artifacts: *.tar.gz NoClassDefFoundError All nodes (Jenkins master and slave) are CentOS 6.5? Does this affect all of them, or only one? Since when, did it ever work? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18682) Strange NoClassDefFoundError on slave
Aviv Yam commented on JENKINS-18682 Strange NoClassDefFoundError on slave W.E Here the new issue - JENKINS-25120 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-25120) Failed to archive artifacts: *.tar.gz NoClassDefFoundError
Aviv Yam commented on JENKINS-25120 Failed to archive artifacts: *.tar.gz NoClassDefFoundError yes, all are CentOS 6.5. Yes it worked and working! But we encounter this issue several times and it become critical for us. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-4289) Hudson subversion checkout causes files to appear modified if they have no revision history
David Kocher commented on JENKINS-4289 Hudson subversion checkout causes files to appear modified if they have no revision history Reproducible with 1.583 and Subversion Plugin 2.4.4. I can confirm it does also affect Ant builds. 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] [p4] (JENKINS-25085) email-ext showPaths does not work with p4-plugin
Paul Allen commented on JENKINS-25085 email-ext showPaths does not work with p4-plugin Happy to try and support this, but I'm going to need a lot more to go on here. The change data is recorded in the XML files; the parser is there. I'm guessing that an enhancement is needed in the email-ext plugin to access/read the new format. 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-24926) Connection to slave constantly breaks, java process can only be kill -9-ed
Johannes Wienke commented on JENKINS-24926 Connection to slave constantly breaks, java process can only be kill -9-ed Alright, after restarting the jenkins and until waiting that the mavericks slave disappeared again, I can now find the following log in the web interface: Oct 10, 2014 5:41:38 PM FINE hudson.slaves.ChannelPinger Set up a remote ping for archlinux_64bit Oct 10, 2014 5:41:38 PM FINE hudson.slaves.ChannelPinger Ping thread started for hudson.remoting.Channel@86122c5:archlinux_64bit with a 5 minute interval Oct 10, 2014 5:41:38 PM FINE hudson.slaves.ChannelPinger Set up a remote ping for MAC_OS_mavericks_64bit Oct 10, 2014 5:41:38 PM FINE hudson.slaves.ChannelPinger Ping thread started for hudson.remoting.Channel@a50c03b:MAC_OS_mavericks_64bit with a 5 minute interval Oct 10, 2014 5:41:43 PM FINE hudson.slaves.ChannelPinger Set up a remote ping for roboard Oct 10, 2014 5:41:43 PM FINE hudson.slaves.ChannelPinger Ping thread started for hudson.remoting.Channel@40cbbb77:roboard with a 5 minute interval Oct 10, 2014 5:41:45 PM FINE hudson.slaves.ChannelPinger Set up a remote ping for ubuntu_lucid_32bit Oct 10, 2014 5:41:45 PM FINE hudson.slaves.ChannelPinger Ping thread started for hudson.remoting.Channel@129056bd:ubuntu_lucid_32bit with a 5 minute interval Oct 10, 2014 5:41:45 PM FINE hudson.slaves.ChannelPinger Set up a remote ping for ubuntu_trusty_32bit Oct 10, 2014 5:41:45 PM FINE hudson.slaves.ChannelPinger Ping thread started for hudson.remoting.Channel@13c0c489:ubuntu_trusty_32bit with a 5 minute interval Oct 10, 2014 5:41:46 PM FINE hudson.slaves.ChannelPinger Set up a remote ping for ubuntu_precise_32bit Oct 10, 2014 5:41:46 PM FINE hudson.slaves.ChannelPinger Ping thread started for hudson.remoting.Channel@46296957:ubuntu_precise_32bit with a 5 minute interval Oct 10, 2014 5:41:46 PM FINE hudson.slaves.ChannelPinger Set up a remote ping for ubuntu_precise_64bit Oct 10, 2014 5:41:46 PM FINE hudson.slaves.ChannelPinger Ping thread started for hudson.remoting.Channel@6f500880:ubuntu_precise_64bit with a 5 minute interval Oct 10, 2014 5:41:47 PM FINE hudson.slaves.ChannelPinger Set up a remote ping for ubuntu_trusty_64bit Oct 10, 2014 5:41:47 PM FINE hudson.slaves.ChannelPinger Ping thread started for hudson.remoting.Channel@47ac9f39:ubuntu_trusty_64bit with a 5 minute interval Oct 10, 2014 5:41:48 PM FINE hudson.slaves.ChannelPinger Set up a remote ping for Windows_7_64bit Oct 10, 2014 5:41:48 PM FINE hudson.slaves.ChannelPinger Ping thread started for hudson.remoting.Channel@563367dc:Windows_7_64bit with a 5 minute interval Oct 10, 2014 5:41:49 PM FINE hudson.slaves.ChannelPinger Set up a remote ping for Windows_7_32bit Oct 10, 2014 5:41:49 PM FINE hudson.slaves.ChannelPinger Ping thread started for hudson.remoting.Channel@42ead3f5:Windows_7_32bit with a 5 minute interval Oct 12, 2014 6:55:39 PM INFO hudson.slaves.ChannelPinger$1 onDead Ping failed. Terminating the channel. java.util.concurrent.TimeoutException: Ping started on 1413132699262 hasn't completed at 1413132939263 at hudson.remoting.PingThread.ping(PingThread.java:120) at hudson.remoting.PingThread.run(PingThread.java:81) archlinux_64bit Oct 10, 2014 5:41:38 PM FINE hudson.slaves.ChannelPinger Ping thread started for hudson.remoting.Channel@5f3bbd78:channel with a 5 minute interval roboard Oct 10, 2014 5:41:43 PM FINE hudson.slaves.ChannelPinger Ping thread started for hudson.remoting.Channel@42719c:channel with a 5 minute interval ubuntu_lucid_32bit Oct 10, 2014 5:41:45 PM FINE hudson.slaves.ChannelPinger Ping thread started for hudson.remoting.Channel@5c750:channel with a 5 minute interval ubuntu_precise_32bit Oct 10, 2014 5:41:43 PM FINE hudson.slaves.ChannelPinger Ping thread started for hudson.remoting.Channel@1cdc4a5:channel with a 5 minute interval ubuntu_precise_64bit Oct 10, 2014 5:41:44 PM FINE hudson.slaves.ChannelPinger Ping thread started for hudson.remoting.Channel@52ee4084:channel with a 5 minute interval ubuntu_trusty_32bit Oct 10, 2014 5:41:45 PM FINE hudson.slaves.ChannelPinger Ping thread started for hudson.remoting.Channel@1edc0ad:channel with a 5 minute interval ubuntu_trusty_64bit Oct 10, 2014 5:41:47 PM FINE hudson.slaves.ChannelPinger Ping thread started for hudson.remoting.Channel@23edc0ad:channel with a 5 minute interval Windows_7_32bit Oct 10, 2014 5:41:34 PM FINE hudson.slaves.ChannelPinger Ping thread started for hudson.remoting.Channel@cc9d70:channel with a 5 minute interval
[JIRA] [p4] (JENKINS-19568) Support OpenGrok as SCM Browser for Perforce
Paul Allen closed JENKINS-19568 as Fixed Support OpenGrok as SCM Browser for Perforce 1.0.16 - Basic support added (please open a new JIRA issues/features as required) Change By: Paul Allen (13/Oct/14 9:49 AM) Status: Open Closed Assignee: PaulAllen 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] [p4] (JENKINS-24599) Parameters are not resolved in stream
Paul Allen
resolved JENKINS-24599 as Wont Fix
Parameters are not resolved in stream
As outlined the sanity check can't necessarily expand the ${var}.
The alternative would be to remove the check altogether. If common use changes from explicit paths to expanded vars then I may change the sanity check.
Change By:
Paul Allen
(13/Oct/14 9:55 AM)
Status:
Open
Resolved
Resolution:
WontFix
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] [p4] (JENKINS-24607) Need ability to build changes sequentially
Paul Allen closed JENKINS-24607 as Fixed Need ability to build changes sequentially Added in 1.0.16 Change By: Paul Allen (13/Oct/14 9:57 AM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25020) Accessing parameters of triggered build has strange syntax
Kaaleppi Kekkola commented on JENKINS-25020 Accessing parameters of triggered build has strange syntax Sorry for being confusing. I was actually using Jenkins build parameter named 'user' and I just realized that I also have an environment variable which is named equally. I thought I was experiencing the problem with different parameter names as well but apparently that wasn't the case when testing now. "This seems to be a known issue affecting variables that have already been defined" seems to be the case really. Thanks for the help. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [timestamper] (JENKINS-25091) Timestamper Elapsed time only showing System clock time
David Brown closed JENKINS-25091 as Not A Defect Timestamper Elapsed time only showing System clock time My apologies. After upgrading to the latest version of Jenkins (and re-starting it), the radio button works as I had hoped it would. Change By: David Brown (13/Oct/14 11:38 AM) Status: Open Closed Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-11690) CLI fails to parse argument containing several = signs
Daniel Beck resolved JENKINS-11690 as Fixed CLI fails to parse argument containing several = signs Appears to have been fixed a while ago. A similar issue (JENKINS-21160) occurs in remoting, but it seems unrelated to this. Change By: Daniel Beck (13/Oct/14 11:47 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25020) Accessing parameters of triggered build has strange syntax
Daniel Beck resolved JENKINS-25020 as Not A Defect Accessing parameters of triggered build has strange syntax Change By: Daniel Beck (13/Oct/14 12:00 PM) Status: Open Resolved Resolution: NotADefect 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] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
Andre Doherty commented on JENKINS-21863 WebSphere deployer: deploy to cluster @schaudhari : in case you haven't solved your issue yet, the problem you meet is connected to the mismatch of the certificate shown by your server and the url (console or soap (see serverindex.xml)) you used (128.0.1.212). As for me, i am trying to deploy an app on a server + an ihs web server at the same time, something that is feasible via the console. Is there some trick that allows to do it using the plugin ? Thank you This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkinswalldisplay] (JENKINS-25121) Place a small Console output icon near build number
Kostiantyn Rybnikov created JENKINS-25121 Place a small Console output icon near build number Issue Type: New Feature Assignee: Unassigned Components: jenkinswalldisplay Created: 13/Oct/14 12:52 PM Description: I propose a minor UI tweak. I have a strong feeling that a lot of people often need to get into "console output" scfeen for a build-task that is running, and currently that involves few steps to do. I think it would be quite nice to put small terminal icon next to currently-building item (at least) in a build list. p.s.: sorry, couldn't find any component for this Project: Jenkins Priority: Minor Reporter: Kostiantyn Rybnikov 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-15063) support for multiple security realms with failover
Kanstantsin Shautsou commented on JENKINS-15063 support for multiple security realms with failover I'm not specialist on Atlassian products, but probably Crowd may do this, have you looked on 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] [extended-choice-parameter] (JENKINS-22924) [Extended Choice Parameter] - Parameter does not support the definition from CLI
SCM/JIRA link daemon commented on JENKINS-22924 [Extended Choice Parameter] - Parameter does not support the definition from CLI Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/cwctravel/hudson/plugins/extended_choice_parameter/ExtendedChoiceParameterDefinition.java http://jenkins-ci.org/commit/extended-choice-parameter-plugin/8dd582e69fc55c7d662a8c362b35f7d5b581e2a7 Log: FIXED JENKINS-22924 - Allow the parameter specification from Jenkins CLI The parameter takes the comma-separated list of values. Signed-off-by: Oleg Nenashev o.v.nenas...@gmail.com Conflicts: src/main/java/com/cwctravel/hudson/plugins/extended_choice_parameter/ExtendedChoiceParameterDefinition.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] [extended-choice-parameter] (JENKINS-23359) Multi-level choice modes do not support URL paths to property files
SCM/JIRA link daemon commented on JENKINS-23359 Multi-level choice modes do not support URL paths to property files Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/cwctravel/hudson/plugins/extended_choice_parameter/ExtendedChoiceParameterDefinition.java http://jenkins-ci.org/commit/extended-choice-parameter-plugin/5bede415b9d916f629d950644b8699af1214ef93 Log: FIXED JENKINS-23359 - Added support of URL paths to multi-level choice options Signed-off-by: Oleg Nenashev o.v.nenas...@gmail.com 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] [cloudbees-folder] (JENKINS-25078) Default health metric is potentially expensive
Jesse Glick commented on JENKINS-25078 Default health metric is potentially expensive For better discoverability, Folder.getBuildHealthReports could check for an empty reporter list, and if so display a special report (with no icon) that just offers the hint that you can enable metrics if you want them. 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] [publish-over-ssh] (JENKINS-25122) Permanent error message Either Source files, Exec command or both must be supplied
Nicolas Baumann created JENKINS-25122 Permanent error message Either Source files, Exec command or both must be supplied Issue Type: Bug Assignee: bap Attachments: [Jenkins]_2014-10-13_16-17-58.png Components: publish-over-ssh Created: 13/Oct/14 2:21 PM Description: No matter how the fields are fed, even if all optional fields are fed, it displays the message "Either Source files, Exec command or both must be supplied", which should disappear as soon as one of the mentionned fields are fed by the user. Everything's working fine but every user that is new to the plugin thinks there's something missing to feed. It also seems a common rule in Jenkins that red messages disappear in real-time as soon as problem is fixed. Project: Jenkins Labels: publish-over-ssh Priority: Major Reporter: Nicolas Baumann 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] [publish-over-ssh] (JENKINS-25122) Permanent error message Either Source files, Exec command or both must be supplied
Nicolas Baumann commented on JENKINS-25122 Permanent error message Either Source files, Exec command or both must be supplied Jenkins version : 1.583 Publish Over SSH version : 1.11 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] [configurationslicing] (JENKINS-25123) Configuration Slicing plugin 1.39 does not support build timeout plugin 1.14
Jochen Ehret created JENKINS-25123 Configuration Slicing plugin 1.39 does not support build timeout plugin 1.14 Issue Type: Bug Assignee: mdonohue Components: configurationslicing Created: 13/Oct/14 2:32 PM Description: We've installed the abovementioned plugins on Jenkins 1.565.3. The slicing plugin however doesn't support timeout configurations. In the Jenkins log we can see: Oct 13, 2014 3:54:06 PM INFO configurationslicing.ConfigurationSlicing getAxes NOT Loaded: class configurationslicing.buildtimeout.BuildTimeoutSlicer Oct 13, 2014 3:54:06 PM INFO configurationslicing.ConfigurationSlicing getAxes NOT Loaded: class configurationslicing.buildtimeout.BuildTimeoutSlicer2 Is there anything wrong with our Jenkins configuration or do we need additional plugins? Thanks for your support and best regards, Jochen. Project: Jenkins Priority: Major Reporter: Jochen Ehret 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-17170) Jenkins auto install tools feature floods Nexus of HTTP request
Kanstantsin Shautsou commented on JENKINS-17170 Jenkins auto install tools feature floods Nexus of HTTP request So we need have some checkbox to control this behavior. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-25066) Build on the same node option triggers runs on node with same label and not on identical node
Tobias Del Fabro updated JENKINS-25066 Build on the same node option triggers runs on node with same label and not on identical node Change By: Tobias Del Fabro (13/Oct/14 2:48 PM) Attachment: build_jobB.xml Attachment: build_jobC.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-25066) Build on the same node option triggers runs on node with same label and not on identical node
Tobias Del Fabro commented on JENKINS-25066 Build on the same node option triggers runs on node with same label and not on identical node Oh, i'm sorry! I obviously picked the wrong build.xml file from my server, despite re-checking. Please find attached the two correct files for jobB and jobC: jobB ran on the correct slave "debian-build" @revision 20 jobB triggered jobC on the (wrong) slave "debian-build2" due to identical labeling of both slaves jobC ran on slave "debian-build2" without SVN checkout. thus, on @revision 10 from the previous build on that slave I assume the cause can be found in hudson.plugins.parameterizedtrigger.NodeParameters.java line 36: nodeLabel = node.getSelfLabel(); which should basically be nodeLabel = node.getNodeName(); 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] (JENKINS-25118) GroovyPostbuildRecorder$BadgeManager.setBuildNumber cannot be used in sandbox
Jesse Glick started work on JENKINS-25118 GroovyPostbuildRecorder$BadgeManager.setBuildNumber cannot be used in sandbox Change By: Jesse Glick (13/Oct/14 2:53 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] [script-security] (JENKINS-25118) GroovyPostbuildRecorder$BadgeManager.setBuildNumber cannot be used in sandbox
SCM/JIRA link daemon commented on JENKINS-25118 GroovyPostbuildRecorder$BadgeManager.setBuildNumber cannot be used in sandbox Code changed in jenkins User: ikedam Path: src/main/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/GroovyCallSiteSelector.java http://jenkins-ci.org/commit/script-security-plugin/ba5b9ac9701d2e051fdf436b5cb43dfa4f027462 Log: FIXED JENKINS-25118 Matches primitives and wrapper types when matching methods. 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] (JENKINS-25118) GroovyPostbuildRecorder$BadgeManager.setBuildNumber cannot be used in sandbox
SCM/JIRA link daemon resolved JENKINS-25118 as Fixed GroovyPostbuildRecorder$BadgeManager.setBuildNumber cannot be used in sandbox Change By: SCM/JIRA link daemon (13/Oct/14 3:05 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] [script-security] (JENKINS-25118) GroovyPostbuildRecorder$BadgeManager.setBuildNumber cannot be used in sandbox
SCM/JIRA link daemon commented on JENKINS-25118 GroovyPostbuildRecorder$BadgeManager.setBuildNumber cannot be used in sandbox Code changed in jenkins User: ikedam Path: src/test/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/SandboxInterceptorTest.java http://jenkins-ci.org/commit/script-security-plugin/80d2ccb63ebf517cfe1c68ba1f18267fcded2472 Log: JENKINS-25118 Added a test to reproduce JENKINS-25118 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] (JENKINS-25118) GroovyPostbuildRecorder$BadgeManager.setBuildNumber cannot be used in sandbox
SCM/JIRA link daemon commented on JENKINS-25118 GroovyPostbuildRecorder$BadgeManager.setBuildNumber cannot be used in sandbox Code changed in jenkins User: Jesse Glick Path: src/test/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/SandboxInterceptorTest.java http://jenkins-ci.org/commit/script-security-plugin/0240639d543544ef9546e11ca32c77b5b36c6628 Log: JENKINS-25118 Enhanced test to make sure the call can be whitelisted, too. 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-16395) The path parameter in the REST API should support wildcard '*'.
Jesse Glick commented on JENKINS-16395 The path parameter in the REST API should support wildcard *. The bot does not listen to commits to the @stapler org as far as I know. 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] (JENKINS-25119) Sandbox cannot handle methods Groovy provides additionally
Jesse Glick assigned JENKINS-25119 to Kohsuke Kawaguchi Sandbox cannot handle methods Groovy provides additionally This is at root a problem in the Groovy Sandbox library, that it fails to tell an interceptor the real call site. Change By: Jesse Glick (13/Oct/14 3:07 PM) Assignee: JesseGlick KohsukeKawaguchi 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-16395) The path parameter in the REST API should support wildcard '*'.
Jesse Glick commented on JENKINS-16395 The path parameter in the REST API should support wildcard *. BTW _api.jelly needs to get updated to document this syntax. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-slaves] (JENKINS-20108) SSH slaves can block for a long time in NativePRNG
Jesse Glick commented on JENKINS-20108 SSH slaves can block for a long time in NativePRNG Unfortunate that Trilead SSH in bundled in core; we would really prefer such updates to done directly in the ssh-slaves plugin. Has this issue been filed upstream? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-slaves] (JENKINS-20108) SSH slaves can block for a long time in NativePRNG
Jesse Glick updated JENKINS-20108 SSH slaves can block for a long time in NativePRNG Change By: Jesse Glick (13/Oct/14 3:15 PM) Labels: lts-candidate performance This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-slaves] (JENKINS-20108) SSH slaves can block for a long time in NativePRNG
Jesse Glick assigned JENKINS-20108 to Kohsuke Kawaguchi SSH slaves can block for a long time in NativePRNG Change By: Jesse Glick (13/Oct/14 3:17 PM) Assignee: KohsukeKawaguchi 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] [junit-plugin] (JENKINS-25124) Junit publisher doesn't work for more than one test report
Lorelei McCollum created JENKINS-25124 Junit publisher doesnt work for more than one test report Issue Type: Bug Assignee: Unassigned Components: junit-plugin Created: 13/Oct/14 3:22 PM Description: In the post build I would like to graph more than one test report for a given run. The flexible publish plugin allows you to use the Junit plugin more than once in a post build step, this does work well, however the main history test trend graph on the main page does not show unique graphs for each Report. It only shows one of the reports and displays the same graph for the second report To Explain better I want to publish reports for BVT1.xml and BVT0.xml.. I want to have separate test trend graphs for each of these. I use the flexible publish plugin + junit plugin in the post build and set one to find the BVT1.xml and the other to find BVT0.xml. When the job runs, it does correctly find the TestResults, but the main page for the job will show two test trend graphs of the same thing, so seems that is not "unique" 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] [ssh-slaves] (JENKINS-20108) SSH slaves can block for a long time in NativePRNG
Jesse Glick commented on JENKINS-20108 SSH slaves can block for a long time in NativePRNG For the record: The switch doesn't cause JVM to use /dev/urandom instead of /dev/random. It just bypasses both. That is what happens when you use the obvious -Djava.security.egd=file:/dev/urandom When you use the tricky -Djava.security.egd=file:/dev/./urandom then this does not match URL_DEV_URANDOM and so /dev/urandom is used. 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] [dependency-check-jenkins] (JENKINS-25125) Verbose log activate verbose for all Jenkins
Henri Gomez created JENKINS-25125 Verbose log activate verbose for all Jenkins Issue Type: Bug Assignee: Unassigned Components: dependency-check-jenkins Created: 13/Oct/14 3:33 PM Description: When selecting Enable verbose logging is Analysis part, verbose logging is activated for DC but also Jenkins core and plugins. It end up with javaX.log in jenkins home dir (and jenkins client). And log could be very huge Environment: Jenkins LTS 1.565.3 - DependencyCheck 1.2.4 Project: Jenkins Priority: Minor Reporter: Henri Gomez 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] [extended-choice-parameter] (JENKINS-24639) ExtendedChoiceParameter not supported in Jenkins CLI (ssh)
Oleg Nenashev resolved JENKINS-24639 as Duplicate ExtendedChoiceParameter not supported in Jenkins CLI (ssh) It should be fixed in 0.34 (see JENKINS-22924) Please re-open JENKINS-22924 if you still experience the issue on the new version Hope that vimil starts updating the Version history at some point Change By: Oleg Nenashev (13/Oct/14 3:59 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] [extended-choice-parameter] (JENKINS-25126) Add support of custom delimiters in multi-level CSV files
Oleg Nenashev created JENKINS-25126 Add support of custom delimiters in multi-level CSV files Issue Type: Improvement Assignee: vimil Components: extended-choice-parameter Created: 13/Oct/14 4:01 PM Description: The default \t is weird, but seems we cannot use another one without regressions Project: Jenkins Priority: Minor Reporter: Oleg Nenashev 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] [github] (JENKINS-25127) Hook uninstalled if job is in a subfolder
Leandro Lucarella created JENKINS-25127 Hook uninstalled if job is in a subfolder Issue Type: Bug Assignee: Unassigned Components: github Created: 13/Oct/14 4:06 PM Description: After I started using the CloudBees Folders Plugin and moving jobs into folders, I noticed when I pushed stuff to github, builds were no longer triggered. I checked in GitHub and the Jenkins plugin was not enabled. I go to the job, save it again (the option "Build when a change is pushed to GitHub" is always checked and is the only method to trigger a build that's activated) and I see the hook is created, but after a minute or 2, it gets removed again. GitHub security log says the removal request comes from the Jenkins server. Looking at the source code, I see where hooks are being removed: https://github.com/jenkinsci/github-plugin/blob/49bc59d79707808d73eb0f9d5c97996fd5525d08/src/main/java/com/cloudbees/jenkins/Cleaner.java Activating the log for com.cloudbees.jenkins.Cleaner I can definitely see it's Jenkins the one removing the hooks. Why is considering jobs inside subfolders as "not interesting" I have no idea. Looking at the "GitHub Hook Log" for a top-level project, I see something like this: Last GitHub Push Started on Oct 13, 2014 3:21:08 PM Polling SCM changes on master Using strategy: Default poll Last Built Revision: Revision ae6386642259cb1b675730fbce96deaa29d3a369 (origin/master) git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repositories git config remote.origin.url g...@github.com:sociomantic/git-hub.git # timeout=10 Fetching upstream changes from g...@github.com:sociomantic/git-hub.git git --version # timeout=10 using GIT_SSH to set credentials GitHub jenkins-admin git fetch --tags --progress g...@github.com:sociomantic/git-hub.git +refs/heads/:refs/remotes/origin/ Polling for changes in Seen branch in repository origin/master git log --full-history --no-abbrev --format=raw -M -m --raw ae6386642259cb1b675730fbce96deaa29d3a369..7618cac3f33deb84868332acc64572b60d7adf7e # timeout=10 Done. Took 3.4 sec Changes found (I don't know why is it polling anything in the first place because Polling is not enabled) For a job in a subfolder, I see this log instead: Environment: Jenkins ver. 1.565.3, GitHub plugin 1.9.1, CloudBees Folders Plugin 4.6.1 Project: Jenkins Priority: Critical Reporter: Leandro Lucarella 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] [github] (JENKINS-25127) Hook uninstalled if job is in a subfolder
Leandro Lucarella updated JENKINS-25127 Hook uninstalled if job is in a subfolder Change By: Leandro Lucarella (13/Oct/14 4:09 PM) Description: AfterIstartedusingtheCloudBeesFoldersPluginandmovingjobsintofolders,InoticedwhenIpushedstufftogithub,buildswerenolongertriggered.IcheckedinGitHubandtheJenkinspluginwasnotenabled.Igotothejob,saveitagain(theoptionBuildwhenachangeispushedtoGitHubisalwayscheckedandistheonlymethodtotriggerabuildthatsactivated)andIseethehookiscreated,butafteraminuteor2,itgetsremovedagain.GitHubsecuritylogsaystheremovalrequestcomesfromtheJenkinsserver.Lookingatthesourcecode,Iseewherehooksarebeingremoved:https://github.com/jenkinsci/github-plugin/blob/49bc59d79707808d73eb0f9d5c97996fd5525d08/src/main/java/com/cloudbees/jenkins/Cleaner.javaActivatingthelogforcom.cloudbees.jenkins.CleanerIcandefinitelyseeitsJenkinstheoneremovingthehooks.WhyisconsideringjobsinsidesubfoldersasnotinterestingIhavenoidea. LookingattheGitHubHookLogforatop-levelproject,Iseesomethinglikethis:---LastGitHubPushStartedonOct13,20143:21:08PMPollingSCMchangesonmasterUsingstrategy:Default[poll]LastBuiltRevision:Revisionae6386642259cb1b675730fbce96deaa29d3a369(origin/master)gitrev-parse--is-inside-work-tree#timeout=10FetchingchangesfromtheremoteGitrepositoriesgitconfigremote.origin.urlg...@github.com:sociomantic/git-hub.git#timeout=10Fetchingupstreamchangesfromg...@github.com:sociomantic/git-hub.gitgit--version#timeout=10usingGIT_SSHtosetcredentialsGitHubjenkins-admingitfetch--tags--progressg...@github.com:sociomantic/git-hub.git+refs/heads/*:refs/remotes/origin/*PollingforchangesinSeenbranchinrepositoryorigin/mastergitlog--full-history--no-abbrev--format=raw-M-m--rawae6386642259cb1b675730fbce96deaa29d3a369..7618cac3f33deb84868332acc64572b60d7adf7e#timeout=10Done.Took3.4secChangesfound---(IdontknowwhyisitpollinganythinginthefirstplacebecausePollingisnotenabled)Forajobinasubfolder,Iseethisloginstead:--- 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] [scm-sync-configuration] (JENKINS-25128) SCM Sync pushes the scm-sync-configuration/checkoutConfiguration/jobs directory to the repo
Simeon Panayotov created JENKINS-25128 SCM Sync pushes the scm-sync-configuration/checkoutConfiguration/jobs directory to the repo Issue Type: Bug Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 13/Oct/14 4:10 PM Description: It could be because of this default include rule: */jobs//config.xml. I believe the jobs directory in scm-sync-configuration/**/ should be excluded. Project: Jenkins Priority: Minor Reporter: Simeon Panayotov 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] [scm-sync-configuration] (JENKINS-25128) SCM Sync pushes the scm-sync-configuration/checkoutConfiguration/jobs directory to the repo
Simeon Panayotov updated JENKINS-25128 SCM Sync pushes the scm-sync-configuration/checkoutConfiguration/jobs directory to the repo Change By: Simeon Panayotov (13/Oct/14 4:11 PM) Description: Itcouldbebecauseofthisdefaultincluderule: \ * \ */jobs/ \ */config.xml.Ibelievethejobsdirectoryinscm-sync-configuration/ \ * \ */shouldbeexcluded. 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-25129) SCM Sync Shows Errors in the logs but GIT show no issues.
C. Alex Reober created JENKINS-25129 SCM Sync Shows Errors in the logs but GIT show no issues. Issue Type: Bug Assignee: Frédéric Camblor Attachments: Error.txt Components: core, scm-sync-configuration Created: 13/Oct/14 4:58 PM Description: I have had to turn off the "Dsiplay SCM Sync Status" on my system, because I am getting the attached error twice every 20 minutes or so, and it is making the screen scroll to display all the errors. Checking the SCM process to fix I cd to /var/lib/jenkins/scm-sync-configuration/checkoutConfiguration Run "git status", and get the this: On branch master Your branch is up-to-date with 'origin/master'. nothing to commit, working directory clean Still get the same error on the next run. Environment: AWS Instance = Amazon Linux AMI release 2014.09 Jenkins = ver. 1.582 SCM Sync Configuration Plugin = 0.0.8 Project: Jenkins Priority: Minor Reporter: C. Alex Reober 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-25129) SCM Sync Shows Errors in the logs but GIT show no issues.
C. Alex Reober commented on JENKINS-25129 SCM Sync Shows Errors in the logs but GIT show no issues. More info: git version git version 2.1.0 java -version java version "1.7.0_65" OpenJDK Runtime Environment (amzn-2.5.1.2.45.amzn1-x86_64 u65-b17) OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode) 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] [scm-sync-configuration] (JENKINS-25129) SCM Sync Shows Errors in the logs but GIT show no issues.
Daniel Beck updated JENKINS-25129 SCM Sync Shows Errors in the logs but GIT show no issues. Change By: Daniel Beck (13/Oct/14 5:16 PM) 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] [ssh-slaves] (JENKINS-20108) SSH slaves can block for a long time in NativePRNG
Kohsuke Kawaguchi
commented on JENKINS-20108
SSH slaves can block for a long time in NativePRNG
There's no upstream for trilead ssh anymore. There was an invitation from another fork maintainer to combine the effort, but he was using trilead in different package name, so we couldn't switch.
As for removing this from the core, we need to check if anyone else is using it from their plugins. ssh-plugin can potentially use a child-first classloading to have its copy of trilead, which might be a cheaper way to solve this problem.
Finally, with the {{-Djava.security.egd=file:/dev/./urandom}} switch, I meant /dev/urandom is only used for seeding SHA1PRNG but not for generating actual random numbers.
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-25130) f:dropdownDescriptorSelector ignores help.html for the selected descriptor
Jesse Glick created JENKINS-25130 f:dropdownDescriptorSelector ignores help.html for the selected descriptor Issue Type: Improvement Assignee: Unassigned Components: core Created: 13/Oct/14 5:33 PM Description: f:dropdownDescriptorSelector can pick up help for the whole field. But frequently you would want to specify help for each selectable item. There appears no way to do this, other than adding a f:block with text to the config.jelly of that item, or adding a help-subField.html for one or more of its fields. Project: Jenkins Labels: form-data ui help jelly workflow Priority: Minor Reporter: Jesse Glick 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-25130) f:dropdownDescriptorSelector ignores help.html for the selected descriptor
SCM/JIRA link daemon commented on JENKINS-25130 f:dropdownDescriptorSelector ignores help.html for the selected descriptor Code changed in jenkins User: Jesse Glick Path: cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition/config.jelly http://jenkins-ci.org/commit/workflow-plugin/f5bf1a6ded8f1dae2a39c339308cf76b169091b2 Log: JENKINS-25130 Add help per item when available. Looks a little odd because there is nothing we can put in the columns prior to the help button. 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] [cucumber-testresult-plugin] (JENKINS-21835) Cucumber Test Result Plugin does not correctly parse Scenario Outline results
Kanstantsin Shautsou commented on JENKINS-21835 Cucumber Test Result Plugin does not correctly parse Scenario Outline results Is there any news? 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] [other] (JENKINS-2551) Option to compress build logs
Oleg Nenashev commented on JENKINS-2551 Option to compress build logs The plugin has not been released yet 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] [heavy-job] (JENKINS-11548) Heavy Job plugin not working with Matrix jobs
Oleg Nenashev commented on JENKINS-11548 Heavy Job plugin not working with Matrix jobs The fix from ks.vladimir: https://github.com/jenkinsci/heavy-job-plugin/pull/1 BTW, the fix cannot be merged This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-agent] (JENKINS-18897) ssh-agent slave: 'JCE cannot authenticate the provider BC', because 'Class is on the bootclasspath'
milki mlk
commented on JENKINS-18897
ssh-agent slave: JCE cannot authenticate the provider BC, because Class is on the bootclasspath
I installed the unlimited policy and verified in the slave node's script console with:
import javax.crypto.Cipher;
int maxKeyLen = Cipher.getMaxAllowedKeyLength("AES");
println(maxKeyLen);
And got output of 2147483647 instead of 128. But I still have the same error.
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] [mask-passwords] (JENKINS-22770) Mask password plugin fails to mask password with $ character in the middle of the password
Alex LeDonne commented on JENKINS-22770 Mask password plugin fails to mask password with $ character in the middle of the password Confirming that password masking fails also if the dollar sign is the last character in the password. 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] [github] (JENKINS-25127) Hook uninstalled if job is in a subfolder
Daniel Beck commented on JENKINS-25127 Hook uninstalled if job is in a subfolder This line is bogus, needs to be getAllItems(...): https://github.com/jenkinsci/github-plugin/blob/49bc59d79707808d73eb0f9d5c97996fd5525d08/src/main/java/com/cloudbees/jenkins/Cleaner.java#L55 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] [other] (JENKINS-2551) Option to compress build logs
Oleg Nenashev commented on JENKINS-2551 Option to compress build logs Forked and released Daniel's plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-25066) Build on the same node option triggers runs on node with same label and not on identical node
Daniel Beck commented on JENKINS-25066 Build on the same node option triggers runs on node with same label and not on identical node Does 'debian-slave2' have the label 'debian-slave'? If so, that's a config issue. Fix that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-25066) Build on the same node option triggers runs on node with same label and not on identical node
Daniel Beck edited a comment on JENKINS-25066 Build on the same node option triggers runs on node with same label and not on identical node Does 'debian-build2' have the label 'debian-build'? If so, that's a config issue confusing not just this particular component. Fix that, e.g. by renaming the first node to debian-build1, and giving both just the 'debian-build' label. 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] [multiple-scms] (JENKINS-25131) Multiple SCMs Plugin doesn't track multiple Git Repo SHA1
Tony Yang created JENKINS-25131 Multiple SCMs Plugin doesnt track multiple Git Repo SHA1 Issue Type: Bug Assignee: Kevin Bell Components: multiple-scms Created: 13/Oct/14 7:24 PM Description: When we go to each build log, as in ...jenkins/job/job name/1, we have a list of Changes from Git which identifies the corresponding SHA1 against the changes. However, since Jenkins job configure only gives 1 GitHub project url, and we are using the Multiple Git plugin, the SHA1 attached always refer to the 1 repo, even though it might belong to a different repo. Example: repo1 -change 1: SHA1=12345 repo2 -change 3: SHA1=09876 The change list on that page shows Changes Git Changelog updated by ... (commit: 12345) (detail) Getting gitzip version (commit: 09876) (detail) When I click on the commit link, they both leads to repo1's commit history. The first link will work because the SHA1 belongs to repo1, the second link will fail Environment: LTS 1.565.3 Project: Jenkins Labels: plugin Priority: Major Reporter: Tony Yang 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] [mask-passwords] (JENKINS-22770) Mask password plugin fails to mask password with $ character in the middle of the password
Daniel Beck commented on JENKINS-22770 Mask password plugin fails to mask password with $ character in the middle of the password The issue description is a bit weird, but it seems to boil down to passwords participating in variable placeholder resolution. Usually, you'd escape a dollar char using another dollar char (foo$$bar becomes foo$bar), but that means the raw value does not match the script output, and the password is shown plain. Only workaround seems to be to not use passwords that don't contain a dollar char. 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-17170) Jenkins auto install tools feature floods Nexus of HTTP request
Daniel Beck commented on JENKINS-17170 Jenkins auto install tools feature floods Nexus of HTTP request Might be sufficient to cache any given URL's state after a check for ~10 seconds. One request per Jenkins instance and URL per 10 seconds should be reasonable. 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] [configurationslicing] (JENKINS-25123) Configuration Slicing plugin 1.39 does not support build timeout plugin 1.14
Daniel Beck edited a comment on JENKINS-25123 Configuration Slicing plugin 1.39 does not support build timeout plugin 1.14 (obsolete... missed essential information in the issue title only) 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] [configurationslicing] (JENKINS-25123) Configuration Slicing plugin 1.39 does not support build timeout plugin 1.14
Daniel Beck commented on JENKINS-25123 Configuration Slicing plugin 1.39 does not support build timeout plugin 1.14 I'm guessing here, but... no Build Timeout Plugin installed? Questions should be directed to IRC or the mailing list. 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] [configurationslicing] (JENKINS-25123) Configuration Slicing plugin 1.39 does not support build timeout plugin 1.14
Daniel Beck commented on JENKINS-25123 Configuration Slicing plugin 1.39 does not support build timeout plugin 1.14 The last version to be supported appears to be 1.11, before https://github.com/jenkinsci/build-timeout-plugin/commit/47e927ceded0c38ec9c6c71304ee4c7c89283ed5#diff-891dfa43e0d85dea7162d46b430299d7L82 which broke https://github.com/jenkinsci/configurationslicing-plugin/blob/master/src/main/java/configurationslicing/buildtimeout/BuildTimeoutSlicer.java#L170 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-4289) Hudson subversion checkout causes files to appear modified if they have no revision history
Daniel Beck commented on JENKINS-4289 Hudson subversion checkout causes files to appear modified if they have no revision history David: What about $Id$ vs. $Id:$ ? Does that make any difference? 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] [youtrack] (JENKINS-24333) No action for executing command from build step
Erik Zielke
commented on JENKINS-24333
No action for executing command from build step
About changelog in an environmnet variable, I had a similar need once, and as far as I can remember there is only IMHO weird ways to get it, e.g. by calling the xml/json api from the build. Maybe there is some plugin which sets that variable. Developing this plugin I have found that the Git Plugin only shows the first line or 80 chars (can't remember which) of the commit message, I get the remaining text by reflection as do the view renders. This might also be an issue when calling the api.
Am I overlooking something or haven't you written the same project twice ("XYZ" instead of "XYZ")? I haven't have time to test it my self yet.
Thanks for mentioning the typo.
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] [promoted-builds] (JENKINS-20492) Re-Execute promotion button is gone
Damien Nozay commented on JENKINS-20492 Re-Execute promotion button is gone https://github.com/jenkinsci/promoted-builds-plugin/pull/45 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] [email-ext] (JENKINS-16181) Jenkins does not try to resend a failed e-mail
Alex Earl resolved JENKINS-16181 as Fixed Jenkins does not try to resend a failed e-mail Fixed in 2.39 Change By: Alex Earl (13/Oct/14 7:57 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-24638) No E-Mail sent when build of new branch fails for first time
Alex Earl assigned JENKINS-24638 to Unassigned No E-Mail sent when build of new branch fails for first time Change By: Alex Earl (13/Oct/14 7:59 PM) Assignee: AlexEarl This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24638) No E-Mail sent when build of new branch fails for first time
Alex Earl updated JENKINS-24638 No E-Mail sent when build of new branch fails for first time If the build doesn't see any changes, then email-ext won't see them either. This needs to be addressed in the SCM. Change By: Alex Earl (13/Oct/14 8:00 PM) Component/s: git Component/s: email-ext 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] [email-ext] (JENKINS-24537) Email-ext: No e-mail when using other/template post-build steps
Alex Earl assigned JENKINS-24537 to Unassigned Email-ext: No e-mail when using other/template post-build steps This needs to be addressed by the template project plugin first. Change By: Alex Earl (13/Oct/14 8:01 PM) Assignee: AlexEarl This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24638) No E-Mail sent when build of new branch fails for first time
Alex Earl updated JENKINS-24638 No E-Mail sent when build of new branch fails for first time Change By: Alex Earl (13/Oct/14 8:00 PM) Labels: email-ext 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-20262) Fix for JENKINS-18629 caused a regression in several plugins
Alex Earl commented on JENKINS-20262 Fix for JENKINS-18629 caused a regression in several plugins Bump, what's the status on this? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24638) No E-Mail sent when build of new branch fails for first time
Daniel Beck commented on JENKINS-24638 No E-Mail sent when build of new branch fails for first time The obvious workaround of course is to trigger the first build immediately after branch creation, so there's a reference point for the first failing build's changelog to compare to. 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-25132) Remote access API - listing culprits using the 'tree' query parameter throws exception
Torsten Ehrhorn created JENKINS-25132 Remote access API - listing culprits using the tree query parameter throws exception Issue Type: Bug Assignee: Unassigned Attachments: 2014-10-13_21h54_14.png, stack-trace.txt Components: core Created: 13/Oct/14 8:13 PM Description: The scenario ... trying to access data for job https://ci.jenkins-ci.org/job/jenkins_rc_branch/ using the XML API note that the latest build #468 is unstable the actual query https://ci.jenkins-ci.org/job/jenkins_rc_branch/api/xml?tree=builds[culprits] throws a java.io.IOException: Failed to write culprits which is Caused by: java.lang.RuntimeException: No author in changeset note that the JSON API throws the same exception ... see the attached screenshot and stack trace for further information. Environment: https://ci.jenkins-ci.org/ running Jenkins ver. 1.565-SNAPSHOT (rc-05/20/2014 18:32 GMT-kohsuke) Project: Jenkins Labels: exception api rest Priority: Minor Reporter: Torsten Ehrhorn 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-11543) UTF-8 encoding issue of build parameters as soon as including File parameter
SCM/JIRA link daemon commented on JENKINS-11543 UTF-8 encoding issue of build parameters as soon as including File parameter Code changed in jenkins User: Oliver Gondža Path: test/src/test/java/hudson/model/ParametersTest.java http://jenkins-ci.org/commit/jenkins/75f5d2180f7340ce2efd4f41c8670afb049eb530 Log: JENKINS-11543 Unit test 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-25133) downgrade fails with Not Found for manually installed plugin
Nicolas De Loof created JENKINS-25133 downgrade fails with Not Found for manually installed plugin Issue Type: Bug Assignee: Unassigned Components: core Created: 13/Oct/14 8:26 PM Description: plugin manager offers to downgrade manually installed plugins, but clicking the button result in : ``` HTTP ERROR 404 Problem accessing /updateCenter/plugin/ID/downgrade. Reason: Not Found ``` button should then not be offered to user. 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] [maven-plugin] (JENKINS-18030) Unable to parameterized Maven module build
Daniel Beck updated JENKINS-18030 Unable to parameterized Maven module build Change By: Daniel Beck (13/Oct/14 8:37 PM) Description: ImabletoconfiguresomeparametersforaMavenmodulebuild (withtheJenkinsParameterizedTriggerplugin) butwhentryingtoexecuteamavenmoduledirectly,parametersarenotpassed.HerestheConsoleOutput:ExecutingMaven:-N-B-f/var/lib/jenkins/customWorkspaces/SOAPUI/Google/Divers/pom.xmlcleanintegration-test-P$Environnement$Environnementshouldbereplacedbytheparametervalue. Labels: buildparameterizedplugins Assignee: KohsukeKawaguchi 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] [youtrack] (JENKINS-24333) No action for executing command from build step
Wolfgang Ziegler commented on JENKINS-24333 No action for executing command from build step Sry, it should have been '"XYZ" instead of "XYZ-123"' - the number and the dash is missing from the detected issue ID. Without a changelog variable, I've no idea how I'd get to the right youtrack issue for posting a comment to - so it looks like I'll have to figure this one out. Thanks for the tip with the API - http://stackoverflow.com/questions/11823826/get-access-to-build-changelog-in-jenkins describes this also. Basically it's about having a custom comment message (where I can make use of environment variables) instead of "Update YouTrack issue with link to build". Thus, appending information to the default comment posted to the issue would be already helpful as well. Does it post "build notes" maybe, or is the posted text hard-coded right now? Thanks a lot! 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-15252) Why is Prevent Cross Site Request Forgery exploits disabled by default?
Daniel Beck commented on JENKINS-15252 Why is Prevent Cross Site Request Forgery exploits disabled by default? Would this be sufficient? Some Jenkins features (like the REST API) are more difficult to use when this option is enabled. Some features, especially in plugins not tested with this option enabled, may not work at all. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-15252) Why is Prevent Cross Site Request Forgery exploits disabled by default?
Daniel Beck edited a comment on JENKINS-15252 Why is Prevent Cross Site Request Forgery exploits disabled by default? Would this be sufficient? Some Jenkins features (like the REST API) are more difficult to use when this option is enabled. Some features, especially in plugins not tested with this option enabled, may not work at all. Some reverse proxies may filter the "crumb" parameter, resulting in failures when trying to use certain actions. 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-25132) Remote access API - listing culprits using the 'tree' query parameter throws exception
Daniel Beck commented on JENKINS-25132 Remote access API - listing culprits using the tree query parameter throws exception If this were related to the newest build, wouldn't https://ci.jenkins-ci.org/job/jenkins_rc_branch/468/api/xml?tree=culprits fail? 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] [ghprb] (JENKINS-24820) Environment is not fulfilled
David Tanner
commented on JENKINS-24820
Environment is not fulfilled
Using the cron job will set the ${sha1} variable. At my company Jenkins is only available behind our firewall so we can't use webhooks either. Make sure that there are no other triggers enabled, and it should be fine. Please advise if you are still seeing issues.
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] [ghprb] (JENKINS-24954) Test PASSed comments added even if Published Jenkins URL
David Tanner commented on JENKINS-24954 Test PASSed comments added even if Published Jenkins URL It should be fixed in the latest, 16-3 and I am also releasing 16-4 now, so it should be available tomorrow. 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-25132) Remote access API - listing culprits using the 'tree' query parameter throws exception
Daniel Beck resolved JENKINS-25132 as Duplicate Remote access API - listing culprits using the tree query parameter throws exception Appears to duplicate JENKINS-16737. The problem with reporting bugs in someone else's instance is that you have no way to help the investigation by providing non-public data, and no way to verify a fix. IOW, these issues are usually a dead end. (OTOH if you're specfically reporting issues with the Jenkins Project infrastructure, the INFRA project may be a better place.) Change By: Daniel Beck (13/Oct/14 8:56 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] [git] (JENKINS-16737) java.lang.RuntimeException: No author in changeset null
Daniel Beck commented on JENKINS-16737 java.lang.RuntimeException: No author in changeset null According to JENKINS-25132, ci.jenkins-ci.org has that problem. So it may be possible to determine whether the fix works by upgrading Git plugin there. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25133) downgrade fails with Not Found for manually installed plugin
Daniel Beck commented on JENKINS-25133 downgrade fails with Not Found for manually installed plugin Are you sure this isn't about failed plugins not having the updateCenter/plugin/foo URL? 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-25133) downgrade fails with Not Found for manually installed plugin
Daniel Beck edited a comment on JENKINS-25133 downgrade fails with Not Found for manually installed plugin (removed) 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-25133) downgrade fails with Not Found for manually installed plugin
Daniel Beck edited a comment on JENKINS-25133 downgrade fails with Not Found for manually installed plugin To clarify, by manually installed, you mean the file was placed in the plugins directory while Jenkins was running? 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-10059) NoClassDefFoundError: org/apache/tools/ant/types/selectors/TokenizedPath after upgrading to 1.417
Daniel Beck updated JENKINS-10059 NoClassDefFoundError: org/apache/tools/ant/types/selectors/TokenizedPath after upgrading to 1.417 Change By: Daniel Beck (13/Oct/14 9:11 PM) Labels: z/linux 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-7339) maven.test.failure.ignore ignored when set globally
Daniel Beck reopened JENKINS-7339 maven.test.failure.ignore ignored when set globally Reopening: I tried with export MAVEN_OPTS=DskipTests=true (easier to verify), and it worked. Sorry about that. Change By: Daniel Beck (13/Oct/14 9:19 PM) Resolution: NotADefect Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-11543) UTF-8 encoding issue of build parameters as soon as including File parameter
dogfood commented on JENKINS-11543 UTF-8 encoding issue of build parameters as soon as including File parameter Integrated in jenkins_main_trunk #3746 JENKINS-11543 Unit test (Revision 75f5d2180f7340ce2efd4f41c8670afb049eb530) Result = SUCCESS ogondza : 75f5d2180f7340ce2efd4f41c8670afb049eb530 Files : test/src/test/java/hudson/model/ParametersTest.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-7339) maven.test.failure.ignore ignored when set globally
Daniel Beck commented on JENKINS-7339 maven.test.failure.ignore ignored when set globally Global MAVEN_OPTS is used as fallback when the per-project MAVEN_OPTS are not set. It's also only for the Maven Project type. Is one of these two limitations the cause for it not working? 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-5909) JVM heap options cannot be honoured on Windows slave
Daniel Beck commented on JENKINS-5909 JVM heap options cannot be honoured on Windows slave Is this still an unresolved problem? Are you able to reproduce this in recent Jenkins versions? What's the user Jenkins is running as on the Windows machine? 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.
