[JIRA] [p4-plugin] (JENKINS-32454) new option to delete perforce client view & workspace on job deletion
Title: Message Title Patrick Byrne commented on JENKINS-32454 Re: new option to delete perforce client view & workspace on job deletion That seems entirely reasonable to me: our many users are not going to bother setting checkboxes themselves and from my POV it would be much better to manage this centrally. Thanks for your attention. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-32454) new option to delete perforce client view & workspace on job deletion
Title: Message Title Patrick Byrne updated an issue Jenkins / JENKINS-32454 new option to delete perforce client view & workspace on job deletion Change By: Patrick Byrne Could we please have two checkboxes on the options for the perforce plugin for a job. One would be 'delete client on job deletion' and the other would be 'delete client root on job deletion'.The first would delete the client workspace in Jenkins ie 'p4 client - f d 'The second would delete the client workspace root directory ie all the checked-out files.Perhaps the global plugin configuration could have two further checkboxes so that these could default to 'on'?Having this feature would facilitate admin on our jenkins servers.I hope this feature is seen as potentially useful to others. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-32454) new option to delete perforce client view & workspace on job deletion
Title: Message Title Patrick Byrne created an issue Jenkins / JENKINS-32454 new option to delete perforce client view & workspace on job deletion Issue Type: New Feature Assignee: Unassigned Components: p4-plugin Created: 14/Jan/16 2:26 PM Environment: O/S: RedHat Enterprise Linux Server 6.4 (Santiago) JRE: Java(TM) SE Runtime Environment 1.8.0_60-b27 p4-plugin: 1.3.6-SNAPSHOT (private-1843330f-pallen) running jenkins directly Labels: perforce Priority: Minor Reporter: Patrick Byrne Could we please have two checkboxes on the options for the perforce plugin for a job. One would be 'delete client on job deletion' and the other would be 'delete client root on job deletion'. The first would delete the client workspace in Jenkins ie 'p4 client -f ' The second would delete the client workspace root directory ie all the checked-out files. Perhaps the global plugin configuration could
[JIRA] [ansicolor-plugin] (JENKINS-11752) ANSI color plugin adds garbage to log
Title: Message Title Patrick Byrne commented on JENKINS-11752 Re: ANSI color plugin adds garbage to log Yes, these appear to be ~2Kb (7-zip) compressed files embedded in each line of output. This has to be one of the most egregious examples of 'bloat' which I have seen. I would love to hear an explanation of why this was ever thought to be a good idea. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ansicolor] (JENKINS-11752) ANSI color plugin adds garbage to log
Patrick Byrne commented on JENKINS-11752 ANSI color plugin adds garbage to log This affects us at the moment. Jenkins ver 1.508 ANSIColor 0.31 It makes our log files 1000x larger - this is ridiculous! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-13865) Jenkins /queue/api does not produce properly formatted JSON when a build in queue where the destination node/s are busy.
Patrick Byrne commented on JENKINS-13865 Jenkins /queue/api does not produce properly formatted JSON when a build in queue where the destination node/s are busy. Running 1.506 and we are seeing this log file 'decoration' when color xterm output is turned on. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-3265) Reload Configuration from Disk (or POSTing config.xml) loses info on running builds
Patrick Byrne commented on JENKINS-3265 Reload Configuration from Disk (or POSTing config.xml) loses info on running builds Seeing this in 1.492 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
