Hmm… nothing has changed in the mercurial support… however… I suspect this issue was there already. I’m not sure we actually support mecurial subrepositories… the export is done on the agent… which just has a clone of the server’s clone of the original repo. The agent would not have the credentials for the subrepos, unless it’s on the same machine as the server and using the same mecurial.ini.
We’ll need to investigate this some more… but I have to say that hg subrepos, git submodules and svn externals are causing lots of issues… mostly with authentication.
What I’ve do, 1- Look at the continua service to see what user its using. 2- Loged on this user account and setup the mercurial.ini to auto logon to both my subrepos. 3- Logged off, accessed the continua ci interface and start a build.
Same error happens. I will try to reebot the continua ci services, just to see if nothing was cached.