Wrong first release number when using autoincrement

Rafał Gapski's Avatar

Rafał Gapski

26 Feb, 2018 11:06 AM

Octopus v2018.2.1, scenario and result:
- Test package version: 14.27.2.0223-uat
- Project Settings -> Release Versioning -> Use the version number from included package (Test package)
- Create Release -> Octopus automatically set version to 14.27.2.0223-uat, I change it to 14.27.2.0223-uat.i
- Release created with number 14.27.2.0223-0, instead 14.27.2.0223-uat.0 or 14.27.2.0223-uat
- What's more interesting, second or any next release is created properly, as f.ex. 14.27.2.0223-uat.1

Same bug when using octo.exe to create releases, first release is always wrong.

  1. Support Staff 1 Posted by Michael Compton on 27 Feb, 2018 04:59 AM

    Michael Compton's Avatar

    Hi,

    Sorry you've bumped into this bug.

    I've tested my side and I get the same incorrect behaviour. I've created a github issue so we can track it.

    Michael

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:

»

Already uploaded files

  • chrome_2018-02-26_12-04-22.png 4.2 KB

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

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