-
Improvement
-
Resolution: Unresolved
-
Major
-
Linux Suse 11
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
Sascha Vujevic
created issue -
Sascha Vujevic
made changes -
| Description |
Original:
If a user edits a job-configuration he will se also all changes made by use plugins, if before this change an update on plugins was made. It is not clearly visible who made what changes and which are made by an update of plugins. It would be better, if the automated changes by updated of plugins where 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: {code}<spec>0 21 * * 1-6</spec>{code} All other changes came from an update of *maven2-modulset plugin*. I hope a was able to make the problem transparent. |
New:
If a user edits a job-configuration he will se also all changes made by use plugins, if before this change an update on plugins was made. It is not clearly visible who made what changes and which are made by an update of plugins. It would be better, if the automated changes by updated of plugins where 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: {code}<spec>0 21 * * 1-6</spec>{code} All other changes came from an update of *maven2-modulset plugin*. I hope a was able to make the problem transparent. Thank you for your help and support. |
Sascha Vujevic
made changes -
| Description |
Original:
If a user edits a job-configuration he will se also all changes made by use plugins, if before this change an update on plugins was made. It is not clearly visible who made what changes and which are made by an update of plugins. It would be better, if the automated changes by updated of plugins where 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: {code}<spec>0 21 * * 1-6</spec>{code} All other changes came from an update of *maven2-modulset plugin*. I hope a was able to make the problem transparent. Thank you for your help and support. |
New:
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: {code}<spec>0 21 * * 1-6</spec>{code} All other changes came from an update of *maven2-modulset plugin*. I hope a was able to make the problem transparent. Thank you for your help and support. |
Sascha Vujevic
made changes -
| Description |
Original:
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: {code}<spec>0 21 * * 1-6</spec>{code} All other changes came from an update of *maven2-modulset plugin*. I hope a was able to make the problem transparent. Thank you for your help and support. |
New:
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: {code}<spec>0 21 * * 1-6</spec>{code} 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. |
| Component/s | New: jobconfighistory [ 15683 ] | |
| Component/s | Original: core [ 15593 ] |
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: 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 
| Workflow | Original: JNJira [ 151333 ] | New: JNJira + In-Review [ 177922 ] |
Not a core issue.