[JIRA] [cppcheck] (JENKINS-22965) Cppcheck plugin shall display the inconclusive messages
Alexander Mai commented on JENKINS-22965 Cppcheck plugin shall display the inconclusive messages Thanks for fixing/implementing. The homepage mentions a 1.17 as of May, 18th. But it's not yet fully released? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind] (JENKINS-23178) Read DynamicAnalysis.xml written by CTest
Johannes Ohlemacher resolved JENKINS-23178 as Postponed Read DynamicAnalysis.xml written by CTest Its not a bug. The file from CTest is not a valgrind xml file, its completely different. The file from CTest does not even contain easily parsable xml data from valgrind, its just the standard output. The memcheck feature of CTest seems still to be experimental, CTest must export valid valgrind xml to make this work! Change By: Johannes Ohlemacher (25/May/14 11:31 AM) Status: Open Resolved Resolution: Postponed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-3839) setuid support on Linux
Daniel Beck resolved JENKINS-3839 as Wont Fix setuid support on Linux Feature nobody seems interested in. Also, can easily be achieved using reverse proxy, or probably by just configuration iptables. Change By: Daniel Beck (25/May/14 11:42 AM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-4597) Hudson Upgrade succeeded, Jobs creation and saving fails
Daniel Beck resolved JENKINS-4597 as Cannot Reproduce Hudson Upgrade succeeded, Jobs creation and saving fails Needs to be reproduced on recent Jenkins versions to be relevant. Change By: Daniel Beck (25/May/14 11:46 AM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-4307) Ability to enter MD5 fingerprint instead of file upload
Daniel Beck resolved JENKINS-4307 as Cannot Reproduce Ability to enter MD5 fingerprint instead of file upload Just navigate to /fingerprint/abc to see files with the fingerprint abc. Linking there can be easily accomplished from plugins or user scripts. Change By: Daniel Beck (25/May/14 11:45 AM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-4663) WorkspaceCleanupThread nukes Bazaar shared repositores on build slaves
Daniel Beck resolved JENKINS-4663 as Cannot Reproduce WorkspaceCleanupThread nukes Bazaar shared repositores on build slaves 1.551 changed how workspace cleanup work, so needs to be reproduced in newer versions to be relevant. Also, workspace cleanup can be disabled completely using a system property. Also, why not store the shared repository outside the top-level 'workspace' folder, e.g. somewhere else in the slave home directory? Change By: Daniel Beck (25/May/14 11:48 AM) Status: InProgress Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-4817) Hudson should capture current Java when generating the Hudson.xml
Daniel Beck resolved JENKINS-4817 as Wont Fix Hudson should capture current Java when generating the Hudson.xml Installer bundles JRE Change By: Daniel Beck (25/May/14 11:51 AM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-5320) java.net.SocketException when saving slave configuration
Daniel Beck resolved JENKINS-5320 as Incomplete java.net.SocketException when saving slave configuration Too long ago and too little information for further investigation. Change By: Daniel Beck (25/May/14 11:51 AM) 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] [core] (JENKINS-5472) The directory given with --webroot is cleaned if it already exists, even with existing files
Daniel Beck resolved JENKINS-5472 as Incomplete The directory given with --webroot is cleaned if it already exists, even with existing files Needs to be reproduced using Jenkins 1.535 or newer which is based on Jetty. Change By: Daniel Beck (25/May/14 11:58 AM) 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] [hp-application-automation-tools-plugin] (JENKINS-23180) How to use HP Application Automation Tools (Jenkins plugin) through proxy
JY Cr. created JENKINS-23180 How to use HP Application Automation Tools (Jenkins plugin) through proxy Issue Type: Bug Affects Versions: current Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 25/May/14 12:02 PM Description: Could you please tell me how to configure "HP Application Automation Tools" (https://wiki.jenkins-ci.org/display/JENKINS/HP+Application+Automation+Tools) so as to get it connected with UFT through an authenticated proxy (using NTLM or Basic Authentication) ? Thanks for your help. Project: Jenkins Priority: Major Reporter: JY Cr. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-4888) Incorrect expiry HTTP header
Daniel Beck resolved JENKINS-4888 as Cannot Reproduce Incorrect expiry HTTP header Comments seem to indicate this was resolved in a plugin. Long expiry might break things when the admin decides to update Jenkins or plugins, so there really needs to be a good reason for doing this. Note that If-Modified-Since etc. are supported. Change By: Daniel Beck (25/May/14 12:04 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-5284) Provide generic tool installation support
Daniel Beck resolved JENKINS-5284 as Wont Fix Provide generic tool installation support Covered by Custom Tools plugin. Change By: Daniel Beck (25/May/14 12:04 PM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-6204) Tomcat won't shutdown due to stdout copier threads with no active jobs
Daniel Beck resolved JENKINS-6204 as Cannot Reproduce Tomcat wont shutdown due to stdout copier threads with no active jobs Needs to be reproduced in recent Jenkins versions. Change By: Daniel Beck (25/May/14 12:05 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-6501) Authentication via HTTP Header
Daniel Beck resolved JENKINS-6501 as Wont Fix Authentication via HTTP Header Seems to be covered by Reverse Proxy Auth Plugin. If not, would need a new plugin, rather than core implementation. Change By: Daniel Beck (25/May/14 12:08 PM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-6423) Bounds exceeds available space exception after successful build
Daniel Beck commented on JENKINS-6423 Bounds exceeds available space exception after successful build How can this be reproduced in current Jenkins 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] [core] (JENKINS-6533) Cluster testing of applications
Daniel Beck resolved JENKINS-6533 as Incomplete Cluster testing of applications Nobody interested in this issue. Also, not clear what exactly is the goal here or needs to be done, or whether it's still relevant at all. Change By: Daniel Beck (25/May/14 12:11 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] [core] (JENKINS-6557) Add ability to re-enable multi-configuration ('Matrix') projects from the project main page
Daniel Beck resolved JENKINS-6557 as Cannot Reproduce Add ability to re-enable multi-configuration (Matrix) projects from the project main page Probably resolved a long time ago, cannot reproduce in 1.561 Change By: Daniel Beck (25/May/14 12:12 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-3337) ring buffer of SCM polling log
Daniel Beck commented on JENKINS-3337 ring buffer of SCM polling log It's definitely annoying to come across a disabled job and wonder why it was disabled the polling log just says 'job is disabled', because the 'this directory no longer exists so I'm disabling this job' message is long gone... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-6208) Improve the command line handling of java -jar hudson.jar command to start hudson ...
Daniel Beck resolved JENKINS-6208 as Wont Fix Improve the command line handling of java -jar hudson.jar command to start hudson ... Nobody interested in this improvement, so resolving as Won't Fix. The most serious issue (invalid option names are not flagged) I cannot reproduce in 1.564, it's just that you need two dashes for something to be recognized as an option. Change By: Daniel Beck (25/May/14 12:15 PM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-6874) Shorten job names when used in filesystem and URL paths
Daniel Beck resolved JENKINS-6874 as Cannot Reproduce Shorten job names when used in filesystem and URL paths Essentially accomplished by using 'Display Name' for jobs as their 'Nice' name. For Matrix projects and their axes, there's the hudson.matrix.MatrixConfiguration.useShortWorkspaceName system property. Change By: Daniel Beck (25/May/14 12:17 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-6916) Hudson waits forever if a slave is offline
Daniel Beck resolved JENKINS-6916 as Wont Fix Hudson waits forever if a slave is offline It's not necessarily an error condition, so needs configurability. Jenkins offers the ComputerListener extension point, so it's easy to create a plugin that notifies about that event (Extreme Notification plugin or Ownership plugin might, and the commercial Nodes Plus plugin was designed for this). Change By: Daniel Beck (25/May/14 12:24 PM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7126) Stop All Builds if Master Node is Full
Daniel Beck resolved JENKINS-7126 as Wont Fix Stop All Builds if Master Node is Full Nobody interested in this request, so resolving. Also, Jenkins uses the System property hudson.diagnosis.HudsonHomeDiskUsageChecker.freeSpaceThreshold, by default set to 1GB, to determine when to start warning admins about this issue. Change By: Daniel Beck (25/May/14 12:27 PM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-6031) Build parameters not passed correctly into build step
Daniel Beck resolved JENKINS-6031 as Not A Defect Build parameters not passed correctly into build step This is not a Jenkins bug, but shell behavior, as can be seen by checking the value of HUDSON_BUILD_COMMAND in env output. Change By: Daniel Beck (25/May/14 12:33 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7164) Changelog loading in WebAppMain blocks triggers from executing
Daniel Beck resolved JENKINS-7164 as Cannot Reproduce Changelog loading in WebAppMain blocks triggers from executing Not sure that the status of this is given the new lazy loading, I assume this issue is obsolete, as only recent builds' changelogs are loaded. Change By: Daniel Beck (25/May/14 12:35 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-4215) NPE during test run
Daniel Beck resolved JENKINS-4215 as Incomplete NPE during test run Comment by Alan Harder seems to indicate this has been resolved in August 2010 or so. No response by reporter since. Change By: Daniel Beck (25/May/14 12:34 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] [core] (JENKINS-7047) DNS Multicast announcement appears to only happen at startup
Daniel Beck commented on JENKINS-7047 DNS Multicast announcement appears to only happen at startup Needs to be reproduced in more recent Jenkins. The jmDNS discussion happened in 2010, and Jenkins uses a patched jmDNS from early 2011, so chances are this has been resolved. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-7080) Conditional Post-Build Actions
Daniel Beck resolved JENKINS-7080 as Wont Fix Conditional Post-Build Actions While a simple "only if build is successful" might work as a core feature, more sophisticated conditions should be in plugins. And this functionality is already provided in plugins: Flexible Publish + Conditional Build Step. Change By: Daniel Beck (25/May/14 12:49 PM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7248) Matrix-Job configuration did not recognise if node was deleted
Daniel Beck resolved JENKINS-7248 as Incomplete Matrix-Job configuration did not recognise if node was deleted Needs to be reproduced on recent Jenkins (preferably one with detached Matrix Project plugin). Also, not sure why a new node needs to be set up rather than just changing project configuration. Change By: Daniel Beck (25/May/14 12:50 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] [core] (JENKINS-7541) /createItem fails to create intermediate directories
Daniel Beck commented on JENKINS-7541 /createItem fails to create intermediate directories Is this still an issue in recent Jenkins 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] [core] (JENKINS-7609) auto-installation of maven fails when many builds trigger at the same time
Daniel Beck commented on JENKINS-7609 auto-installation of maven fails when many builds trigger at the same time Is this still an issue in recent Jenkins 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] [core] (JENKINS-8044) displaying line.separator without any quoting doesn't make sense
Daniel Beck commented on JENKINS-8044 displaying line.separator without any quoting doesnt make sense Still an issue on Jenkins 1.561. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-7840) High CPU load - possible endless loop - could be consoleText GET related
Daniel Beck commented on JENKINS-7840 High CPU load - possible endless loop - could be consoleText GET related Has this issue been observed in recent Jenkins versions? Up-to-date stack traces would be helpful. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-7865) Weird scrollbar in Dashboard when viewed with Chrome
Daniel Beck resolved JENKINS-7865 as Cannot Reproduce Weird scrollbar in Dashboard when viewed with Chrome Needs to be reproduced on recent Versions of Chrome and Jenkins. Just file a new issue if it still happens. Change By: Daniel Beck (25/May/14 12:59 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project] (JENKINS-8112) Matrix jobs' build duration includes time when the job was waiting for executors
Daniel Beck updated JENKINS-8112 Matrix jobs build duration includes time when the job was waiting for executors Change By: Daniel Beck (25/May/14 1:00 PM) Component/s: matrix-project Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7685) Raw console output does not work
Daniel Beck commented on JENKINS-7685 Raw console output does not work Can anyone reproduce this on recent versions of 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] [matrix-project] (JENKINS-8112) Matrix jobs' build duration includes time when the job was waiting for executors
Daniel Beck commented on JENKINS-8112 Matrix jobs build duration includes time when the job was waiting for executors Is this still an issue on recent versions of 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] [core] (JENKINS-6697) Too many multicast dns answers
Daniel Beck commented on JENKINS-6697 Too many multicast dns answers Has anyone observed this in a recent version of Jenkins? In mid 2011, jmDNS 3.4.0 was integrated into Jenkins, maybe it's resolved since then? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-8055) Ressurected slave marked as dead although it's online
Daniel Beck resolved JENKINS-8055 as Not A Defect Ressurected slave marked as dead although its online It is marked as offline. Just click the button on the top right. It appears you manually marked it as offline before it went down (or while it was down), and that status isn't removed automatically. Change By: Daniel Beck (25/May/14 1:12 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pam-auth] (JENKINS-8540) [security] the test of unix user/password authentication should check the read permission of the service file of pam
Daniel Beck updated JENKINS-8540 [security] the test of unix user/password authentication should check the read permission of the service file of pam Change By: Daniel Beck (25/May/14 1:10 PM) Component/s: pam-auth Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-8598) Hudsod failed to start when unable to read queue.xml
Daniel Beck resolved JENKINS-8598 as Cannot Reproduce Hudsod failed to start when unable to read queue.xml There have been numerous robustness enhancements since this was reported, so it's likely this is no longer a problem. Please file a new issue and provide the faulty queue.xml + a list of plugins and versions so this can be reproduced. Change By: Daniel Beck (25/May/14 1:13 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-8595) How to disable a bundled plugin?
Daniel Beck resolved JENKINS-8595 as Cannot Reproduce How to disable a bundled plugin? Likely resolved since this was reported, maybe in Jenkins 1.524 or so when the dependency loading issue was fixed. If this still is an issue for you in recent Jenkins versions, please file a new bug. Change By: Daniel Beck (25/May/14 1:14 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-8728) Hudson.getTopLevelItemNames() does not enforce permissions
Daniel Beck resolved JENKINS-8728 as Cannot Reproduce Hudson.getTopLevelItemNames() does not enforce permissions This feature is not used at all in core 1.564 (and can probably be deprecated). Change By: Daniel Beck (25/May/14 1:17 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-8257) Add timestamp of last event to json api
Daniel Beck
resolved JENKINS-8257 as Wont Fix
Add timestamp of last event to json api
Very narrow use case, not something that should be in core.
Also, {{/api/xml?tree=jobs[lastCompletedBuildtimestamp]}} + minimal XML parsing should do the trick.
Change By:
Daniel Beck
(25/May/14 1:56 PM)
Status:
Open
Resolved
Resolution:
WontFix
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project] (JENKINS-8898) it should be possible to make labels/axis/nodes optional
Daniel Beck updated JENKINS-8898 it should be possible to make labels/axis/nodes optional Change By: Daniel Beck (25/May/14 2:14 PM) Component/s: matrix-project Component/s: matrix Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project] (JENKINS-8898) it should be possible to make labels/axis/nodes optional
Daniel Beck commented on JENKINS-8898 it should be possible to make labels/axis/nodes optional Is this still an issue for you? It could be possible to provide this feature by implementing an extension point. I may look into it if there's a need for 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-3921) Node provisioning fails when only tied nodes available and untied jobs are waiting to run
Daniel Beck commented on JENKINS-3921 Node provisioning fails when only tied nodes available and untied jobs are waiting to run Is this issue still unresolved on recent Jenkins 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] [core] (JENKINS-8938) Ability to Register a Listener for when Cloud nodes are created and destroyed
Daniel Beck resolved JENKINS-8938 as Cannot Reproduce Ability to Register a Listener for when Cloud nodes are created and destroyed Fixed in 1.520: http://javadoc.jenkins-ci.org/hudson/slaves/CloudProvisioningListener.html Change By: Daniel Beck (25/May/14 2:18 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-9057) Hability to disable slaves
Daniel Beck commented on JENKINS-9057 Hability to disable slaves Is this needed on a per-slave basis, or could this be done globally for all disconnected or marked offline (which?) slaves? What is the use case for this feature? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-8950) CLONE - Disable polling if build is running
Daniel Beck resolved JENKINS-8950 as Wont Fix CLONE - Disable polling if build is running Nobody is interested in this feature, so resolving as Won't Fix. Also, it's not obvious why a new build shouldn't be queued after the current build checked out from SCM and a new change was detected. Querying SCM every minute is unnecessarily expensive anyway, if you need immediate builds, just switch to post-commit hook notifications. Also, behavior would need to be determined for parallel build projects. Change By: Daniel Beck (25/May/14 2:23 PM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-5189) When you trigger a task there is no page for it until the task starts to build
Daniel Beck resolved JENKINS-5189 as Duplicate When you trigger a task there is no page for it until the task starts to build Change By: Daniel Beck (25/May/14 2:26 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] [core] (JENKINS-7135) No such file or directory error when project contains space (no container is used)
Daniel Beck resolved JENKINS-7135 as Not A Defect No such file or directory error when project contains space (no container is used) Looks more like a bug in the reporter's shell script build step, judging by this line: + /Users/vpdn/.hudson/jobs/My App/workspace/build.sh Change By: Daniel Beck (25/May/14 2:29 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-9439) Jump to bottom in console output
Daniel Beck resolved JENKINS-9439 as Wont Fix Jump to bottom in console output Nobody interested in this issue, so I guess the reporter discovered the End key on the keyboard. Change By: Daniel Beck (25/May/14 2:30 PM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-9668) Language control for build broke mails.
Daniel Beck resolved JENKINS-9668 as Not A Defect Language control for build broke mails. Not a defect: You're starting the Jenkins service with German locale, which is the default locale used inside Jenkins (e.g. parts of build logs as well). Change By: Daniel Beck (25/May/14 2:31 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-9707) plugin manager: when installing new plugins, checkbox states should be consistent.
Daniel Beck resolved JENKINS-9707 as Cannot Reproduce plugin manager: when installing new plugins, checkbox states should be consistent. Resolved in 1.447: https://github.com/jenkinsci/jenkins/commit/439c56a5a5f68aac27de0e06eae8b4ffc49fa5f0 Change By: Daniel Beck (25/May/14 2:35 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-9738) Upgrading from Hudson to Jenkins, shows 2 Editable Email Notification plugins
Daniel Beck commented on JENKINS-9738 Upgrading from Hudson to Jenkins, shows 2 Editable Email Notification plugins Is this still a relevant issue, or was this temporary/did you resolve 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-4247) Hudson build now link violates RFC 2616
Daniel Beck commented on JENKINS-4247 Hudson build now link violates RFC 2616 AFAICT this is still an issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10019) Incorrect node name (capitalized) shows under Build Executor Status column of main Dashboard
Daniel Beck resolved JENKINS-10019 as Cannot Reproduce Incorrect node name (capitalized) shows under Build Executor Status column of main Dashboard master node has lowercase m on Jenkins 1.561 Change By: Daniel Beck (25/May/14 2:41 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ws-cleanup] (JENKINS-10022) Delete workspace build step fails silently if it cant remove some folders in the workspace
Daniel Beck updated JENKINS-10022 Delete workspace build step fails silently if it cant remove some folders in the workspace Change By: Daniel Beck (25/May/14 2:43 PM) Component/s: ws-cleanup Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10023) Add a default fs root/workspace folder for master executor
Daniel Beck resolved JENKINS-10023 as Cannot Reproduce Add a default fs root/workspace folder for master executor This has been the default for quite some time, and besides that, it's configurable. Change By: Daniel Beck (25/May/14 2:44 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-3924) Export the useSecurity field of Hudson via the XML API
Daniel Beck commented on JENKINS-3924 Export the useSecurity field of Hudson via the XML API Jesse: Your comment indicates this cannot reasonably be solved on Jenkins side. Any client can query whether security is enabled, and offer auth regardless of what can be accessed anonymously. Resolve as 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] [core] (JENKINS-10152) auto-expand Advanced Project Options when at least one option is enabled
Daniel Beck resolved JENKINS-10152 as Wont Fix auto-expand Advanced Project Options when at least one option is enabled There's a new 'Changed' indicator (an icon) ob Advanced sections. Auto-expand would result in config pages that are too long, and just doing this for 'Advanced Project Options' would be inconsistent. Change By: Daniel Beck (25/May/14 2:47 PM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-7566) Could you add a verbose option to cli
Alex Lehmann reopened JENKINS-7566 Could you add a verbose option to cli Change By: Alex Lehmann (25/May/14 2:49 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] [cli] (JENKINS-7566) Could you add a verbose option to cli
Alex Lehmann commented on JENKINS-7566 Could you add a verbose option to cli That is entirely not what I meant, Jenkins provides a CLI command interface client that can be used to trigger operations from a shell script or manually on the command line https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-4501) WorkspaceCleanupThread deletes Matrix project workspaces
Daniel Beck commented on JENKINS-4501 WorkspaceCleanupThread deletes Matrix project workspaces This needs to be confirmed to still be an issue on 1.551+ which changed how the workspace cleanup works. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-6867) Overall unit test time report.
Daniel Beck commented on JENKINS-6867 Overall unit test time report. Is this still issue still relevant in current 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] [core] (JENKINS-9884) Upgrade to Jenkins from Hudson gives AbstractMethodError in some views
Daniel Beck resolved JENKINS-9884 as Cannot Reproduce Upgrade to Jenkins from Hudson gives AbstractMethodError in some views Looks obsolete, nobody watching this issue. Change By: Daniel Beck (25/May/14 2:52 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10477) The executor widget is still showing build number even after the build display name is updated
Daniel Beck assigned JENKINS-10477 to Daniel Beck The executor widget is still showing build number even after the build display name is updated Change By: Daniel Beck (25/May/14 2:56 PM) Assignee: KohsukeKawaguchi DanielBeck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-12450) Interpret Nested Variables Throughout Jenkins
Daniel Beck
resolved JENKINS-12450 as Wont Fix
Interpret Nested Variables Throughout Jenkins
Nobody seems to care about this feature. Also, use case is not compelling:
It's possible to define
RELEASE_BRANCH=http:///${BRANCH}_BRANCH
and this will evaluate correctly wherever $BRANCH is defined.
Change By:
Daniel Beck
(25/May/14 2:59 PM)
Status:
Open
Resolved
Resolution:
WontFix
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-9057) Hability to disable slaves
ingmartinlopez commented on JENKINS-9057 Hability to disable slaves In my case it's needed on a per slave basis. Example: you have to do maintenance to one of the slaves (so you know that this particular slave is going to be offline for a while), but you want to know if one of the others (productive) are offline to take actions. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10477) The executor widget is still showing build number even after the build display name is updated
Daniel Beck started work on JENKINS-10477 The executor widget is still showing build number even after the build display name is updated Change By: Daniel Beck (25/May/14 3:05 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10477) The executor widget is still showing build number even after the build display name is updated
Daniel Beck commented on JENKINS-10477 The executor widget is still showing build number even after the build display name is updated https://github.com/jenkinsci/jenkins/pull/1254 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-6329) Build fails with Unable to delete ...config.xml which is read-only for a period when read through API
Daniel Beck commented on JENKINS-6329 Build fails with Unable to delete ...config.xml which is read-only for a period when read through API Does this issue still occur on recent Jenkins 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] [core] (JENKINS-6921) deleting project with a queued build leaves build in queue
Daniel Beck commented on JENKINS-6921 deleting project with a queued build leaves build in queue Can reproduce the issue on 1.564. Still, I don't think we need to consider issues like this valid bugs, do we? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-6636) Hudson-internally Usergroups with Active Directory
Daniel Beck resolved JENKINS-6636 as Wont Fix Hudson-internally Usergroups with Active Directory Nobody seems interested in this. Plugins like Role Strategy and Role Based Access Control provide their own solutions to this issue anyway. Change By: Daniel Beck (25/May/14 3:12 PM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-5533) Support renaming in SCM changelog
Daniel Beck resolved JENKINS-5533 as Wont Fix Support renaming in SCM changelog Four years old, no interest in this feature, so resolving as Won't Fix. Change By: Daniel Beck (25/May/14 3:13 PM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-7566) Could you add a verbose option to cli
Oleg Nenashev commented on JENKINS-7566 Could you add a verbose option to cli As I've mentioned previously, the "build" command in CLI provides the execution track if you specify proper options. I suppose it resolved your example case. What particular info would you like to get in such "verbose" mode? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-6000) Enable front-end developers to contribute plugins without complicated java
Daniel Beck resolved JENKINS-6000 as Wont Fix Enable front-end developers to contribute plugins without complicated java Interesting idea, but as there is zero interest after four years... IMO: Since plugins need to be packaged anyway, anyone would need to use Maven, and the few bits of Java (basically copying from the HelloWorldBuilder sample extension) shouldn't be much more difficult to put together. Change By: Daniel Beck (25/May/14 3:16 PM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7066) Glassfishv3 domain stops when using Hudson job to start the Glassfishv3 domain
Daniel Beck resolved JENKINS-7066 as Incomplete Glassfishv3 domain stops when using Hudson job to start the Glassfishv3 domain No response to comment asking for more information 4 years ago, so this is probably obsolete. Change By: Daniel Beck (25/May/14 3:18 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] [core] (JENKINS-9057) Hability to disable slaves
Daniel Beck resolved JENKINS-9057 as Duplicate Hability to disable slaves Change By: Daniel Beck (25/May/14 3:20 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] [core] (JENKINS-8763) Allow Athorisations to be revoked per Job
Daniel Beck resolved JENKINS-8763 as Cannot Reproduce Allow Athorisations to be revoked per Job Has recently been implemented using a preference to not inherit parent ACL. Change By: Daniel Beck (25/May/14 3:21 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-9057) Hability to disable slaves
Daniel Beck commented on JENKINS-9057 Hability to disable slaves In that case the criterion for hiding would be "marked offline" as opposed to "disconnected", which can be done globally (i.e. not introducing a new per-slave preference). Duplicates JENKINS-8834. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-9754) Poll SCM with too few values - Exception
FireFart closed JENKINS-9754 as Wont Fix Poll SCM with too few values - Exception Change By: FireFart (25/May/14 3:22 PM) Status: Open Closed Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-8701) Can't disable a Maven style job via GET method
Daniel Beck resolved JENKINS-8701 as Not A Defect Cant disable a Maven style job via GET method Not a bug, the problem is with Freestyle job (see related JENKINS-4247) Change By: Daniel Beck (25/May/14 3:22 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mstest] (JENKINS-7386) MSTest - Hudson processes trx File even if build failed
FireFart closed JENKINS-7386 as Wont Fix MSTest - Hudson processes trx File even if build failed Change By: FireFart (25/May/14 3:22 PM) Status: Open Closed Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [windmill] (JENKINS-7714) No Configuration Option for Windmill Plugin
FireFart closed JENKINS-7714 as Wont Fix No Configuration Option for Windmill Plugin Change By: FireFart (25/May/14 3:22 PM) Status: Open Closed Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7236) Define directory for log files
Daniel Beck edited a comment on JENKINS-7236 Define directory for log files Slave logs have been moved to $JENKINS_HOME/logs/slaves some time before 1.561, but others don't seem to have been moved. I see: Calculation of builds disk usage.log Calculation of job directories (without builds).log Calculation of workspace usage.log Connection Activity monitoring to slaves.log Download metadata.log Fingerprint cleanup.log Out of order build detection.log Project disk usage.log Workspace clean-up.log Sure, quite a few plugins here, but still. Those should probably be moved to logs as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-7236) Define directory for log files
Daniel Beck commented on JENKINS-7236 Define directory for log files Slave logs have been moved to $JENKINS_HOME/logs/slaves, but others don't seem to have been moved. I see: Calculation of builds disk usage.log Calculation of job directories (without builds).log Calculation of workspace usage.log Connection Activity monitoring to slaves.log Download metadata.log Fingerprint cleanup.log Out of order build detection.log Project disk usage.log Workspace clean-up.log Sure, quite a few plugins here, but still. Those should probably be moved to logs as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-11016) Add an option to try again after a failed Jenkins upgrade
Daniel Beck commented on JENKINS-11016 Add an option to try again after a failed Jenkins upgrade It's not that difficult to download the jar manually and place it on the server. If it failed in the first place, it's not necessarily a bad idea to force the admin to log in, resolve the issue, and clean 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] [core] (JENKINS-9185) ProcessTreeKiller / BUILD_ID from Maven task
Daniel Beck commented on JENKINS-9185 ProcessTreeKiller / BUILD_ID from Maven task Does this issue still occur on recent Jenkins versions? Is there a simply script that when run in a build shows the problem so anyone investigating this doesn't have to deploy Tomcat from Maven? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-10923) /safeRestart doesn't work on AIX
Daniel Beck updated JENKINS-10923 /safeRestart doesnt work on AIX Change By: Daniel Beck (25/May/14 3:32 PM) Labels: aix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-9308) Changes description text corrupted
Daniel Beck commented on JENKINS-9308 Changes description text corrupted Is this issue still occurring in recent Jenkins 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] [xvfb] (JENKINS-23155) Only run plugin under Linux
SCM/JIRA link daemon commented on JENKINS-23155 Only run plugin under Linux Code changed in jenkins User: Zoran Regvart Path: src/main/java/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper.java src/main/resources/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper/config.jelly src/main/resources/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper/help-assignedLabels.html http://jenkins-ci.org/commit/xvfb-plugin/8351332de50d10e86b5eb72a4840c0f1fddfdd43 Log: JENKINS-23155 Only run plugin under Linux This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvfb] (JENKINS-23155) Only run plugin under Linux
zregvart commented on JENKINS-23155 Only run plugin under Linux Hi, I've released a beta version of the plugin with the label mechanism which you can get via the experimental plugins update site (see http://jenkins-ci.org/content/experimental-plugins-update-center). Let me know if that's what you had in mind and it works ok for you Zoran This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvfb] (JENKINS-23163) xserver 1.13 does not support -displayfd
zregvart resolved JENKINS-23163 as Fixed xserver 1.13 does not support -displayfd Hi, I've updated the wiki to state 'a recent version of xserver' without mentioning specifics. Funny thing is that -displayfd option was introduced into version 1.12.99.901 (http://lists.freedesktop.org/archives/xorg/2012-July/054640.html) onward... Change By: zregvart (25/May/14 4:01 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvfb] (JENKINS-23163) xserver 1.13 does not support -displayfd
zregvart closed JENKINS-23163 as Fixed xserver 1.13 does not support -displayfd Change By: zregvart (25/May/14 4:02 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvfb] (JENKINS-23163) xserver 1.13 does not support -displayfd
SCM/JIRA link daemon commented on JENKINS-23163 xserver 1.13 does not support -displayfd Code changed in jenkins User: Zoran Regvart Path: src/main/resources/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper/help-autoDisplayName.html http://jenkins-ci.org/commit/xvfb-plugin/bcbba1f36ce7de84eee13c358fa0734309c6280b Log: JENKINS-23163 xserver 1.13 does not support -displayfd This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-22853) SEVERE: Trying to unexport an object that's already unexported
Bryan Kelly commented on JENKINS-22853 SEVERE: Trying to unexport an object thats already unexported I just completed upgrading to 1.564 and have captured the following logging information. It would appear that our environment is reporting these following stack traces repeatedly. I will continue to monitor the environment. We did upgrade the master node to java 8 as well as apart of this upgrade. May 25, 2014 11:00:07 AM SEVERE hudson.remoting.ExportTable unexportByOid Trying to unexport an object that's already unexported java.lang.IllegalStateException: Invalid object ID 5 iota=171 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:277) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:300) at hudson.remoting.Channel.unexport(Channel.java:600) at hudson.remoting.ProxyOutputStream$Unexport$1.run(ProxyOutputStream.java:352) at hudson.remoting.PipeWriter$1.run(PipeWriter.java:158) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:111) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.Exception: Object was recently deallocated #5 (ref.0) : hudson.CloseProofOutputStream Created at Sun May 25 10:24:01 CDT 2014 at hudson.remoting.ExportTable$Entry.init(ExportTable.java:86) at hudson.remoting.ExportTable.export(ExportTable.java:239) at hudson.remoting.Channel.export(Channel.java:592) at hudson.remoting.RemoteOutputStream.writeObject(RemoteOutputStream.java:82) at sun.reflect.GeneratedMethodAccessor140.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:988) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348) at hudson.util.StreamTaskListener.writeObject(StreamTaskListener.java:161) at sun.reflect.GeneratedMethodAccessor141.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:988) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348) at hudson.remoting.UserRequest._serialize(UserRequest.java:155) at hudson.remoting.UserRequest.serialize(UserRequest.java:164) at hudson.remoting.UserRequest.init(UserRequest.java:62) at hudson.remoting.Channel.call(Channel.java:738) at hudson.Launcher$RemoteLauncher.launch(Launcher.java:888) at hudson.Launcher$ProcStarter.start(Launcher.java:355) at hudson.Launcher$ProcStarter.join(Launcher.java:362) at hudson.tools.AbstractCommandInstaller.performInstallation(AbstractCommandInstaller.java:77) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:61) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:107) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:204) at hudson.plugins.git.GitTool.forNode(GitTool.java:79) at hudson.plugins.git.GitSCM.getGitExe(GitSCM.java:679) at
[JIRA] [core] (JENKINS-10500) Execute shell environment variables
Daniel Beck updated JENKINS-10500 Execute shell environment variables This already exists: Plugins can contribute whatever they want to the job environment. However, the description of available environment variables is hard-coded and does not consider plugins. (SVN and CVS used to be core features) This could probably improved. For now, just check the documentation of the plugin and/or run set (Windows) or env (Linux) to find out what environment variables get contributed to the build. Change By: Daniel Beck (25/May/14 4:20 PM) Priority: Major Trivial This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-9503) Add View Column that displays time since last commit
Daniel Beck resolved JENKINS-9503 as Wont Fix Add View Column that displays time since last commit There is no way to reliably get the necessary information without polling (or post-commit hooks), the the projects that use these get built anyway when there's a change; so "last failed/successful build" columns do essentially the same job. For the apparent effort, there is just not enough support for this issue, so this will probably not be implemented. Change By: Daniel Beck (25/May/14 4:23 PM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-9851) Daemon.java set's the process' name as exe on Unix
Daniel Beck resolved JENKINS-9851 as Cannot Reproduce Daemon.java sets the process name as exe on Unix Obsolete, now resolves symlink to actual executable: https://github.com/kohsuke/akuma/blob/master/src/main/java/com/sun/akuma/Daemon.java#L229 Change By: Daniel Beck (25/May/14 4:26 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
