Just cloned a configuration with 4 time triggers. All time triggers were added as +1 in the new configuration.
Thus originally 09:00 became 10:00.
Hi Geert,
We’ve not been able to replicate this, despite testing with different timezones. What type of time triggers were cloned (daily, weekly, monthly or once off)? Can you also provide details of the timezone on your server and client machines. The time that you made the change could be possibly also be relevant.
Hmmm, my bad. I checked the old configurations and there it also has the wrong timezones:
Trigger TypeNameDescription
Daily09:00Trigger build at 10:00:00 every day.
Daily12:00Trigger build at 13:00:00 every day.
Daily15:00Trigger build at 16:00:00 every day.
Daily19:00Trigger build at 19:00:00 every day.
Either someone changed them (which I find very strange, but it’s possible) or it is done by something in the database which I was not aware of (update of database / something on the db server)? This instance using SQL Server.
For now please ignore this issue, I should’ve checked the original configuration first.
The reason why we did this btw: we had a single project with 25 configurations (because we couldn’t clone over projects in the 1.0.* versions). Now we have moved everything to separate projects. It would be great to have a “move configuration” feature as well (but we don’t need this because we manually copied everything over already).
Hi Geert,
We had issues with time trigger times not being converted been timezones correctly in previous versions of Continua, which have now been fixed. Perhaps these triggers were created using an earlier version.
We’ve made some further checks through the code to check for daylight saving time issues, but everything appears to work correctly. Let us know if you notice the times changing again.