![]() ** unknown exception encountered, please report by visiting Warning: certificate with fingerprint e3:5f:5e:ea:4f:da:ef:a4:0b:4a:bb:00:e8:31:59:de:ce:d0:28:94 not verified (check hostfingerprints or web.cacerts config setting) $ S:\Software\TortoiseHg/hg clone -rev default -noupdate The specific error that I'm getting is listed below : Building remotely on in workspace However, I seem to be running into issues getting this to work when the build is executed by Jenkins. Working on the machine locally, I can clone the repository without issues (this is necessary to get TortoiseHg to preserve the user's password). ![]() The Mercurial repository that I'm using is secured by a self-signed certificate (hosted in IIS). I'm using the Jenkins Mercurial Plugin and pointing to the TortoiseHg installation directory on the slave machine. This solutions has an obvious drawback of discarding any artifacts from previous build, which might save time during the next build and cloning the entire repository from the source control each time instead of just a bunch of changes.įor us I figured we are not running these 'qa' builds too often and the codebase is not too big yet, so we've settled with this workaround for the time being.I've got a build that was previously working fine on the Jenkins Master node that I'm now trying to execute on the Jenkins slave. Do not forget to mark this checkbox in job configuration: There is a plugin, which can make this a part of a build job: Workspace Cleanup Plugin. Simple (although not excatly most efficient) trick that works is wiping the workspace before build. Jenkins developers already know about this issue: Support tags instead of branches hg/hgtags tag points to the "old" revision, it thinks nothing has changed for that tag-branch.
0 Comments
Leave a Reply. |