Can't Initiate a New Build After Test Failure When Using .yml File

dave's Avatar

dave

07 Apr, 2015 06:04 PM

Here's the scenario:
- Increment the version number in a .yml file used for settings in a dev branch.
- Merge the dev branch with master to trigger a build.
- AppVeyor picks up on the merge, initiates the build, then fails on one or more tests.
- Fix tests in master branch and push a new commit.
- AppVeyor sees the new commit but won't build because of duplicate version numbers.

I can't seem to figure out how to get AppVeyor to rebuild for the version number in the .yml file. I keep getting the message "Build version A.B.C.D already exists." I've tried changing the build number in the project settings, but that's ignored (as it should be) since I'm using a .yml file. I don't really want to increment my version in the .yml file because it's the actual version. Otherwise I'll have gaps in my versions every time my build fails a test.

Is there any way to "forget" the failed build?

  1. Support Staff 1 Posted by Feodor Fitsner on 07 Apr, 2015 06:43 PM

    Feodor Fitsner's Avatar

    I'd change current build version to something like {version}-{timestamp}-failed on build failure even, so current build version could be reused. For example:

    on_failure:
      - ps: Update-AppveyorBuild -Version "$($env:appveyor_build_version)-$(Get-Date -format HHmmss)-failed"
    
  2. 2 Posted by dave on 07 Apr, 2015 07:19 PM

    dave's Avatar

    That works great! Thanks as always for your fantastic support.

  3. dave closed this discussion on 26 Feb, 2018 09:00 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac