We are running Octopus version 18.104.22.1686
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
Any idea what is wrong?
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?
Thanks for reaching out. This bug was fixed in 3.0.13. Please try to update to the latest version to get this fix and many others .
I’ve upgrade to version 3.0.24 and the default Schedule date that appears is still in the following format:
Also, if you put a date in this format it would deploy the changes immediately without any errors.
btw, the issue occurs when you input the a future date in the following format: “2015-09-18”
I see that it works if you select the date from the calendar.
I’m not able to reproduce the issue you are mentioning. It works as expected for me with both
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:
e.g 2015-09-17 change to 2015-09-18
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
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.
Senior Release Analyst, Service Delivery
ILS Commercial Delivery & Technology
d: 01733 845878
Join BGL Group on social media
[Description: http://intranet/GroupCommunications/PublishingImages/Social%20Media/Facebook-email-logo.jpg]https://www.facebook.com/pages/BGL-Group/337417076303996[Description: http://intranet/GroupCommunications/PublishingImages/Social%20Media/Twitter-email-logo.jpg]https://twitter.com/The_BGL_Group[http://t0.gstatic.com/images?q=tbn:ANd9GcTFOZJtni6_J0v5TJlWW-CTVIk90I79BtZmJ2TA2xQcoA5I5zHBO4mCXuWB]http://www.linkedin.com/company/162701
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.