"Reference not in tree" when running pipeline on commit manually

[Jozz Scott]

I have successfully run a pipeline on a branch automatically using the 'branches' section of pipelines.yml.

I have now edited the yml file so that I can run the same steps manually using the 'custom' section.

When I create a new commit and try to run the pipeline manually, the pipeline runs but has different results (it fails, when the code passes when run automatically).

The codebase for the commits are identical, as are the steps for the custom and branching sections of the pipelines.yml 

I have checked the output of the pipeline for both cases carefully and notice this difference in the way the repo is cloned.

The automatically run pipeline that works successfully:

git clone --branch="BRANCHNAME" --depth 50 https://x-token-auth:$AUTH_TOKEN@bitbucket.org/REPO

With the result:

HEAD is now at COMMIT_HASH_GOES_HERE Testing successful

The manual run pipeline that does not:

git clone --depth 50 https://x-token-auth:$AUTH_TOKEN@bitbucket.org/REPO

With the result:

fatal: reference is not a tree: COMMIT_HASH_GOES_HERE

As far as I can tell, this results in the commit I actually want to manually test not being checked out - and so the codebase is different to what i'm actually trying to run through the pipeline and so it ends up failing.

Since I do not have control over this cloning command, i'm not really sure how to resolve this.

Has anyone else observed this behaviour or know of a workaround?

[Tom Bradshaw · Accepted solution]

Hi @Jon Scott,

We noticed this problem and have just put out a fix for it. If this continues to be a problem please raise a support ticket at https://support.atlassian.com so we can continue investigating this.

Cheers,

Tom