We are running Octopus version 3.0.12.2366
When we schedule a release it is deploying the release immediately no matter what the schedule date or time is.
e.g. Today = 15/09/2015 14:50
Schedule date = 2015-09-16
Schedule time = 07:30 AM
Hi,
Found the issue. Octopus shows date default setting to 2015-09-15 but the date it does accept is 2015/09/15. Any way we can change the default settings?
I’m not able to reproduce the issue you are mentioning. It works as expected for me with both yyyy-mm-dd and yyyy/mm/dd formats. Would you mind giving us more specific test data? for example of many hours/days ahead did you set the deployment to when you saw that it was incorrectly getting triggered immediately.
Here’s my step by step action when I get to the “Deploy Release” screen:
I select radio button on “Later”
[cid:image005.jpg@01D0F16B.AEE39710]
I place my cursor on the date field (which has todays date on it)
I then delete the date and change it to tomorrows date
e.g 2015-09-17 change to 2015-09-18
[cid:image009.jpg@01D0F16B.AEE39710]
NOTE: “The Deployment will start in approximate…” information disappears and does not re-appear. I have to start the release again to get it back
When I click on the Deploy release then the release happens immediately
I have just ran a test where I don’t delete the date but highlight/replace the number and the “The Deployment will start in approximate…” information does appear.
Regards
Binh Au
Senior Release Analyst, Service Delivery
ILS Commercial Delivery & Technology
Thanks a lot for the detailed steps! Unfortunatelly I wasn’t able to reproduce it, and in my case it always scheduled the deployment to the correct dattime. You said you were running Octopus 3.0.24, correct? Could you also let us know which browser are you using?
I’ve tested it on IE and I was able to reproduce the error. So it seems its only isolated to this particular browser (and something tells me that same or worst will happen on Edge). Here’s the github issue for this: https://github.com/OctopusDeploy/Issues/issues/2014
The calendar picker also seems to be broken, so the recommended workaround is to use another browser for the time being.