Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
Jenkins ver. 2.101
Description
A multibranch job that pulls from mercurial deletes all branches when that repository goes down. This was discovered during Bitbucket's outage going on today, and I lost all the branch build history.
Steps to reproduce:
- Create a local mercurial repo with below basic Jenkinsfile and publish using hg serve
- Start vanilla weekly docker image
- Install multibranch, mercurial
- Create multibranch job pointing at that repo, let it scan and build default branch
- Kill hg serve
- Run "Scan Multibranch Pipeline Now", all branches get deleted
Basic jenkinsfile
pipeline { agent any stages { stage("Build Data") { steps { sh 'echo yay' } } } }
Logs
[Tue Jan 09 17:19:31 UTC 2018] Starting branch indexing... Acquired master cache lock. [D69ADC747155FE53F1452F758ACEC24C520106F9-lblakey-ws1] $ hg pull pulling from http://myWorkstation:8000/ abort: error: Connection refused ERROR: Failed to update /var/jenkins_home/hgcache/D69ADC747155FE53F1452F758ACEC24C520106F9-myWorkstation Master cache lock released. ERROR: Could not use caches, not fetching branch heads [Tue Jan 09 17:19:31 UTC 2018] Finished branch indexing. Indexing took 66 ms Evaluating orphaned items in test Will remove default Finished: SUCCESS
Attachments
Issue Links
- is duplicated by
-
JENKINS-62486 Multibranch jobs rebuild and lose build history when source control is down
-
- Resolved
-
- links to
Recently I've also encountered this with a local mercurial server (mercurial-scm) not being available. Wiped all builds and branches, very problematic! Note that in my case the account used to access mercurial was (temporarily) blocked, resulting in the same behaviour.
Jenkins v2.107.3 (current LTS)
Mercurial plugin v2.3
SCM API plugin 2.2.7