Add Timezone support for Cron Triggers
long-term
E
Enchanting Iguana
Cron triggers run off of UTC, with no support for local time (and therefore no support for DST). In locations which use DST, this results in the local time of a job's execution shifting twice per year without manual intervention
Log In
K
Kobi Blackbird
i Can see this feature request is under development from last one year.
We have pipelines that impacts due to Day light saving time changes.
it is painful to change CRON schedule twice a year.
What is product development timeline ?
M
Mere Reptile
It's been another year and we now have hundreds of pipelines built. This is throwing off our deploys. Can we get this prioritized so that we do not have to change our triggers twice a year?
Rohan Gupta
Merged in a post:
Required US/Eastern time zone to use in pipeline trigger
O
Olive drab Parakeet
Currently UTC is the only time zone standardized in the harness.
We are using trigger in our one of the pipelines, we are expecting to have US/Eastern time zone to use in the cron expression to handle the daylight-saving time.
if we use UTC, we will need to continue by calculating the time and adjust the daylight-saving time which would be the issue specially with PROD environment while maintaining it.
We would need your help to add US/Eastern time zone in order to use. Your assistance and help on this will be much appreciated. Thanks, in advance.
Shylaja Sundararajan
long-term
Shylaja Sundararajan
under review
Shylaja Sundararajan
planned