Create Release does not pick latest feed version

Legacy Uncategorised
1

I publish feeds based on the date with an automated build.
2014.1.8.$(revisionnumber)

2014.1.8.7 worked fine, then the next successful build 2014.1.8.11 did not chose the correct version.
@@@
Pushing Database 2014.1.8.11 to ‘http://(my_nuget_server).azurewebsites.net/’…
Your package was pushed.
@@@

@@@
Release plan for release: 2014.1.8.7
Steps:

Name Version Source

1 Deploy Database 2014.1.8.7 Latest available in NuGet repository

Creating release…
Error from Octopus server (HTTP 400): There was a problem with your request.

  • Release ‘2014.1.8.7’ already exists for this project. Please use a different version, or look at using a mask to auto-increment the number.
    @@@

Using octo.exe

I thought it was an issue with the command line but even on the server interface it will not automatically pick up the latest version it defaults to 2014.1.8.7

Using Command Line Tool 2.0.8.22
And Server Version 2.0.8.977

2

Thanks for the report. I believe we’ve tracked this one down - are you using Team City 8?

Thanks,
Nick

3

No I am using octopack and powershell with octo.exe

Sent from my Nokia 820 Windows Phone

4

No I am using octopack and powershell with octo.exe

Sent from my Nokia 820 Windows Phone

5

No I am using octopack and powershell with octo.exe

Sent from my Nokia 820 Windows Phone

6

No I am using octopack and powershell with octo.exe

Sent from my Nokia 820 Windows Phone

7

No I am using octopack and powershell with octo.exe

Sent from my Nokia 820 Windows Phone

8

Thanks for the follow-up; where are your Octopus NuGet packages hosted?

Cheers,
Nick

9

On an Azure website hosted nuget repo created by the NuGet.Server package

Testing the repo on the server shows the new version but it won’t choose it as the new release version

Sent from my Nokia 820 Windows Phone

10

Any idea when a fix for this will be available? At this point I can only create 9 releases per day.

11

I’ll see if I can get one out today - given the variety of NuGet servers out there it would be good to test our fix in your specific case. Thanks!