You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are you a customer of Octopus Deploy? Don't raise the issue here. Please contact our support team so we can triage your issue, making sure it's handled appropriately.
Prerequisites
[x ] I have verified the problem exists in the latest version
[ x] I have searched open and closed issues to make sure it isn't already reported
[ x] I have written a descriptive issue title
[ x] I have linked the original source of this report
I have tagged the issue appropriately (area/*, kind/bug, tag/regression?)
The bug
From support email:
Octopus Version: 2018.7.13
I had mistakenly set a project release version template to:
I also had a scheduled trigger that creates a release (not sure what happens if you create the release manually). When it triggered, it looked like it did start deploying to tenants, but the release was named "2018.09.10.#{Octopus.Date.Hour}".This blew up the dashboard with an error about parsing the variables. I also could not manually get into the release to delete it, with a similar error.
As a quick workaround, I had to go into SQL and manually edit the release name and then restart the Octopus service to get back in.
What I expected to happen
When an invalid replacement (Octopus.Date.Hour) is found don't crash the dashboard.
Steps to reproduce
Set the release version template to #{Octopus.Date.Year}.#{Octopus.Date.Month}.#{Octopus.Date.Day}.#{Octopus.Date.Hour} and manually create the release.
The text was updated successfully, but these errors were encountered:
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.
Are you a customer of Octopus Deploy? Don't raise the issue here. Please contact our support team so we can triage your issue, making sure it's handled appropriately.
Prerequisites
The bug
From support email:
Octopus Version: 2018.7.13
I had mistakenly set a project release version template to:
#{Octopus.Date.Year}.#{Octopus.Date.Month}.#{Octopus.Date.Day}.#{Octopus.Date.Hour}
Instead of:
#{Octopus.Date.Year}.#{Octopus.Date.Month}.#{Octopus.Date.Day}.#{Octopus.Time.Hour}
I also had a scheduled trigger that creates a release (not sure what happens if you create the release manually). When it triggered, it looked like it did start deploying to tenants, but the release was named "2018.09.10.#{Octopus.Date.Hour}".This blew up the dashboard with an error about parsing the variables. I also could not manually get into the release to delete it, with a similar error.
As a quick workaround, I had to go into SQL and manually edit the release name and then restart the Octopus service to get back in.
What I expected to happen
When an invalid replacement (Octopus.Date.Hour) is found don't crash the dashboard.
Steps to reproduce
Set the release version template to #{Octopus.Date.Year}.#{Octopus.Date.Month}.#{Octopus.Date.Day}.#{Octopus.Date.Hour} and manually create the release.
The text was updated successfully, but these errors were encountered: