We use the Job Configuration History plugin to record the modification history of Pipleline. We found that the configuration of the job has been modified by the system.
The version of Job Configuration History plugin is 1302.va_65b_ccb_fde71, and the version of jenkins is 2.492.1.
The problem is described as follows：
The configuration of the job was modified by the user on 2025-06-13_16-34-59.
Job started by timer on 2025-06-13_22-41-00.
The configuration of this job was modified by system at this time.
We want to know which plugin caused the configuration modification of the job, is it the Job Configuration History plugin?
Thank you very much in advance.
Best regards,
Hesper
Hi Winter,
Thanks for your reply.
The default value of the issueKeyList parameter is periodically changed, and this job is usually triggered by a timer.
Yes, the user has defined parameters inside the Jenkinsfile. Is it because the user only modified the parameters configuration of the interface without modifying the parameters inside the Jenkinsfile, which caused this problem?
yes.
It’s a bit strange to define parameters inside the script when you define the script inline in the job and don’t load it from an SCM.
Note that changes to parameters defined in the script are applied after job execution and not when the job starts.
Dear Winter,
I have reproduced this issue, so the problem that troubled me has been solved. I also learned new knowledge about Jenkins pipeline.
Thank you very much for your reply.
