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

Job-Configuration - Updates on used plugins and their changes are logged under the last user, who changed the job-configuration

      If a user edits a job-configuration he will see all changes made by used plugins too, if an update on plugins was made before.
      It is not transparent who made that changes and which are made by an update of plugins.

      It would be better, if the automated changes on updates of plugins were logged seperatly by a technical user.

      I have attached an example where the only change that was made by the user on the job-configuration was:

      <spec>0 21 * * 1-6</spec>

      All other changes came from an update of maven2-modulset plugin.

      I hope i was able to make the problem more transparent.

      Thank you for your help and support.

          [JENKINS-19814] Job-Configuration - Updates on used plugins and their changes are logged under the last user, who changed the job-configuration

          Daniel Beck added a comment -

          Not a core issue.

          Daniel Beck added a comment - Not a core issue.

          Sorry @Ddanielbeck but I think it is a core issue.
          If the core would call a save listener after upgrade, the jobconfighistory plugin would create a correct change entry for the system user.

          Stefan Brausch added a comment - Sorry @Ddanielbeck but I think it is a core issue. If the core would call a save listener after upgrade, the jobconfighistory plugin would create a correct change entry for the system user.

          Daniel Beck added a comment -

          Stefan: Job.doConfigSubmit() calls save() calls SaveableListener.fireOnChange(...), all in the context of the user. No ACL.impersonate(SYSTEM) anywhere.

          And I hope you're not suggesting that Jenkins should re-save all job configs whenever any plugin is updated just to record the changed version.

          Daniel Beck added a comment - Stefan: Job.doConfigSubmit() calls save() calls SaveableListener.fireOnChange(...) , all in the context of the user. No ACL.impersonate(SYSTEM) anywhere. And I hope you're not suggesting that Jenkins should re-save all job configs whenever any plugin is updated just to record the changed version.

          You are right Daniel. This change wasn't saved before.
          Then I see no easy chance to report it correctly

          Stefan Brausch added a comment - You are right Daniel. This change wasn't saved before. Then I see no easy chance to report it correctly

            Unassigned Unassigned
            georgestark Sascha Vujevic
            Votes:
            3 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: