Package not specified error when creating a release

[slewis74]

When creating a release via octo.exe an error can occur where the package id isn't determined correctly for a step. The error surfaces as

No package version was specified for step : package

I was able to reproduce the issue, but only once. When I tried a second time it worked. As the attached screenshot show, when it worked the second time the release plan from the server had included the Package Name, which is presumably related to the root cause.

Customers have reported the issue when using the TFS/VSTS extension. I was able to repro on the command line so do not think the extension is the cause.

Screen capture

Affected versions

2018.8.x

Octopus Server:

Links

https://secure.helpscout.net/conversation/
https://secure.helpscout.net/conversation/688293304/33763?folderId=909887

[slewis74]

We now have an accurate repro for this issue. It occurs with earlier versions of Octo.exe calling the new server, due to an edge case we had not foreseen.

In my earlier testing, from the attached screenshot, I realised that the first run I did was using exe compiled against an earlier version of the code (even though I had the new code at the time). I'd run in debug then and so new binaries and it worked as expected every time after that. Rolled the code back and could repro every time.

So the fix is we need to update the build server extensions to have the new octo.exe

[slewis74]

TeamCity extension 4.42.0
VSTS extension 3.0.184
both released, which should address this issue.

[lock]

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.