Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-22230

PostBuildScript updates job configuration every time job runs

    Details

    • Similar Issues:

      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.

        Attachments

          Activity

          Hide
          jakub Jakub Czaplicki added a comment -

          I was able to reproduce the SYSTEM-job-config-update issue having the following versions:
          Jenkins ver. 1.553
          Post-Build Script Plug-in plugin ver.0.10
          Metadata plugin ver.1.1.0b

          The SYSTEM stopped updating job configuration after updating the Post-Build script plugin to ver.0.16:
          Jenkins ver. 1.553
          Post-Build Script Plug-in plugin ver.0.16
          Metadata plugin ver.1.1.0b

          It seems that the issue has been fixed somewhere between version 0.10 and 0.16.
          Perhaps this change was a fix: https://github.com/jenkinsci/postbuildscript-plugin/commit/b225c1b845bd8b26b153de9fda03dac5c3259b7e ?

          I am going to resolve this ticket now.

          Show
          jakub Jakub Czaplicki added a comment - I was able to reproduce the SYSTEM-job-config-update issue having the following versions: Jenkins ver. 1.553 Post-Build Script Plug-in plugin ver.0.10 Metadata plugin ver.1.1.0b The SYSTEM stopped updating job configuration after updating the Post-Build script plugin to ver.0.16: Jenkins ver. 1.553 Post-Build Script Plug-in plugin ver.0.16 Metadata plugin ver.1.1.0b It seems that the issue has been fixed somewhere between version 0.10 and 0.16. Perhaps this change was a fix: https://github.com/jenkinsci/postbuildscript-plugin/commit/b225c1b845bd8b26b153de9fda03dac5c3259b7e ? I am going to resolve this ticket now.

            People

            • Assignee:
              gbois Gregory Boissinot
              Reporter:
              jakub Jakub Czaplicki
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: