We have bitbucket pipelines setup and they worked great for some time now, but for some reason (we haven't modified bitbucket-pipelines.yml file) it stopped working or perhaps to be more precise getting stuck for relatively long on build step.
Repo size is around 250mb and recent commits haven't increased it dramatically (definitely no more than by 1 mb).
The only logged message I see after stopping it:
+ umask 000
+ GIT_LFS_SKIP_SMUDGE=1 git clone --branch="master" --depth 50 https://x-token-auth:$REPOSITORY_OAUTH_ACCESS_TOKEN@bitbucket.org/XXX/XXX.git $BUILD_DIR ; git reset --hard 9c8b615cca0702f8637a1b40c9d843614f832af4 ; git remote set-url origin git@bitbucket.org:XXX/XXX.git
Cloning into '/opt/atlassian/pipelines/agent/build'...
Here is number of attempts to relaunch + previous successful attempt (with timing):
Hi @mch0lic,
It looks like the build is failing to complete the clone. There is some work going on at the moment that is modifying the way clones are handled that might be related.
However, to figure out any more we will have to look at your configuration and repository more in depth. Can I ask you to raise a support ticket at https://support.atlassian.com/.
Cheers,
Tom.
Hi Thomas,
It seems that problem resolved itself. Yesterday I did another commit and all went well. It took ~2 minutes instead of 1 that typically takes, but at least it worked.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.