I'm having troubles configuring Bitbucket HTTPS repositories at the moment.
It looks like there is some mixed up logic in the repo user name or a mismatch between PF\Continua\..\hg.exe and PF\Mecurial\ cacert. Ideas?
Running C:\Program Files\VSoft Technologies\ContinuaCI\Server\hg\hg.exe failed with return code 255 and error output abort: could not find web.cacerts: C:\Program Files\Mercurial\cacert.pem (Args were : status -R "https://Jamie_Clayton:XXXXXXX@bitbucket.org/jenasysdesign/iims" --config ui.username=Continua)
I did try an "reset" the repo, just in-case, but this one is a particularly large one that seems to trigger timeouts. Here is the event log for the repo.
Repository @link(2002, 0ab2db44-76b7-4abf-8a8b-0e260bb4df99)[Iims-Bitbucket] cannot be initialised: Running C:\Program Files\Mercurial\hg.exe failed with return code -1 and error output The process timed out or was forcibly terminated. (Args were : clone --noupdate https://Jamie_Clayton:XXXXXXX@bitbucket.org/jenasysdesign/iims C:\Continua\Rc\0ab2db44 --config ui.username=Continua)
This event has been reported 3 times.
I just wonder if this is some left over logic from the previous Beta's and my require a server delete of the folder \\Continua_WS\Repos\STUCKREPOSLUG
Looks like we missed this in our installer. In the Continua CI\Server\hg folder, edit the hg.ini file and change that to point to the correct path (ie continua’s \hg folder). The reason we missed this is we all have hg installed on our dev machines already, with the file in that default location! (doh!).
With the second error, my guess is it’s busy prompting you for input. If you make the ini file edit this should be resolved. We’re running build now and will test the installer once it’s done. Hopefully we’ll have an update out tonight.