Issue Type: Bug Bug
Assignee: Gregory Boissinot
Components: postbuildscript
Created: 17/Mar/14 5:11 PM
Description:

When a Post-build Action is added to a job, its configuration is being updated by user SYSTEM every time the job runs. The updated value is always <time>.

An example of how the job config diff looks like:

36                   <generated>true</generated>
37                   <exposedToEnvironment>false</exposedToEnvironment>
38                   <value>
-39                     <time>1394798774448</time>
+39                     <time>1394800224909</time>
40                     <timezone>Europe/London</timezone>
41                   </value>
42                   <checked>false</checked>

Another example:

39                 <generated>true</generated>
40                  <exposedToEnvironment>false</exposedToEnvironment>
41                  <value>
- 42                    <time>1395074512487</time>
+ 42                    <time>1395074516623</time>
43                    <timezone>Europe/London</timezone>
44                  </value>
45                  <checked>false</checked>
...
56                      <parent class="metadata-tree" reference="../../.."/>
57                      <generated>true</generated>
58                      <exposedToEnvironment>false</exposedToEnvironment>
- 59                      <value>jakub</value>
+ 59                      <value>SYSTEM</value>
60                    </metadata-string>
61                    <metadata-string>
62                      <name>full-name</name>
62                      <name>full-name</name>
64                     <parent class="metadata-tree" reference="../../.."/>
65                     <generated>true</generated>
66                      <exposedToEnvironment>false</exposedToEnvironment>
- 67                      <value>jakub</value>
+ 67                      <value>SYSTEM</value>
68                    </metadata-string>
69                  </children>
70                </metadata-tree>

This causes the "SCM Sync configuration plugin" repository to grow very quickly, and it also makes difficult to work out when a configuration has been changed by a user and not SYSTEM.

  • Is it a bug ?
  • Is it an expected behaviour ? If so how can I disable it ?
  • Is it the PostBuildScriptListener class that's responsible for this ?
    publishers.remove(curPublisher.getClass());
    publishers.add(curPublisher);

We're currently using PostBuildScript version 0.10.

Project: Jenkins
Labels: postbuildscript
Priority: Major Major
Reporter: Jakub Czaplicki
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to