Currently, Pipelines fails when it is applied to a Mercurial repo that depends on subrepos which are cloned over SSH.
I have a simple Mecurial repository A that relies on Mercurial repository B. A contains a
.hgsub file with a line on the following form:
B = ssh://firstname.lastname@example.org/karltk/B
When using Pipelines to build repo A, the build stops on checkout, complaining about
ssh not being found:
+ hg clone -r "42e8c457a6cabf66c55b8e9a864620903d46ddf1" https://x-token-auth:$AUTH_TOKEN@bitbucket.org/karltk/A . adding changesets adding manifests adding file changes added 5 changesets with 7 changes to 4 files updating to branch default remote: /bin/sh: remote: ssh: not found remote: abort: no suitable response from remote hg!
atlassian/agent-setup-hg:latest image appears to contain the machinery used for the checkout/cloning stage. As you appear to only clone Mercurial repos over HTTPS, the "missing"
ssh isn't really a surprise...
Pipelines appears to be very much tied to Bitbucket, so don't expect you to fetch "foreign" repos hosted elsewhere as part of my build. Hence, I'm not asking for a full SSH-keys solution, as is common with other CI services. Just something that works internally with Bitbucket would be acceptable.
That being said, what I'm really after is a way to compose a Pipelines build out of several Mercurial repos, all hosted on Bitbucket; another mechanism than Mercurial subrepos would do fine, as well.