We have a pipeline script executing for our jobs, where we set job parameters. For example, we configure the job to be parameterized and we set a cron to execute the job at some specific times.

When we first trigger the job, the pipeline executes and all is good. However, we've noticed for the past few months that the we regularly find that the job has lots its configuration (no longer parameterized, no cron set anymore), and doesn't get triggered anymore as a consequence. We're not exactly sure when it happens but it seems to be at least when there's a jenkins restart. This was not happening before and this suggest a regression in Jenkins itself.

Example of our jenkinsfile: https://github.com/xwiki/xwiki-platform/blob/04f457ed6fd272c98f77a5b2b814a647f2857a52/JenkinsfileEnvironmentTests

Example of job using this jenkinsfile: https://ci.xwiki.org/job/XWiki%20Environment%20Tests/job/xwiki-platform/job/master/