-
Notifications
You must be signed in to change notification settings - Fork 652
Cannot generate version number on BitBucket Cloud Pipelines #3057
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Perhaps a duplicate of #2900? |
I don't believe so - the issue you linked to says that the error they experience occurs on With those changes, my Pipelines build step looks like this:
and the output that it produces is:
|
I've queried on the Atlassian community boards, and their suggestion was to do a full clone of the repo, and that does change the output a little (I've snipped off the commit graph for now):
Of which, the following 4 lines are new:
|
I'm not sure what's going on. Are you able to reproduce this in a local clone of a public repository, @davidkeaveny? |
I forked GitVersion and imported that repository into BitBucket Cloud, then created a minimal pipeline, and the wretched thing ran out of the box! Using the exact same contents for |
In the end, I exported my |
Looks like I got ahead of myself - as soon as I created a feature branch from So to summarise, when building on Atlassian BitBucket Cloud Pipelines and
|
Would it help if I implemented a build agent for BitBucket Pipelines? That might help work around whatever limitation is causing this issue; I've got an initial version in https://github.com/davidkeaveny/GitVersion/tree/feature/add-bitbucket-build-agent. |
Closed by #3069 |
🎉 This issue has been resolved in version 5.10.0 🎉 Your GitReleaseManager bot 📦🚀 |
I am using Atlassian's BitBucket Cloud edition and their Pipelines CI service to build a new application (so we haven't done our first merge back to
master
yet). When I run GitVersion to calculate the version number, the pipeline step fails with the messageGitversion could not determine which branch to treat as the development branch (default is 'develop') nor release-able branch (default is 'main' or 'master'), either locally or remotely. Ensure the local clone and checkout match the requirements or considering using 'GitVersion Dynamic Repositories'
.Expected Behavior
The pipeline step should generate the calculated version number.
Actual Behavior
The pipeline step is erroring with the following exception:
Steps to Reproduce
I am using the following configuration for Pipelines:
If I run
dotnet-gitversion
locally on the repo, then the version number is calculated as expected, so I believe that myGitVersion.yml
is good.The complete output from the build server is as follows:
The text was updated successfully, but these errors were encountered: