-
Notifications
You must be signed in to change notification settings - Fork 43
[JENKINS-52009] Added support for timezone in cron and percent sign in parameter key/value #47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The hpi file generated for this PR can be found at Use hpi file to upload the plugin with above mentioned features. |
} | ||
|
||
@Test | ||
public void with_no_params_seperator() throws Exception { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
spelling should be separator not seperator
great PR otherwise - I came here looking for a way to use timezone :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @shbhardwaj
Did you have chance to look at above comment?
Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
spelling fixed
Question for the maintainers: Would it be quicker to get this timezone functionality merged if there were a separate PR with just that functionality? I can create that PR, if so, given that's what my team has the most use for (granted I would be shamelessly copying @shbhardwaj's code to do so) |
This should happen or merge this! Long over due. |
Would be great to have this merged in! |
please merge it. |
Hi @batmat it would be great to review and merge the changes. Do you think a different pull request only for timezone should be needed as @bawjensen suggested to have the release faster? cc: @shbhardwaj |
Can anyone merge this? |
@batmat Please advise if there is anything that needs to be done to get this merged. This is really important for orgs that have a centralized jenkins installation and teams spread across the world. Developers want their jobs to run in their local time and this helps deal with Daylight Savings. Not all time zones switch at the same time and scheduled jobs that are expected to run at a given time are now running an hour earlier or later depending on the time of the year. |
let's get this merged! |
merge this feature please. ppl need it |
Can anyone merge this please?? This would be a great fix! |
@shbhardwaj Can you please kindly resolve the conflict and update your PR? Then @res0nance, if you would be able to merge this into the master at an early convenience, it would be great! |
@andymcf @mpasat Spelling fixed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@shbhardwaj sorry about that, I recently took over as maintainer roughly 2 weeks ago
What is the ETA for making this fix available in a new release? We would like to make use of it. |
Waiting for a reply on #44 followed by some testing, then a release. Can't give an exact ETA, but maybe a week or two after that PR is merged. |
It would be nice if README had an example usage that included timezone, e.g.
(FYI, currently the TZ expression can only be on the first line, applies to all lines if present.) |
Current behavior : No way to set timezone for all the parameterized cron expressions.
After this change : Timezone in first line will be applied to all the cron expressions see below for example.
TZ=Australia/Sydney
H/15 * * * * %name=value
H(0-29)/10 * * * * % name=value; othername=othervalue
The timezone Australia/Sydney will be applied for both the crons.
Current behavior : If percent sign is part of some parameter key or value then all the parameters of the job are ignored.
After this change : Only the first % sign will be used to separate the cron expression from the parameters. Any other percent sign in key/value will be part of the key/value see below for example
H/15 * * * * %name=value;key=10%;
The parameters will be name=value, key=10%