Changing the build version number doesn't seem to have any effect
My latest build was v1.6.42. Now that my project has moved to 1.8, I changed the "Build version format" to `1.8.{build}` and the "Next build number" to `1`. When I save these changes and create a new build, it refuses to start because it claims I already have a build called v1.6.1. When a new build is triggered by a commit/merge from Github, the title/date in the project/history page show me the recent commit but when I click on it for details, I see the old build results from a few months ago (as in: it refers to the actual v1.6.1 build).
What gives?
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
Support Staff 1 Posted by Feodor Fitsner on 05 Aug, 2015 10:07 PM
Do you have version format defined in appveyor.yml?
- Feodor
2 Posted by Jeroen Vannevel on 05 Aug, 2015 10:10 PM
Ahh of course. I had the appveyor.yml file in my source control but forgot to disable it in the UI.
Thanks, that solved it.
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:58 AM.