![]() ![]() NOTE: You may also have to remove the mercurial_keyring line from mercurial.ini. The only way I was able to figure out how to get the server to remember the password (and work with polling) in my setup was to specify it manually in \mercurial.ini. See How do you specify authentication information for Mercurial as part of Jenkins? (mercurial_keyring) ![]() Polling Solution: (The solution above does not seem to work with the Jenkins polling functionality, so we're left with the solution below). It may already have been terminated.' error. It seems that once the repository is available on the slave, it's able to get past the 'A specified logon session does not exist. The fix to this turns out to be to manually clone the repository on the slave at the workspace location (where it would normally end up). Non-Polling Solution: (Useful if you're not doing polling of the repository to trigger builds) It may already have been terminated.')ĮRROR: Failed to clone Can anyone offer suggestions on what I can do to get past this? Pywintypes.error: (1312, 'CredRead', 'A specified logon session does not exist. ![]() ** Mercurial Distributed SCM (version 2.1.2)įile "mercurial\dispatch.pyo", line 27, in runįile "mercurial\dispatch.pyo", line 64, in dispatchįile "mercurial\dispatch.pyo", line 87, in _runcatchįile "mercurial\dispatch.pyo", line 685, in _dispatchįile "mercurial\dispatch.pyo", line 467, in runcommandįile "mercurial\dispatch.pyo", line 739, in _runcommandįile "mercurial\dispatch.pyo", line 693, in checkargsįile "mercurial\dispatch.pyo", line 682, in įile "mercurial\util.pyo", line 456, in checkįile "mercurial\commands.pyo", line 1157, in cloneįile "mercurial\hg.pyo", line 250, in cloneįile "mercurial\hg.pyo", line 93, in repositoryįile "mercurial\httprepo.pyo", line 236, in instanceįile "mercurial\httprepo.pyo", line 57, in _fetchcapsįile "mercurial\httprepo.pyo", line 169, in _callįile "mercurial\httprepo.pyo", line 117, in _callstreamįile "urllib2.pyo", line 510, in http_responseįile "urllib2.pyo", line 369, in _call_chainįile "urllib2.pyo", line 864, in http_error_401įile "mercurial\url.pyo", line 429, in http_error_auth_reqedįile "hgext\mercurial_keyring.pyo", line 332, in basic_http_error_auth_reqedįile "urllib2.pyo", line 842, in http_error_auth_reqedįile "urllib2.pyo", line 845, in retry_http_basic_authįile "hgext\mercurial_keyring.pyo", line 326, in find_user_passwordįile "hgext\mercurial_keyring.pyo", line 177, in find_authįile "hgext\mercurial_keyring.pyo", line 60, in get_http_passwordįile "keyring\core.pyo", line 37, in get_passwordįile "keyring\backend.pyo", line 560, in get_passwordįile "keyring\backend.pyo", line 573, in _get_password ** 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. 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |