search

OctopusDeploy / Issues

| Public | Bug reports and known issues for Octopus Deploy and all related tools
https://octopus.com
161 stars 20 forks source link

Octopus not deploying correct versions of packages #653

Closed devopsguys closed 10 years ago

devopsguys commented 10 years ago

We are experience a major issue with the deployment of the wrong package versions.

We are creating a release from TeamCity using the Octopus plugin.

In the attached example you can see that the release number generated by TC is 0.40.28.13072. The package version for this release is 0.40.28.13072.

The release number in OD is 0.40.28.13072. However, when the deployment runs OD Tentacle downloads and deploys an old package version .0.40.9.13021

Please can you review as a matter of priority.

octopus-wrong-package

devopsguys commented 10 years ago

The same behaviour described in this issue is also exhibited here. https://github.com/OctopusDeploy/Issues/issues/628

Below are more screenshots showing OD picking the wrong package versions

octopus-wrong-package-1 ![Uploading octopus-wrong-package-2.jpg . . .]()

devopsguys commented 10 years ago

octopus-wrong-package-2

PaulStovell commented 10 years ago

Hi James,

It looks like the deployment is working fine, but on the create release page, Octopus is picking the wrong package to be used as "latest" (although it gets the sort order right on the previous versions dialog). Is that right?

What NuGet server are you using?

Paul

devopsguys commented 10 years ago

Paul, The deployment is also picking up the wrong version. In the example above, 0.40.9.13021 is being deployed, but it should be 0.40.28.13072.

On the create release page, OD is also picking up the wrong version. Its neither using the latest date or highest build number to correctly determine the latest package.

We are using TeamCity as the NuGet Server.

PaulStovell commented 10 years ago

Upgrading to Octopus 2.0.13 seems to have solved this - going to close the issue for now, let me know if it happens again James.

lock[bot] commented 5 years ago

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.