We have a parent repository and child repository in Bitbucket Mercurial cloud.
When push to mercurial happens, the parent pipeline gets triggered, but the child repositories are not able to clone. Kindly let us know if this is supported
The log shows
+ docker run -t --entrypoint=/bin/bash --memory=4096m -e BUILD_DIR=/opt/atlassian/pipelines/agent/build -v /tmp/bashScript6789261114367880226.sh:/tmp/bashScript6789261114367880226.sh:ro -v build-volume-a42e25d5-c3db-41d8-9b62-314f0781dfbd:/opt/atlassian/pipelines:rw -w /opt/atlassian/pipelines/agent/build --label com.atlassian.pipelines.agent="2ec0cd73b24c" "atlassian/pipelines-dvcstools:latest" -i /tmp/bashScript6789261114367880226.sh
WARNING: Your kernel does not support swap limit capabilities, memory limited without swap.
+ umask 000Completed at 2016-12-22T07:26:13Z+
hg clone -r "a64a61840842739387d18f5d5f66877f55c22dbf" https://x-token-auth:$AUTH_TOKEN@bitbucket.org/xxxxxx-parent .
adding changesetsadding manifestsadding file changes
added 384 changesets with 402 changes to 10 files
updating to branch AHS
http authorization required for https://bitbucket.org/xxxx/child
realm: Bitbucket.org HTTPuser: x-token-authpassword:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.