Invalid version string error

basil_m_maypa · 13 August 2014 09:06

Hi,

I created a Release for one of the Tentacles. When I edited the Release entry, I changed the version from “0.0.1” to “VRTVW 0.0.1”. When I view the Release, it returns an error and I am also unable to edit the entry to revert to the old value.

Vanessa_Love · 14 August 2014 04:00

Hi Basil,

Thanks for getting in touch! We recently fixed this issue in a recent release. You can now view and delete bad release numbers.
If you are not able to upgrade you will have to delete the release from the DB itself.

Let me know how you go.
Vanessa

basil_m_maypa · 14 August 2014 06:15

Hi Vanessa,

Thank you for the response. We’re currently using Octopus Deploy 2.5.4.280. What is the release version that has the fix?
Can you also provide me a link or the steps to delete the release from the DB?

Basil

basil_m_maypa · 14 August 2014 06:20

Vanessa,

I also tried using the approach in this link (http://octopusdeploy.com/blog/deleting-releases-via-command-line), however, the Octo.exe version is not compatible with our Octopus server. Is my assumption correct that this is the DB delete approach?

Basil

Vanessa_Love · 14 August 2014 07:23

Hi Basil,

Yeah the fix was part of 2.5.5.
The delete-releases command still works. Octo.exe is a separate install from Octopus
You can download it here: http://octopusdeploy.com/downloads if it is out of date. However the issue remains with the latest octo.exe it throws the error of a bad release number.

So this leaves you with actually opening up the RavenDB browser "Octopus Manager -> Browse RavenDB"
Under Documents you can find Releases. We then need to know which ID to delete.
Under Audit back in the Configuration section of Octopus Server you can mouseover the release number for when the release was created - it should give a number such as Release-126
Then that row can be deleted from the Raven DB browser.

As you can see a bit convoluted to do manually, thus why it was fixed in 2.5.5.
Vanessa

ianpaullin · 25 August 2014 19:02

Hi Vanessa,

This technique of deleting the offending release worked for us. Thanks so much!

Ian

dalmiro_granias_notStaff · 1 September 2014 20:39

Hi Vanessa,

Wouldnt it be safer to add a validation to that field before the users hit save? I just got the same issue as Ian and had to go to Raven to Fix it up.

Thx,

Dalmiro.

Vanessa_Love · 2 September 2014 00:07

Hi Dalmiro,

That was part of the 2.5.5 fix (see screenshot)

Thanks!
Vanessa