[JIRA] [disk-usage-plugin] (JENKINS-22224) one job configuration change results in three Job Config History entries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-4 Re: one job configuration change results in three Job Config History entries Code changed in jenkins User: lvotypko Path: src/main/java/hudson/plugins/disk_usage/DiskUsageItemListener.java src/main/java/hudson/plugins/disk_usage/DiskUsageProperty.java src/main/java/hudson/plugins/disk_usage/DiskUsageWorkspaceListener.java http://jenkins-ci.org/commit/disk-usage-plugin/64a823acf27cf33fd71851f0c01bc3cd3013226f Log: Remove multiple saving. JENKINS-4 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] [disk-usage-plugin] (JENKINS-22224) one job configuration change results in three Job Config History entries
Title: Message Title Lucie Votypkova commented on JENKINS-4 Re: one job configuration change results in three Job Config History entries Hi data is moved into separate file. But another problem was with losing DiskUsageProperty during saving. This is fixed in https://github.com/jenkinsci/disk-usage-plugin/commit/64a823acf27cf33fd71851f0c01bc3cd3013226f. It will be included in version 0.26 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] [disk-usage-plugin] (JENKINS-22224) one job configuration change results in three Job Config History entries
Title: Message Title Lucie Votypkova resolved as Fixed Jenkins / JENKINS-4 one job configuration change results in three Job Config History entries Change By: Lucie Votypkova Status: Open Resolved Resolution: Fixed 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] [disk-usage-plugin] (JENKINS-22224) one job configuration change results in three Job Config History entries
Kanstantsin Shautsou commented on JENKINS-4 one job configuration change results in three Job Config History entries Lycie, i think it makes sense to move runtime data into TransientProjectAction (if you need i can provide examples), but keep in JobProperty only configuration about disk-usage plugin. What do you think? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage-plugin] (JENKINS-22224) one job configuration change results in three Job Config History entries
Helge Klug updated JENKINS-4 one job configuration change results in three Job Config History entries Change By: Helge Klug (20/Apr/15 7:30 AM) Assignee: HelgeKlug LucieVotypkova This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage-plugin] (JENKINS-22224) one job configuration change results in three Job Config History entries
Helge Klug assigned JENKINS-4 to Helge Klug one job configuration change results in three Job Config History entries Change By: Helge Klug (20/Apr/15 7:29 AM) Assignee: LucieVotypkova HelgeKlug This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage-plugin] (JENKINS-22224) one job configuration change results in three Job Config History entries
Kanstantsin Shautsou edited a comment on JENKINS-4 one job configuration change results in three Job Config History entries 1) scm-sync-configuration-plugin is bad itself 2) JobProperty is a right place for storing information and it's not a bug. 3) disk-usage can migrate for storing data in separate xml files but backward compatibility and performance is under question. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage-plugin] (JENKINS-22224) one job configuration change results in three Job Config History entries
Kanstantsin Shautsou commented on JENKINS-4 one job configuration change results in three Job Config History entries 1) scm-sync-configuration-plugin is bad itself 2) JobProperty is a right place for storing information and it's not a bug. 3) disk-usage can save info in separate xml files but backward compatibility and performance is under question. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage-plugin] (JENKINS-22224) one job configuration change results in three Job Config History entries
Dmitry Maslakov updated JENKINS-4 one job configuration change results in three Job Config History entries I do not use Disk Usage plug-in, but it's enabled. On some job I see: $ grep DiskUsageProperty jobs/job-name/config.xml |wc -l 4228 I.e., the line `hudson.plugins.disk__usage.DiskUsageProperty plugin="disk-usage@0.24"/` appeared 4228 times! And it continues to add more and more. Adding these lines is not related to configuration changes neither new builds of the job (this is not very actively used job). Another thing to note is I have about 200 jobs, and all of them are suffered: $ grep DiskUsageProperty jobs/*/config.xml |wc -l 78483 But this is still not the end of that sad story. Using scm-sync-configuration-plugin for Jenkins configuration backup it lead to thousands of commits in backup SCM repository per day: it spams the log and increases the repository size without real need. So let me raise the bug priority. Change By: Dmitry Maslakov (08/Dec/14 4:52 AM) Priority: Minor Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage-plugin] (JENKINS-22224) one job configuration change results in three Job Config History entries
Danny Staple commented on JENKINS-4 one job configuration change results in three Job Config History entries We are seeing a general problem here - some of the plugins appear (parameterizedTrigger, ThrottleConcurrentbuilds, NodeLabel, ExtendedChoice are current suspects) to do this too - we are now having as many as 8 (!!) saves in the config. For some plugins, it seems that when there is no change, they save a no-diff config. Almost as if each is doing their own save in order. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage-plugin] (JENKINS-22224) one job configuration change results in three Job Config History entries
Marc Günther commented on JENKINS-4 one job configuration change results in three Job Config History entries +1 We are not using disk-usage plugin anymore, cause it's so slow, but I still see this behaviour. So it's definitely not restricted to disk-usage plugin alone This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
