Package version not expanded when variable stored in git

[magnus.bengtsson]

We recently enabled version control (git) for the variables stored in Octopus.

We have diffrent packages we deploy depending on the channel selected on the deployment screen.

Before moving the variables to git, upon selecting the different channels the package name and number would update accordingly.

After the moving the variable to git, the #{WebsitePackageId} is not expanded nor is the latest version showing.

If clicking on the “select version” version button. There are no packages showing.

Again the #{WebsitePackageId} variable is not expended as it should.

If we enter the version manually in “Enter a version” field it is working as expected.

Is this a bug or are we missing something obvious?

[Kenneth_Bates]

Hi Magnus,

Thank you for getting in touch. I appreciate the report of this issue, though my apologies for the confusion it has caused. Great to hear you have a manageable workaround to this issue. I’ve been able to reproduce this and raised a bug report at the following link that you can track.

Version controlled variable bound to package id doesn't populate on release creation page

If you have any other questions or concerns in the future, please don’t hesitate to shout out.

Best regards,

Kenny