Details
-
Bug
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Duplicate
-
None
-
CentOS 7 x64
Jenkins 2.222.3
Description
We used Mercurial (hg) for source control and most of our Jenkins jobs are multi-branch jobs. They all have skipDefaultCheckout set to false and have a build step that calls `deleteDir` and then `checkout scm` (because it doesn't appear as though default checkout can do a clean checkout.)
When our version control server is goes down and then comes back up (like a reboot), all the multibranch builds are triggered even though nothing in the code has changed. Additionally, the lose all their build history
Attachments
Issue Links
- duplicates
-
JENKINS-48867 Mercurial multibranch pipeline deletes all branches when repository is down
-
- Resolved
-
Some more details. We're no longer deleting the directory but instead doing a clean checkout. The problem still exists.
It appears as though Jenkins will delete all known details of branches in the time our source control server is down.
Here's a relevant log:
I would think that the unsuccessful response would cause the job to fail, thereby avoiding branch indexing and removal of branches