[JIRA] [disk-usage] (JENKINS-22224) one job configuration change results in three Job Config History entries
Thomas Van Doren commented on JENKINS-4 one job configuration change results in three Job Config History entries I figured out why my publisher configs were disappearing. It happened when a new build started and one of the publisher values was invalid. For example, if a text field was expected to be SUCCESS or UNSTABLE and it had something invalid like STABLE, that particular publisher config would just be deleted when the job started. It would be nice if the API could validate the config using whatever logic is run before builds starts, but that is a separate issue from this one. Sorry for the confusion. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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] (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 It is a problem, cause it is convoluting your job config history. If every plugin did something like this, the history would be completely useless. Disappearing publisher configs are of course an even bigger problem... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage] (JENKINS-22224) one job configuration change results in three Job Config History entries
Thomas Van Doren commented on JENKINS-4 one job configuration change results in three Job Config History entries I see this, which isn't really a problem. I have seen a problem where adding the DiskUsageProperty results in some, and often times all, the publisher configs disappearing. I'm still investigating whether it is a bug in this plugin, the jenkins core, or the jenkins API. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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] (JENKINS-22224) one job configuration change results in three Job Config History entries
Marc Günther
updated JENKINS-4
one job configuration change results in three Job Config History entries
Change By:
Marc Günther
(18/Mar/14 6:37 PM)
Description:
Every time I make a configuration change to a job, I get three entries in the Job Config History view:# removal of the config for {{disk-usage}} plugin# actual change I made# addition of the config of {{disk-usage}} againThe removed and re-added line looks like this:{code}{code}Expected: 1. and 3. should not happen..
EDIT:I have now also seen a case where 1. and 2. are combined into one change, and 3. is the second change.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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] (JENKINS-22224) one job configuration change results in three Job Config History entries
Marc Günther
updated JENKINS-4
one job configuration change results in three Job Config History entries
Change By:
Marc Günther
(17/Mar/14 2:17 PM)
Description:
Every time I make a configuration change to a job, I get three entries in the Job Config History view:# removal of the config for {{disk-usage}} plugin# actual change I made#
add
addition
of the config of {{disk-usage}} againThe removed and re-added line looks like this:{code}{code}Expected: 1. and 3. should not happen..
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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] (JENKINS-22224) one job configuration change results in three Job Config History entries
Marc Günther created JENKINS-4 one job configuration change results in three Job Config History entries Issue Type: Bug Assignee: Lucie Votypkova Components: disk-usage, jobconfighistory Created: 17/Mar/14 1:42 PM Description: Every time I make a configuration change to a job, I get three entries in the Job Config History view: removal of the config for disk-usage plugin actual change I made add of the config of disk-usage again The removed and re-added line looks like this: "disk-usage@0.23"/> Expected: 1. and 3. should not happen.. Project: Jenkins Priority: Minor Reporter: Marc Günther This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
