Packages created and pushed from TeamCity to Octopus Deploy contain partial of version number in its ID

[Ge]

Hello,

We are using “Octopus Deploy integration” plug-in in our TeamCity.

In one of our project, we have “OctopusDeploy: Create and Push Packages” build step to push the package from TeamCity to Octopus.

The package path patterns is:
./** => PackageName.%build.number%.zip

The value for %build.number% is 1.3.0.9.11. We expect to see PackageName.1.3.0.9.11

However, the package ID shown in the Octopus built-in package repository as “PackageName.1” and the version is “3.0.9.11”

When we change the package path patterns to use underscore, Octopus Deploy is able to pick up the package name and version info correctly.
“./** => PackageName_%build.number%.zip”

I don’t know why Octopus Deploy parses partial of the version number as the package ID. Any help will be appreciated!

Thanks,

Ge

Octopus version: v2018.3.12
TeamCity version: 2017.2.3
Octopus Deploy integration plug-in version: 4.31.1

[benpearce]

Hi Ge,

Thanks for getting touch.

It appears that the version number you are using contains too many parts. Octopus works best when SemVer patterns are followed for versioning your packages. There is a documentation page on versioning that will be helpful.

SemVer version numbers need to be in the format MAJOR.MINOR.PATCH-prereleasetag+metadata. So, your version number will need to remove two parts, or change the last two numbers to a prerelase tag or metadata.

I also used this web site to test the version number strings.

Hopefully this helps you out.

Regards
Ben

[Ge]

Thanks for the clarification!