Skip to content
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

PR builds fails on second Appveyor build, for merge-commit #737

Closed
reisenberger opened this issue Dec 27, 2019 · 3 comments
Closed

PR builds fails on second Appveyor build, for merge-commit #737

reisenberger opened this issue Dec 27, 2019 · 3 comments
Labels

Comments

@reisenberger
Copy link
Member

Summary:

A PR typically builds twice on AppVeyor - for the branch and then the merge-commit of the PR. The second build often fails with:

========================================
__UpdateAppVeyorBuildNumber
========================================
Executing task: __UpdateAppVeyorBuildNumber
Build with specified version already exists.

The cake build script intends to set the build number from the git metadata FullSemVer and this repeats for the second build.

More analysis at: Polly-Contrib/Simmy#56

Expected behavior:

Both the branch-build and the merge-commit-build of a PR pass.

Actual behaviour:

The merge-commit-build of a PR often fails with above error, even if branch build has passed.

Steps / Code to reproduce the problem:

Make a PR against any non-master branch, without changing gitversionconfig.yml

@reisenberger
Copy link
Member Author

Fixed by #738

@martincostello
Copy link
Member

This is still happening.

@martincostello martincostello added the help wanted A change up for grabs for contributions from the community label Jan 17, 2022
@martincostello
Copy link
Member

I think #921 resolved this once and for all.

@martincostello martincostello removed the help wanted A change up for grabs for contributions from the community label Feb 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants