Looking at the code it appears as though the pipeline was running but when Jenkins was restarted it could not find its data. (https://github.com/jenkinsci/workflow-cps-plugin/blob/a6ac2775ac1767f68ddabcff14364235a61e8bdf/plugin/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java#L659)
Perhaps you had some dirty shutdown of Jenkins and are using a non survivable performace strategy rather than MAX_SURVIVABILITY ? https://www.jenkins.io/doc/book/pipeline/scaling-pipeline/ /James On Monday, July 10, 2023 at 3:04:21 PM UTC+1 [email protected] wrote: > I have a multi-branch pipeline with ‘Discard old Items’ set up to get rid > of old PRs, but I’ve noticed that the directories aren’t all being removed > completely from the controller’s filesystem. These directories have no > confg.xml and they disappear from the UI but it leads to warning messages > in the log saying the config.xml couldn’t be found for the PR job. They all > seem to have the remnants of a single build that wasn’t removed correctly, > which includes a directory named ‘workflow-fallback’. What remains looks > like: > > > $JENKINS_HOME/jobs/<my job>/branches/<old pr>/builds/<build id>/ > > build.xml > > workflow-fallback/ > > <number>.xml > > > This workflow-fallback directory doesn’t currently exist for any build of > a PR that hasn’t been removed, so I’m unsure where it come from. Given the > time stamps of these directories this was happening over a wide span of > versions up to and including 2.401.2. > > > Can anyone explain what’s happening and is there anything I can do to > prevent this? > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/91073651-8d0d-4260-9de2-fac469cbd963n%40googlegroups.com.
