Octopus.time.hour in release versioning is giving UTC timzone instead of server timezone

Legacy Execution
1

Hi,

#{Octopus.time.hour} in release versioning is giving UTC timzone instead of server timezone.

If time in AEST is 10 then #{Octopus.time.hour} is resolving to 00.

Can anyone help to suggest if there is any config for setting timezone for release versioning?

Regards
Kishore

3

Hi Kishore,

Thanks for getting in touch! I’m sorry you’re hitting this strange issue. We expect this special variable for your versioning template to be pulling from your server timezone instead of UTC. When giving it a test in my local instance, the Octopus.Time.Hour variable pulls from the server timezone, so I’m getting the expected behavior.

Which version of Octopus are you running? It’s possible this was a previously known issue which has since been resolved.

I look forward to hearing back!

Best regards,

Kenny

4

Hi Kenneth,

We are using DAAS component provided by octopus

Thanks
Kishore

5

HI,

We are using DAAS service hosted by octopus.

Sorry,I gave wrong info as octopus is installed in our servers.

Can anyone help please?

Regards
Kishore

6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.