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/d64c53d6-3db4-4f9b-93bc-d2460e36d499n%40googlegroups.com.
