When I reran the pipeline I get the same error.
This was working a week ago. I turned off the pipeline because I did not need to redeploy for a while, and just turned it on. Probably relevant?
Anyway I don't know what to do next.
Thanks for any help
The repo is https://bitbucket.org/methodmaker/snakecharmer
Hi @RogerJParkinson ,
Does the issue still persist? If so, please submit a support case to https://support.atlassian.com so that we can investigate it.
Sorry for any inconvenience caused,
Raul
I solve the problem by creating a new repo an copying the old stuff into there. The problem was caused by my accidently creating a .git dir lower down, ie a repo within a repo (or that's what it lookd like). Understandably there was some confusion. I needed to move the repo anyway so the issue is solved.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I was having the same issue when I try to run the bitbucket pipelines in feature branches specially with force commits. Either I could re run the pipeline or occasionally had to delete and recreate the branch to overcome this. Particular reason for this ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I was having this same issue. For me, I was actually triggering a custom pipeline on a specific commit, that I had since rebased. After supplying the correct commit hash, I was back in business.
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.