Hi,
I am in Amsterdam, UTC+2 and my server is on UTC. When I want to schedule a deployment at 15:59 my time, I get the suggestion of 16:59 server time, where the server is at 13:59 UTC!
So when I want to run the deployment at 20:00 my time, I set the schedule for 18:00UTC. It then shows that the deployment is scheduled for 6:00PM, while that is 18:00 it is confusing. In OttoFMS it shows 18:00 so there it shows correctly.
Hey Ruben,
The suggestion for the time to run the deployment defaults to 1 hour in the future of your device time. OttoDeploy doesn’t know what timezone the server is on. I’ll take a look at the differing representation between 24 hour and 12 hour time. It sounds like you’re setting the right times though!
-Kyle
That is confusing and will not work correctly if I use the suggested time. I end up with a 2hour difference.
I would expect that I either have to enter my time and the system translates that to server time (which would be my preference) or gives the option to either enter my time or server time
Best, Ruben
Hey Ruben,
OttoDeploy 2.2.3 was just released, which includes a fix that makes that confirm information match the schedule information. There’s still an issue where the time selection is showing 12 hour time instead of 24 hour time, but the value it displays is correctly in 24 hour time below the selector (I know this is annoying, there’s a strange dependency issue that’s preventing an easy fix right now).
Thanks for the report!
-Kyle
Thanks for the follow up!
1 Like