Add Timezone support for Cron Triggers
in progress
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
This post was marked as
in progress
Rohan Gupta
Merged in a post:
Automatic Daylight Savings Time (DST) in Scheduled Triggers
U
Utrecht blue Zebra
Problem:
Currently, scheduled triggers in Harness use UTC time and do not automatically adjust for Daylight Savings Time (DST). Customers have to manually update the cron expressions every March and November to account for the time change, which is cumbersome.
Request:
Allow customers to specify their local timezone (e.g., EST/EDT) in scheduled triggers, with automatic adjustments for DST. This would eliminate the need for manual updates when DST begins and ends.
Rohan Gupta
Merged in a post:
Cron triggers on Pipelines
P
Papaya Caribou
So we had a cron trigger on our pipeline with an cron expression like below. This works in Jenkins as it would run at 9:30 and 13:30 on Mon-Thus. But in Harness it only runs at 9:30 on Mon-Thurs. Either would like this cron expression be not allowed or ideally allow for this type of feature in Harness cron schedules.
30 9,13 1-4
Rohan Gupta
Merged in a post:
Ability to schedule jobs based on time and not cron
E
Eager Cardinal
Currently Harness supports only CRON to schedule jobs.
This means that as an user, I need to be aware of the system load in order to schedule jobs that do no overload the servers.
Ex: I have 100 jobs that I want to run in a day. I dont mind the time of the day it runs, and all I want to do is run it once in a day. The current solution puts the onus on me to figure out the system load at any given time and determine the best time to schedule these 100. This is inefficient and error prone.
I would like to Harness to provide me a way to configure a job to be run once a day, once a week etc. and automagically identify the best time to do it based on other configured cron/scheduled jobs.
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
Load More
→