[JIRA] [core] (JENKINS-25533) "Restrict where this project can be run" removed/disabled after Save/Apply of Job Configuration
podskalsky commented on JENKINS-25533 "Restrict where this project can be run" removed/disabled after Save/Apply of Job Configuration The trailing newlines are not the problem (I've checked it) but the changed xml tag canRoam and the removed tag assignedNode !!! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-plugin] (JENKINS-24421) Github webhook throwing "Form too large"
Kohsuke Kawaguchi commented on JENKINS-24421 Github webhook throwing "Form too large" Eclipse project describes the rationale as the following: Jetty limits the amount of data that can post back from a browser or other client to the server. This helps protect the server against denial of service attacks by malicious clients sending huge amounts of data. The default maximum size Jetty permits is 20 bytes. You can change this default for a particular webapp, for all webapps on a particular Server instance, or all webapps within the same JVM. Maybe we should set a bit bigger value in Winstone. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-plugin] (JENKINS-24848) The github plugin should build the commit specified in the service payload
Kohsuke Kawaguchi resolved JENKINS-24848 as Won't Fix The github plugin should build the commit specified in the service payload Because there's no way to authenticate a payload POSTEed, we cannot trust anything in there. So I don't think it's possible for us to build what is pushed, unless somehow we recover that information from the GitHub event API or some such. Building every commit separately would indeed be a sensible feature, and that should be filed against the Git plugin. I'm closing this issue as WONTFIX as the issue described in the title cannot be done by design. Change By: Kohsuke Kawaguchi (18/Nov/14 2:55 AM) Status: Open Resolved Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-25632) workflow cps-global-lib workflowLibs.git issues
Kohsuke Kawaguchi resolved JENKINS-25632 as Fixed workflow cps-global-lib workflowLibs.git issues As instructed by Valentina. Change By: Kohsuke Kawaguchi (18/Nov/14 1:31 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] [junit-plugin] (JENKINS-25573) Junit plugin always produces 100% health report
Jesse Glick commented on JENKINS-25573 Junit plugin always produces 100% health report File a PR for it. Especially if you can write a 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] [ssh-slaves-plugin] (JENKINS-25656) SSH slaves plugin hangs the shutdown of Jenkins
Kohsuke Kawaguchi created JENKINS-25656 SSH slaves plugin hangs the shutdown of Jenkins Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: ssh-slaves-plugin Created: 18/Nov/14 1:14 AM Description: I've encountered a situation in which the Jenkins shutdown hangs at the following stacks that span across three threads: "Shutdown" prio=10 tid=0x7f52b803b000 nid=0x6a2a waiting for monitor entry [0x7f532157b000] java.lang.Thread.State: BLOCKED (on object monitor) at com.trilead.ssh2.Connection.getHostname(Connection.java:961) - waiting to lock <0x00060c4bfba8> (a com.trilead.ssh2.Connection) at hudson.plugins.sshslaves.PluginImpl.closeRegisteredConnections(PluginImpl.java:47) - locked <0x00060c78cac8> (a java.lang.Class for hudson.plugins.sshslaves.PluginImpl) at hudson.plugins.sshslaves.PluginImpl.stop(PluginImpl.java:38) at hudson.PluginWrapper.stop(PluginWrapper.java:382) at hudson.PluginManager.stop(PluginManager.java:650) at jenkins.model.Jenkins.cleanUp(Jenkins.java:2695) at hudson.WebAppMain.contextDestroyed(WebAppMain.java:344) at org.mortbay.jetty.handler.ContextHandler.doStop(ContextHandler.java:545) at org.mortbay.jetty.webapp.WebAppContext.doStop(WebAppContext.java:451) at org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:65) at org.mortbay.jetty.handler.HandlerCollection.doStop(HandlerCollection.java:164) at org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:65) at org.mortbay.jetty.handler.HandlerCollection.doStop(HandlerCollection.java:164) at org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:65) at org.mortbay.jetty.handler.HandlerWrapper.doStop(HandlerWrapper.java:129) at org.mortbay.jetty.Server.doStop(Server.java:242) at org.mortbay.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:65) at org.mortbay.jetty.Server$ShutdownHookThread.run(Server.java:509) "Jenkins-Remoting-Thread-8" daemon prio=10 tid=0x7f52b54ad000 nid=0x698d waiting for monitor entry [0x7f5322756000] java.lang.Thread.State: BLOCKED (on object monitor) at com.trilead.ssh2.channel.ChannelManager.closeChannel(ChannelManager.java:311) - waiting to lock <0x00060c4c29a0> (a java.lang.Object) at com.trilead.ssh2.channel.ChannelManager.closeAllChannels(ChannelManager.java:278) at com.trilead.ssh2.Connection.close(Connection.java:564) at com.trilead.ssh2.Connection.close(Connection.java:558) - locked <0x00060c4bfba8> (a com.trilead.ssh2.Connection) at hudson.plugins.sshslaves.SSHLauncher.afterDisconnect(SSHLauncher.java:611) - locked <0x00060c4bfa48> (a hudson.plugins.sshslaves.SSHLauncher) at hudson.slaves.SlaveComputer$3.run(SlaveComputer.java:552) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) "Monitoring thread for Free Swap Space started on Mon Nov 17 16:53:46 PST 2014" daemon prio=10 tid=0x7f5308005000 nid=0x69e6 runnable [0x7f532167c000] java.lang.Thread.State: RUNNABLE at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109) at java.net.SocketOutputStream.write(SocketOutputStream.java:153) at com.trilead.ssh2.crypto.cipher.CipherOutputStream.flush(CipherOutputStream.java:75) at com.trilead.ssh2.transport.TransportConnection.sendMessage(TransportConnection.java:193) at com.trilead.ssh2.transport.TransportConnection.sendMessage(TransportConnection.java:107) at com.trilead.ssh2.transport.TransportManager.sendMessage(TransportManager.java:666) - locked <0x00060c4bfe68> (a java.lang.Object) at com.trilead.ssh2.channel.ChannelManager.sendData(ChannelManager.java:438) - locked <0x00060c4c29a0> (a java.lang.Object) at com.trilead.ssh2.channe
[JIRA] [active-directory-plugin] (JENKINS-24195) Faster permission lookups when having many unused AD-groups
Kohsuke Kawaguchi
commented on JENKINS-24195
Faster permission lookups when having many unused AD-groups
The downside of this change is that if you update permissions and start referencing a new group, people need to log out and come back into to see the effect.
I think the performance improvement is great, and I get that this is a practical fix to work around the problem at hand for the author, but at the same time, I feel that this is exposing a complexity to users, when a problem should have been solved by us.
Role-based Authorization Strategy plugin has known performance issues, and as for the matrix auth plugin, I think SparseACL.hasPermission() implementation should be improved to reject uninteresting {{Sid}}s more quickly.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector-plugin] (JENKINS-22394) Ensure that collector runs after individual analysis publishers
Ulli Hafner updated JENKINS-22394 Ensure that collector runs after individual analysis publishers Change By: Ulli Hafner (17/Nov/14 10:52 PM) Summary: Ensure that collector runs after individual analysis publishers This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector-plugin] (JENKINS-22394) Ensure that collector runs after analysis publishers
Ulli Hafner updated JENKINS-22394 Ensure that collector runs after analysis publishers Change By: Ulli Hafner (17/Nov/14 10:51 PM) Summary: Only one of multiple warnings parser is reported in Combined Analysis results Ensure that collector runs after analysis publishers Description: The Job has 4 warnings parsers, 1 built in and 3 on the fly parsersThe Job also looks for open tasks.There are graphs for only 3 or the 4 warnings on the job splash, but they are Analysis collector build step should check that all present in the side bar linksAll the checkboxes (warnings, checkstyle, findbugs, pmd, tasks) selected analysis plugins are enabled on running *before* the SA combinerThe SA combiner graph on the job splash has only one of the warnings (the oldest) and open tasks data in it collection step . The SA combiner on the dashboard with this job (display by type) indicates only 2 types, compiler (warnings?), and open tasks If not a warning or error should be shown . Where compiler looks like it also matches that oldest (on the fly) parser only. Priority: Major Minor Component/s: analysis-core-plugin Component/s: warnings-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] [artifactdeployer-plugin] (JENKINS-25461) ArtifactDeployer breaks under recent build(s) of Jenkins
Matt Philmon commented on JENKINS-25461 ArtifactDeployer breaks under recent build(s) of Jenkins That is correct. I am stuck on Jenkins 1.585 until this bug is fixed. We heavily use this 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] [core] (JENKINS-25655) AbstractLazyLoadRunMap.entrySet improperly cached
Jesse Glick updated JENKINS-25655 AbstractLazyLoadRunMap.entrySet improperly cached Change By: Jesse Glick (17/Nov/14 10:49 PM) Labels: lazy-loading lts-candidate regression This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector-plugin] (JENKINS-22394) Only one of multiple warnings parser is reported in Combined Analysis results
Ulli Hafner commented on JENKINS-22394 Only one of multiple warnings parser is reported in Combined Analysis results Wow, that feature is quite old I never actually realized that... @Greg: I'll add a warning if the collector is not last. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.
Tim-Christian Bloss commented on JENKINS-22542 Subversion polling not work with externals or variables in URL - E200015: No credential to try. Interesting aspect. Java 7 seems to have some issues since those SSL-Updates of last days/weeks. In some cases regarding SNI and SSL, especially when combined, Java 8 may be an option to try for master and slaves. Another problem may be Windows updates, as some parts like smb/ad protocols get updated now and then and therefore some apache httpd modules might need an update for proper authentication/authorization against security realm/domain. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25655) AbstractLazyLoadRunMap.entrySet improperly cached
Jesse Glick assigned JENKINS-25655 to Jesse Glick AbstractLazyLoadRunMap.entrySet improperly cached Change By: Jesse Glick (17/Nov/14 10:39 PM) Assignee: 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-25655) AbstractLazyLoadRunMap.entrySet improperly cached
Jesse Glick created JENKINS-25655 AbstractLazyLoadRunMap.entrySet improperly cached Issue Type: Bug Assignee: Unassigned Components: core Created: 17/Nov/14 10:39 PM Description: JENKINS-18065 introduced a layer of caching which caused stale data to be reported under some conditions. Project: Jenkins Labels: lazy-loading regression Priority: Major 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-25655) AbstractLazyLoadRunMap.entrySet improperly cached
Jesse Glick started work on JENKINS-25655 AbstractLazyLoadRunMap.entrySet improperly cached Change By: Jesse Glick (17/Nov/14 10:39 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25381) Build history widget verbosity
Tom FENNELLY commented on JENKINS-25381 Build history widget verbosity Experimented with adding a date separator. See attachement http://goo.gl/iGLRDD . Wdyt ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25381) Build history widget verbosity
Tom FENNELLY updated JENKINS-25381 Build history widget verbosity Change By: Tom FENNELLY (17/Nov/14 10:33 PM) Attachment: Screenshot 2014-11-18 22.25.48.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector-plugin] (JENKINS-22394) Only one of multiple warnings parser is reported in Combined Analysis results
Daniel Beck commented on JENKINS-22394 Only one of multiple warnings parser is reported in Combined Analysis results It appears this has been introduced with the addition of the dropdown, i.e. 1.463, May 2012. See https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-dev/UQLvxQclyb4 (I think the UI ignores behavior from Recorder/Notifier/needsToRunAfterFinalized though, so it's actually a bit confusing.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector-plugin] (JENKINS-22394) Only one of multiple warnings parser is reported in Combined Analysis results
Ulli Hafner commented on JENKINS-22394 Only one of multiple warnings parser is reported in Combined Analysis results Interesting, since when is it possible to reorder post build steps? I defined the order of the actions in source code so that the collector plugin is always last. Seems that this could be changed now... The order of the graphs cannot be changed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector-plugin] (JENKINS-22394) Only one of multiple warnings parser is reported in Combined Analysis results
Greg Moncreaff commented on JENKINS-22394 Only one of multiple warnings parser is reported in Combined Analysis results console log messages (interesting that analysis collector is before DRY, etc. I had it 1st in list since I wanted its graph to be top of Job splash page. 00:02:18.992 [ANALYSIS-COLLECTOR] Computing warning deltas based on reference build #737 00:02:18.992 [DRY] Collecting duplicate code analysis files... 00:02:18.995 [DRY] Finding all files that match the pattern bin/cpd.xml 00:02:18.995 [DRY] Parsing 1 files in /var/lib/jenkins/workspace/zzz 00:02:18.995 [DRY] Successfully parsed file /var/lib/jenkins/workspace/zzz/bin/cpd.xml of module with 15 warnings. 00:02:19.005 [DRY] Computing warning deltas based on reference build #737 00:02:19.007 [WARNINGS] Parsing warnings in console log with parser GNU C Compiler 4 (gcc) 00:02:19.021 [WARNINGS] Computing warning deltas based on reference build #737 00:02:19.021 [WARNINGS] Plug-in Result: Success - no threshold has been exceeded 00:02:19.235 [TASKS] Scanning folder '/var/lib/jenkins/workspace/zzz' for files matching the pattern '*/.cpp, */.h' - excludes: 00:02:19.235 [TASKS] Found 486 files to scan for tasks 00:02:19.235 [TASKS] Found 138 open tasks. 00:02:19.265 [TASKS] Computing warning deltas based on reference build #737 not latest, our tool governance model typically imposes a one-two quarter lag, but reasonably current (this year anyway) Jenkins ver. 1.581 Static Analysis Collector Plug-in 1.41 I changed the publisher order to be 1. DRY 2. WARNINGS 3. TASKS 4. ANALYSIS-COLLECTOR and AH-HA! now I'm seeing something more reasonable in the graph. It looks like 1. there is an (unobvious) dependency between the plugins, and 2. order of graphs on the splash page can't be adjusted independently? As a minimum I'd recommend putting text on the base (not advanced) SA-Collector plugin configurator to say it needs to be below any of the plugins you want it to be summarizing. And the wiki should explain it more? I don't know if core has any kind of dependency model for plugins to allow automatic reordering of execution? and allowing user to order the display (graphs) in some desired summary/details or priority high/low order in the job config, suspecting not?.. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook-plugin] (JENKINS-24232) Hook fails on parametrized jobs
Vanja Radovanović commented on JENKINS-24232 Hook fails on parametrized jobs No definite timeline just yet. Have to close a few remaining issues. Hopefully in a month. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [libvirt-slave-plugin] (JENKINS-12523) Could not initialize class org.libvirt.Connect
Jacob Keller commented on JENKINS-12523 Could not initialize class org.libvirt.Connect I was able to just convert the slaves to SSH which works ok, but I lose the added functionality of the libvirt on/off changes. What generally needs to be done to fix this? I don't mind having a go at the libvirt plugin, but I don't have a whole lot of experience at what exactly is wrong. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25488) New UI wastes horizontal space
Daniel Beck commented on JENKINS-25488 New UI wastes horizontal space Looks like 11xx pixels wide, but with zoom applied, resulting in an equivalent/effective horizontal width of 870-930 pixels (going by where line breaks in the list view footer are applied). Do we really need to optimize what's primarily a developers' tool for resolutions no modern IDE can be used with? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook-plugin] (JENKINS-24232) Hook fails on parametrized jobs
Stephen Finney edited a comment on JENKINS-24232 Hook fails on parametrized jobs I've got this issue too. Any word on a new version of Jenkins with this fix included? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-hook-plugin] (JENKINS-24232) Hook fails on parametrized jobs
Stephen Finney commented on JENKINS-24232 Hook fails on parametrized jobs I've got this issue too. Any word on a new version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector-plugin] (JENKINS-22394) Only one of multiple warnings parser is reported in Combined Analysis results
Ulli Hafner commented on JENKINS-22394 Only one of multiple warnings parser is reported in Combined Analysis results And are you using the latest versions of the plugins/jenkins? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector-plugin] (JENKINS-22394) Only one of multiple warnings parser is reported in Combined Analysis results
Ulli Hafner commented on JENKINS-22394 Only one of multiple warnings parser is reported in Combined Analysis results Can you please show the log messages of the analysis plugins from your console log of the latest build? There should be messages starting with [WARNINGS] [DRY], etc. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector-plugin] (JENKINS-22394) Only one of multiple warnings parser is reported in Combined Analysis results
Ulli Hafner reopened JENKINS-22394 Only one of multiple warnings parser is reported in Combined Analysis results Change By: Ulli Hafner (17/Nov/14 8:48 PM) Resolution: Incomplete 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] [email-ext-plugin] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Alex Earl commented on JENKINS-21861 option to include attachment with console.txt from failed slaves A screen sharing session would be useful, I'm just not sure when during the day I could do it. What timezone are you in? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactdeployer-plugin] (JENKINS-25461) ArtifactDeployer breaks under recent build(s) of Jenkins
Daniel Beck commented on JENKINS-25461 ArtifactDeployer breaks under recent build(s) of Jenkins To clarify, you cannot upgrade beyond 1.585 without a fix? Or what else is the problem here? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector-plugin] (JENKINS-22394) Only one of multiple warnings parser is reported in Combined Analysis results
Greg Moncreaff edited a comment on JENKINS-22394 Only one of multiple warnings parser is reported in Combined Analysis results I picture of what I said earlier. It's wrong in 'build details' also... Static Analysis Warnings: 0 warnings. No warnings since build 719. New zero warnings highscore: no warnings for 2 days! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodelabelparameter-plugin] (JENKINS-24280) Environment variables get corrupted when using Node parameter
Richard Hendricks commented on JENKINS-24280 Environment variables get corrupted when using Node parameter I see the same problem with our Jenkins setup. We are not using env-inject. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector-plugin] (JENKINS-22394) Only one of multiple warnings parser is reported in Combined Analysis results
Greg Moncreaff edited a comment on JENKINS-22394 Only one of multiple warnings parser is reported in Combined Analysis results I picture of what I said earlier. I don't know what you mean by 'build details view'? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector-plugin] (JENKINS-22394) Only one of multiple warnings parser is reported in Combined Analysis results
Greg Moncreaff updated JENKINS-22394 Only one of multiple warnings parser is reported in Combined Analysis results I picture of what I said earlier Change By: Greg Moncreaff (17/Nov/14 8:08 PM) Attachment: JENKINS-22394.JPG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector-plugin] (JENKINS-22394) Only one of multiple warnings parser is reported in Combined Analysis results
Ulli Hafner commented on JENKINS-22394 Only one of multiple warnings parser is reported in Combined Analysis results I.e., only the job graph shows a wrong result, the SA result is correct in the build details view? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory-plugin] (JENKINS-25654) Restore Project option for Job Config History gets Oops! page
george trubisky created JENKINS-25654 Restore Project option for Job Config History gets Oops! page Issue Type: Bug Assignee: Mirko Friedenhagen Attachments: JobConfigHistory_2014-11-17_11-39-41.jpg, JobConfigHistory_stacktrace.txt Components: jobconfighistory-plugin Created: 17/Nov/14 7:57 PM Description: When attempting to restore projects, get the "devil jenkins" oops page. Projects in question were disabled prior to delete and Job Config History plugin was not installed prior to the project being disabled. Environment: Jenkins ver. 1.565.1, jobconfighistory plugin 2.9 Project: Jenkins Labels: user-experience Priority: Major Reporter: george trubisky This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-25653) TimeoutStepTest.killingParallel() in aggregator failing on MacOS
Tom FENNELLY created JENKINS-25653 TimeoutStepTest.killingParallel() in aggregator failing on MacOS Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 17/Nov/14 7:47 PM Description: This test (introduced in f7c0db4) fails every time on Darwin/MacOS (at least for me). It runs fine if you run the test on its own (i.e. do not run TimeoutStepTest.basic()). It times out waiting for the build to fail (line 51). It seemed like it might be something to do with not being able to kill all related child processes running in the parallel step, but I'm not sure about that now after adding some logging to the ProcessTree class. Initially it seemed as though it was trying to kill the same process multiple times (I thought maybe that might cause things to hang) but that's not the case either since I've seen it hang even when all the PIDs are unique, so not sure now. Environment: MacOS Project: Jenkins Priority: Major Reporter: Tom FENNELLY This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-25653) TimeoutStepTest.killingParallel() in aggregator failing on MacOS
Tom FENNELLY updated JENKINS-25653 TimeoutStepTest.killingParallel() in aggregator failing on MacOS Change By: Tom FENNELLY (17/Nov/14 7:48 PM) Assignee: Jesse Glick Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25652) Relaunch slave agent fails after node changes IP address
Matthew Bells created JENKINS-25652 Relaunch slave agent fails after node changes IP address Issue Type: Bug Assignee: Unassigned Components: core Created: 17/Nov/14 7:33 PM Description: Steps to reproduce Setup Jenkins (computer "jenkins") with a node "foo" on separate computers. Browse to the page: http://jenkins:8080/computer/foo/ Ensure the node is running and Idle. Turn off the node foo computer (without first bringing the Jenkins node offline). Restart the node and have it reconnect to the network with DHCP. Make sure its IP address changed. Refresh the page, note the node is offline. The state may be "This node is being launched.", but the log is empty. Press the "Relaunch slave agent" button. This takes you to the log, which remains empty. Other info The stack trace from Jenkins shows: "Channel reader thread: foo" Id=360 Group=main WAITING on com.trilead.ssh2.channel.Channel@66a77259 at java.lang.Object.wait(Native Method) - waiting on com.trilead.ssh2.channel.Channel@66a77259 at java.lang.Object.wait(Object.java:503) at com.trilead.ssh2.channel.FifoBuffer.read(FifoBuffer.java:212) at com.trilead.ssh2.channel.Channel$Output.read(Channel.java:127) at com.trilead.ssh2.channel.ChannelManager.getChannelData(ChannelManager.java:946) at com.trilead.ssh2.channel.ChannelInputStream.read(ChannelInputStream.java:58) at com.trilead.ssh2.SFTPv3Client.readBytes(SFTPv3Client.java:215) at com.trilead.ssh2.SFTPv3Client.receiveMessage(SFTPv3Client.java:240) at com.trilead.ssh2.SFTPv3Client.init(SFTPv3Client.java:864) at com.trilead.ssh2.SFTPv3Client.(SFTPv3Client.java:108) at com.trilead.ssh2.SFTPv3Client.(SFTPv3Client.java:119) at hudson.plugins.sshslaves.SSHLauncher.afterDisconnect(SSHLauncher.java:1160) - locked hudson.plugins.sshslaves.SSHLauncher@1cb4fc57 at hudson.slaves.SlaveComputer$2.onClosed(SlaveComputer.java:443) at hudson.remoting.Channel.terminate(Channel.java:799) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Workaround Configure the node, add a dummy value (e.g. "relaunch-1" to the description). Save the new configuration. It will now launch. There may be a way to script this too... Environment: Jenkins ver. 1.554.3 Ubuntu 14.04 Project: Jenkins Labels: slave Priority: Minor Reporter: Matthew Bells This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-plugin] (JENKINS-25535) Exception if email trigger enabled but no recipient specified
Alex Earl commented on JENKINS-25535 Exception if email trigger enabled but no recipient specified FYI, please see JENKINS-24506 for further discussion on this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25642) Bad link to /configureSecurity/asynchPeople
Daniel Beck updated JENKINS-25642 Bad link to /configureSecurity/asynchPeople Change By: Daniel Beck (17/Nov/14 7:27 PM) Priority: Minor Trivial Assignee: Daniel Beck Component/s: core Component/s: security This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25533) "Restrict where this project can be run" removed/disabled after Save/Apply of Job Configuration
Daniel Beck commented on JENKINS-25533 "Restrict where this project can be run" removed/disabled after Save/Apply of Job Configuration podskalsky: Jenkins does not add trailing newlines to XML files, I assume those are yours? (JENKINS-25628) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25606) PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source
Shane Gannon commented on JENKINS-25606 PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source -DskipTests=true did the trick. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-plugin] (JENKINS-24506) NPE when sending an email in post build
Alex Earl resolved JENKINS-24506 as Fixed NPE when sending an email in post build This is fixed in 2.39. I was previously only creating the recipient provider list if one of the options was selected (send to recipients, etc). In 2.39 this was changed so that if the list is null, it always gets created. Change By: Alex Earl (17/Nov/14 6:03 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] [core] (JENKINS-25381) Build history widget verbosity
Tom FENNELLY commented on JENKINS-25381 Build history widget verbosity Doing a no-wrap and overflow can also make it look terrible. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25651) Admins should be able to force queued items to be executed
Bruno Meneguello created JENKINS-25651 Admins should be able to force queued items to be executed Issue Type: Improvement Assignee: Unassigned Components: core Created: 17/Nov/14 6:03 PM Description: When jobs are queued, or when the system is in shutdown mode, as admin, I want to be able to force (heavily suggest) one queued item to be executed. It happens because when I put the server to shutdown (I prefer maintenance mode), sometimes I need to run admin tasks without leaving the maintenance mode. I think the logic that tests for shutdown is spread in inadequate places, like LoadBalancer.sanitize anonymous class, and since the Task interface is much core, alter it is not a good idea. Project: Jenkins Priority: Minor Reporter: Bruno Meneguello This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25488) New UI wastes horizontal space
Tom FENNELLY commented on JENKINS-25488 New UI wastes horizontal space What resolution are you working with here? It looks very small. The width of the left panel changes depending on the overall width of the browser window. It adjusts the number of "columns" given to the left panel based on the overall width of the window. This is not easy to get working in a way that is "perfect" for every situation. When doing it I experimented with different screen widths and settled on what I thought was the best balance, but of course there will be situations where it is not perfect. I suppose I leaned in favour of screens with higher resolutions, so you may be suffering from that if your screen is lower res. Changing the responsive grid css (which we got from twitter bootstrap) is not really a fix. It may fix it for the the exact scenario you are talking about here, but will most probably cause something else to look messed up. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-plugin] (JENKINS-25535) Exception if email trigger enabled but no recipient specified
Alex Earl commented on JENKINS-25535 Exception if email trigger enabled but no recipient specified I agree, just wondering if there was a use case I wasn't thinking of. I can create a version of 2.38.x that has what I think is the fix for this, or you can try upgrading to 2.39, it has the change I would make already. Let me know which you would like to do. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-plugin] (JENKINS-24506) NPE when sending an email in post build
Alex Earl commented on JENKINS-24506 NPE when sending an email in post build I believe I have a pretty simple fix for this. Is anyone willing to try a "debug" build based on 2.39? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-25535) Exception if email trigger enabled but no recipient specified
davida2009 commented on JENKINS-25535 Exception if email trigger enabled but no recipient specified why have a trigger with no recipients defined? That's clearly an error on my part. But I just thought it shouldn't result in an exception. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-25535) Exception if email trigger enabled but no recipient specified
Alex Earl edited a comment on JENKINS-25535 Exception if email trigger enabled but no recipient specified This will be super helpful, thanks. If you need a fast workaround, opening the job and resaving should fix the issue for you. Let me know if it does not. One question though, why have a trigger with no recipients defined? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-plugin] (JENKINS-25535) Exception if email trigger enabled but no recipient specified
Alex Earl commented on JENKINS-25535 Exception if email trigger enabled but no recipient specified This will be super helpful, thanks. If you need a fast workaround, opening the job and resaving should fix the issue for you. Let me know if it does not. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24006) Customize number of Junit test failures that affect weather
Mark Sinclair commented on JENKINS-24006 Customize number of Junit test failures that affect weather The always 100% health report issue is tracked by the following: https://issues.jenkins-ci.org/browse/JENKINS-25573 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-plugin] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Mike Dubman commented on JENKINS-21861 option to include attachment with console.txt from failed slaves Hi ALex, yes - this is still an issue for "Matrix projects". works as advertised on "freestyle" projects. I tried to change "send log for all slaves" and for "master only" - it did not help. Currently, as a work-around we have some ugly script to fetch consoles and attach to the outgoing email. We could have screen sharing session if needed to demo the problem - but it is the same as in screenshot. Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25573) Junit plugin always produces 100% health report
Mark Sinclair commented on JENKINS-25573 Junit plugin always produces 100% health report I think this is the issue: The health score is calculated in this file: junit-plugin / src / main / java / hudson / tasks / test / AbstractTestResultAction.java On Line 160-162, the health score is calculated. The lines are shown below: int score = (totalCount == 0) ? 100 : (int) (100.0 * Math.max(1.0, Math.min(0.0, 1.0 - (scaleFactor * failCount) / totalCount))); The problem is the Math.max has a first argument of 1.0, which makes the second argument irrelevant as it is always less than 1. The first argument should be 0.0, as the intention is to never report negative health. Corrected code is below (just changed to 1.0 to 0.0 in the first arg of Math.max: int score = (totalCount == 0) ? 100 : (int) (100.0 * Math.max(0.0, Math.min(0.0, 1.0 - (scaleFactor * failCount) / totalCount))); I'm pretty sure the above would fix the problem. This nested max, min functions seem redundant so the code could be further simplified - I think the following is more concise: int score = (totalCount == 0) ? 100 : (int) (100.0 * Math.max(0.0, 1.0 - (scaleFactor * failCount) / totalCount)); This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-plugin] (JENKINS-25535) Exception if email trigger enabled but no recipient specified
davida2009 updated JENKINS-25535 Exception if email trigger enabled but no recipient specified config.xml as requested, saved via Job Config History screen. Change By: davida2009 (17/Nov/14 4:56 PM) Attachment: config.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] [email-ext-plugin] (JENKINS-22713) '+' char in content encoded as +
Alex Earl commented on JENKINS-22713 '+' char in content encoded as + Using a test, the generated HTML with inlined images looks fine and renders if I open it. I'll sending an email to see if that changes it somehow. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector-plugin] (JENKINS-22394) Only one of multiple warnings parser is reported in Combined Analysis results
Greg Moncreaff edited a comment on JENKINS-22394 Only one of multiple warnings parser is reported in Combined Analysis results I'm looking at a job splash page right now. SA = 0 Dup code = 15 Comp warn = 0 Open Task = ~137 SA was supposed to collect (warnings, duplicates, tasks) but it looks like (trend graph) its currently only collecting comp warnings (of which there are zero at present), when there were non-zero comp warnings, it looks like it collected the other two (duplicates, open tasks) but not compiler warnings e.g. builds 712-119 had dup code = 15 all builds open task = 137 all builds comp warnings = ~5 for all builds sa = ~155 all builds comp warnings were fixed in build 720 but the open tasks, duplicates remained stead state sa = 0 warnings dup = 15 tasks = 140 since the # of comp warnings was low (3-5) it may be including then correctly (when there are non-zero of them) its just hard to see (since there are 155 other counts) I changed the graph to 'distr by type' and it looks like comp warnings are on the x-axis This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector-plugin] (JENKINS-22394) Only one of multiple warnings parser is reported in Combined Analysis results
Greg Moncreaff edited a comment on JENKINS-22394 Only one of multiple warnings parser is reported in Combined Analysis results I'm looking at a job splash page right now. SA = 0 Dup code = 15 Comp warn = 0 Open Task = ~137 SA was supposed to collect (warnings, duplicates, tasks) but it looks like (trend graph) its currently only collecting comp warnings (of which there are zero at present), when there were non-zero comp warnings, it looks like it collected the other two (duplicates, open tasks) but not compiler warnings e.g. builds 712-119 had dup code = 15 all builds open task = 137 all builds comp warnings = ~5 for all builds sa = ~155 all builds comp warnings were fixed in build 720 but the open tasks, duplicates remained stead state sa = 0 warnings dup = 15 tasks = 140 since the # of comp warnings was low (3-5) it may be including then correctly (when there are non-zero of them) its just hard to see (since there are 155 other counts) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector-plugin] (JENKINS-22394) Only one of multiple warnings parser is reported in Combined Analysis results
Greg Moncreaff commented on JENKINS-22394 Only one of multiple warnings parser is reported in Combined Analysis results I'm looking at a job splash page right now. SA = 0 Dup code = 15 Comp warn = 0 Open Task = ~137 SA was supposed to collect (warnings, duplicates, tasks) but it looks like (trend graph) its currently only collecting comp warnings (of which there are zero at present), when there were non-zero comp warnings, it looks like it collected the other two (duplicates, open tasks) but not compiler warnings e.g. builds 712-119 had dup code = 15 all builds open task = 137 all builds comp warnings = ~5 for all builds sa = ~155 all builds comp warnings were fixed in build 720 but the open tasks, duplicates remained stead state sa = 0 warnings dup = 15 tasks = 140 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-plugin] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Alex Earl commented on JENKINS-21861 option to include attachment with console.txt from failed slaves Hi Tom, Did you try changing the "Trigger for matrix projects" setting in the job configuration along with the attach build log? Thanks, Alex This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-plugin] (JENKINS-25535) Exception if email trigger enabled but no recipient specified
Alex Earl commented on JENKINS-25535 Exception if email trigger enabled but no recipient specified Can you also attach your job's config.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] [email-ext-plugin] (JENKINS-25535) Exception if email trigger enabled but no recipient specified
Alex Earl commented on JENKINS-25535 Exception if email trigger enabled but no recipient specified Strange, I setup something the same way as you have and I don't get an exception. I'll continue trying to replicate. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25606) PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source
Daniel Beck commented on JENKINS-25606 PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source Jenkins is notoriously bad to build on Windows. When I'm forced to do that I just -DskipTests=true and outsource testing to Linux boxes. That said, there appears to be something wrong, so filing an issue is the right action to take. (I'd just not hold my breath on getting a fix.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-25646) Global configuration enforces job configuration without tri-state
Kanstantsin Shautsou commented on JENKINS-25646 Global configuration enforces job configuration without tri-state For example "Close failed pull request automatically?" has no help description and you can't unset it without admin permissions. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [m2release-plugin] (JENKINS-25487) Exception not verbose with m2release plugin
soufien BOUZAOUIA commented on JENKINS-25487 Exception not verbose with m2release plugin I don't have the same problem when I do the release in command line on the other side i have this not verbose exception when i try to execute the release with m2release plugin (Jenkins). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-testresult-plugin] (JENKINS-23991) Step error_message is not quoted in the scenario view, but IS quoted in the message error view
teilo updated JENKINS-23991 Step error_message is not quoted in the scenario view, but IS quoted in the message error view fix component. Change By: teilo (17/Nov/14 3:34 PM) Component/s: cucumber-testresult-plugin Component/s: cucumber-reports-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] [cucumber-testresult-plugin] (JENKINS-21703) Cucumber Test results plugin
teilo resolved JENKINS-21703 as Duplicate Cucumber Test results plugin JENKINS-21835 Change By: teilo (17/Nov/14 3:33 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] [cucumber-testresult-plugin] (JENKINS-21703) Cucumber Test results plugin
teilo updated JENKINS-21703 Cucumber Test results plugin Change By: teilo (17/Nov/14 3:33 PM) Component/s: cucumber-testresult-plugin Component/s: cucumber-reports-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] [cucumber-testresult-plugin] (JENKINS-21835) Cucumber Test Result Plugin crashes on malformed output in Scenario Outline results produced by some tools
teilo updated JENKINS-21835 Cucumber Test Result Plugin crashes on malformed output in Scenario Outline results produced by some tools Change By: teilo (17/Nov/14 3:32 PM) Summary: Cucumber Test Result Plugin does not correctly parse crashes on malformed output in Scenario Outline results produced by some tools This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [m2release-plugin] (JENKINS-10104) Make releases visible to the release plugin
teilo commented on JENKINS-10104 Make releases visible to the release plugin portlet support for releases has been available for a fair while - along with a permalink to the latest release. houskeeping and closign this - and keeping open Jenkins-7487 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-with-parameters-plugin] (JENKINS-25650) java.lang.NoClassDefFoundError when attempting to build parameterized job
Jean Gressmann updated JENKINS-25650 java.lang.NoClassDefFoundError when attempting to build parameterized job It appears this was due to an unused matrix configuration parameter. Once I removed the param this exception disappeared. Change By: Jean Gressmann (17/Nov/14 3:22 PM) Priority: Major Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [m2release-plugin] (JENKINS-19547) Release build fails on jenkins-slave for MultiModuleMavenProjects
teilo assigned JENKINS-19547 to Unassigned Release build fails on jenkins-slave for MultiModuleMavenProjects Change By: teilo (17/Nov/14 3:21 PM) Assignee: teilo This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-11962) Symlinking lastSuccessful build shouldn't fail with concurrent jobs
Rebecca Drabenstott commented on JENKINS-11962 Symlinking lastSuccessful build shouldn't fail with concurrent jobs Thanks for the suggestions Daniel. We plan to move to Java 7 in the near future. Possibly that will fix the issue. Good point about the parallel runs being unnecessary. However, the other job we have that runs for much longer (and stalls for much longer) does require parallel runs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [m2release-plugin] (JENKINS-16091) Aborted builds are repeated within subsequent builds
teilo commented on JENKINS-16091 Aborted builds are repeated within subsequent builds can someone explain how the Server can abort a build. and can someone please attach logs and versions. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-with-parameters-plugin] (JENKINS-25650) java.lang.NoClassDefFoundError when attempting to build parameterized job
Jean Gressmann created JENKINS-25650 java.lang.NoClassDefFoundError when attempting to build parameterized job Issue Type: Bug Assignee: Unassigned Components: build-with-parameters-plugin Created: 17/Nov/14 3:18 PM Description: When starting a build on a parameterized job this exception happens: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-1.590.jar!/hudson/model/ParametersDefinitionProperty/index.jelly:50:78: java.lang.NoClassDefFoundError: hudson/tasks/test/AggregatedTestResultAction at org.kohsuke.stapler.jelly.JellyRequestDispatcher.forward(JellyRequestDispatcher.java:60) at jenkins.model.ParameterizedJobMixIn.doBuild(ParameterizedJobMixIn.java:162) at hudson.model.AbstractProject.doBuild(AbstractProject.java:1733) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse
[JIRA] [m2release-plugin] (JENKINS-16091) Aborted builds are repeated within subsequent builds
teilo commented on JENKINS-16091 Aborted builds are repeated within subsequent builds @danielbeck - what wierd things? the arguments interceptor changes the goals - but only if the build was triggered via the UI and has a M2ReleaseAction attached. If we are getting one of those attached for non release builds then Jenkins itself is erronously attaching old 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] [m2release-plugin] (JENKINS-20131) M2 Release Plugin Build Failure message
teilo resolved JENKINS-20131 as Incomplete M2 Release Plugin Build Failure message no response to request for more info. Change By: teilo (17/Nov/14 3:16 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [m2release-plugin] (JENKINS-15983) Possibility to define a custom SCM tag in project config
teilo stopped work on JENKINS-15983 Possibility to define a custom SCM tag in project config Change By: teilo (17/Nov/14 3:12 PM) Status: In Progress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [m2release-plugin] (JENKINS-11509) maven release plugin does not allow to set the pom file used
teilo resolved JENKINS-11509 as Incomplete maven release plugin does not allow to set the pom file used Change By: teilo (17/Nov/14 3:11 PM) Status: Reopened Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [m2release-plugin] (JENKINS-25487) Exception not verbose with m2release plugin
teilo commented on JENKINS-25487 Exception not verbose with m2release plugin I'm not entirely sure what you are expecting in this exception - it is coming from maven and is not under Jenkins control. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-25649) Duplicate Test Reports in Projects
Jason Davis created JENKINS-25649 Duplicate Test Reports in Projects Issue Type: Bug Assignee: Unassigned Components: junit-plugin Created: 17/Nov/14 2:51 PM Description: Duplicate Test Results chart after upgrading to version 1.2. Reverting back to 1.1 resolved the issue. I'm seeing this in Test results generated in projects using the xUnit plugin and the HP Application Automation Tools plugin. Environment: Windows 2008 R2 - Jenkins 1.585 Project: Jenkins Priority: Minor Reporter: Jason Davis This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactdeployer-plugin] (JENKINS-25461) ArtifactDeployer breaks under recent build(s) of Jenkins
Matt Philmon commented on JENKINS-25461 ArtifactDeployer breaks under recent build(s) of Jenkins Is there a workaround I can try? I can't move Jenkins forward without 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] [core] (JENKINS-25641) Need to share variables between jobs without using globale variables
Anis benAli assigned JENKINS-25641 to Unassigned Need to share variables between jobs without using globale variables Change By: Anis benAli (17/Nov/14 2:43 PM) Assignee: Anis benAli This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xunit-plugin] (JENKINS-25527) xUnit reports yield duplicated "Test Result Trend" charts
Jason Davis edited a comment on JENKINS-25527 xUnit reports yield duplicated "Test Result Trend" charts Experiencing the same problem after upgrading to v1.92 (I only performed plugin upgrades) - however, I noticed the issue with existing reports. The duplicate chart appeared right after restarting Jenkins and before any builds occurred. I'm generating mstest results in a freestyle project on a windows host and slave. jenkins version is 1.585. Downgrading to v1.91 didn't help resolve the duplicate test result charts issue. - False alarm - just noticed the problem in another project not using xUnit and reverting the Junit plugin (which I had also upgraded) to the previous version resolved the problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-plugin] (JENKINS-25535) Exception if email trigger enabled but no recipient specified
davida2009 commented on JENKINS-25535 Exception if email trigger enabled but no recipient specified Sorry for my slow reply. I've attached a screenshot to show conditions that trigger the exception. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-25535) Exception if email trigger enabled but no recipient specified
davida2009 edited a comment on JENKINS-25535 Exception if email trigger enabled but no recipient specified Sorry for my slow reply. I've attached a screenshot to show conditions that trigger the exception. The job succeeded. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-plugin] (JENKINS-25535) Exception if email trigger enabled but no recipient specified
davida2009 updated JENKINS-25535 Exception if email trigger enabled but no recipient specified Change By: davida2009 (17/Nov/14 2:38 PM) Attachment: Jenkins_screenshot.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25648) P4_CHANGELIST variable points to unshelved cl , not synced CL
Morne Joubert created JENKINS-25648 P4_CHANGELIST variable points to unshelved cl , not synced CL Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 17/Nov/14 2:39 PM Description: I would like to extract the CL that s jobs was synced to and the CL of the shelved job that was un-shelved. It is unclear how these values are available to the job (there is nothing in the documentation) The variable P4_CHANGELIST seems to point to the last CL action. So for a normal sync to CL 1000 the value maps to P4_CHANGELIST =1000 If i now test a shelved CL 1050 the value maps to P4_CHANGELIST =1050 This is problematic since the code didn't sync to 1050, it just unshelved 1050. Since the job passes in the shelved CL number , i do have access to it but i need the P4_CHANGELIST to point to the CL that was synced. Project: Jenkins Priority: Minor Reporter: Morne Joubert This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25641) Need to share variables between jobs without using globale variables
Anis benAli updated JENKINS-25641 Need to share variables between jobs without using globale variables Change By: Anis benAli (17/Nov/14 2:36 PM) Priority: Minor Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-ucm-plugin] (JENKINS-25647) LoadRules not properly added in certain situations (case 12301)
Mads Nielsen created JENKINS-25647 LoadRules not properly added in certain situations (case 12301) Issue Type: Bug Assignee: Praqma Support Components: clearcase-ucm-plugin Created: 17/Nov/14 2:34 PM Project: Jenkins Priority: Major Reporter: Mads Nielsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-25646) Global configuration enforces job configuration without tri-state
Kanstantsin Shautsou created JENKINS-25646 Global configuration enforces job configuration without tri-state Issue Type: Improvement Assignee: Honza Brázdil Components: ghprb-plugin Created: 17/Nov/14 2:32 PM Description: I think something wrong with global/job configuration inheritance. I always expect to have default values in global configuration and ability to change any setting in job configuration. AFAIK usually it: new job uses global configuration as it default values, all values then saved to job configuration and global configuration doesn't override them. In this case if you want do mass changes from global configuration you should use groovy script that will do mass changes using jenkins api (i.e. scriptler plugin) or other ways. Project: Jenkins Priority: Minor Reporter: Kanstantsin Shautsou This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xunit-plugin] (JENKINS-25527) xUnit reports yield duplicated "Test Result Trend" charts
Jason Davis commented on JENKINS-25527 xUnit reports yield duplicated "Test Result Trend" charts Experiencing the same problem after upgrading to v1.92 (I only performed plugin upgrades) - however, I noticed the issue with existing reports. The duplicate chart appeared right after restarting Jenkins and before any builds occurred. I'm generating mstest results in a freestyle project on a windows host and slave. jenkins version is 1.585. Downgrading to v1.91 didn't help resolve the duplicate test result charts issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-23600) SDK repositories and emulator images do not install
clemp6r commented on JENKINS-23600 SDK repositories and emulator images do not install Any news? For me it's a blocker issue that prevent using the android emulator 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] [cli] (JENKINS-25606) PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source
Joshua Strouse commented on JENKINS-25606 PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source Would it be preferable to create a new issue regarding the new error that Shane and I have seen when changing to JDK 7? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-plugin] (JENKINS-25645) Plugin writes out "Triggerin projects: myproject" even if no project succeeds to be triggered.
Tomas Westling created JENKINS-25645 Plugin writes out "Triggerin projects: myproject" even if no project succeeds to be triggered. Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger-plugin Created: 17/Nov/14 2:13 PM Description: If I setup a nonblocking project to trigger as a build step and get a failure to trigger this project (in my case due to a missing property file). I get the printouts: [parameterizedtrigger] Properties file $SOMETHING did not exist. Not triggering due to missing file Triggering projects: myproject When myproject in fact is never triggered. Environment: Jenkins 1.554.2, parameterized trigger plugin 2.25 Project: Jenkins Priority: Minor Reporter: Tomas Westling This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle-jpi-plugin] (JENKINS-25643) Not able to use example build.gradle file with Java 8
Hallvard Nygård commented on JENKINS-25643 Not able to use example build.gradle file with Java 8 Seems to be an issue with Gradle user home being a network share (corporate setup). The example in "doc" does not 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] [log-parser-plugin] (JENKINS-25644) image urls don't respect the jenkins base url
martin sarsale created JENKINS-25644 image urls don't respect the jenkins base url Issue Type: Bug Assignee: rgoren Components: log-parser-plugin Created: 17/Nov/14 1:59 PM Description: My jenkins is configured in http://jenkins.local:8091/jenkins/ but the URLs images linked from the log-parser-plugin don't include the '/jenkins/' part: eh: http://jenkins.local:8091///plugin/log-parser/images/red.gif Project: Jenkins Priority: Minor Reporter: martin sarsale This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [log-parser-plugin] (JENKINS-25644) log parser image urls don't respect the jenkins base url
martin sarsale updated JENKINS-25644 log parser image urls don't respect the jenkins base url Change By: martin sarsale (17/Nov/14 1:59 PM) Summary: log parser image urls don't respect the jenkins base 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.
