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

Time Zone support #2504

Merged
merged 11 commits into from Jun 20, 2017

Conversation

Projects
None yet
4 participants
@jtobard
Contributor

jtobard commented May 11, 2017

Fix #906 bug, now the execution time is displayed the same on Activity page and on the job detail.

And add the support for execute scheduled jobs on other time zone from #138

The Time zone now its part of the Schedule to run repeatedly section.
The schedule will be executed against this time zone, in case its empty or null, the actual implementation will be used, scheduling it against the jvm timezone.

A new input text with contextual help about how to complete it:
screenshot at may 05 16-15-14

With autocomplete of supported time zones:
pasted image at 2017_05_09 01_42 pm

The input isn't restricted to time zones to enter GMT+/- custom time zones.

In the case the entered time zone isn't valid a error is displayed:
image

@gschueler gschueler modified the milestone: 2.9.0 May 11, 2017

@Fahri28

This comment has been minimized.

Show comment
Hide comment
@Fahri28

Fahri28 May 31, 2017

Hi,
is this custom script already fixed?, and may i know what rundeck version you use, because i not found "ScheduledExecutionController.groovy" in /var/lib/rundeck

thank you

Fahri28 commented May 31, 2017

Hi,
is this custom script already fixed?, and may i know what rundeck version you use, because i not found "ScheduledExecutionController.groovy" in /var/lib/rundeck

thank you

@jtobard

This comment has been minimized.

Show comment
Hide comment
@jtobard

jtobard May 31, 2017

Contributor

@Fahri28 This is not a custom script but this feature will be in the 2.9.0 release.

Contributor

jtobard commented May 31, 2017

@Fahri28 This is not a custom script but this feature will be in the 2.9.0 release.

@Fahri28

This comment has been minimized.

Show comment
Hide comment
@Fahri28

Fahri28 Jun 2, 2017

@jtobard thank you for you replying,
may i know when the new version 2.9 will be released as we check in rundeck.org currently only 2.8 version

thank you

Fahri28 commented Jun 2, 2017

@jtobard thank you for you replying,
may i know when the new version 2.9 will be released as we check in rundeck.org currently only 2.8 version

thank you

@gschueler gschueler changed the base branch from master to prerelease-2.9.0 Jun 20, 2017

@gschueler gschueler merged commit 401e7d5 into rundeck:prerelease-2.9.0 Jun 20, 2017

@jimr6007

This comment has been minimized.

Show comment
Hide comment
@jimr6007

jimr6007 Oct 25, 2017

Can't believe I didn't notice this until now but it seems that it's defaulting to EST. The server is definitely at UTC and none of my jobs have the TZ specified on the job config page. Today I realized, what da..., my jobs are all running 4 hours earlier than I expected, or 4 hours later. Now I'm confused.

I'm at 2.9.2-1 CentOS 7

screen shot 2017-10-25 at 7 42 05 pm

screen shot 2017-10-25 at 7 45 02 pm

jimr6007 commented Oct 25, 2017

Can't believe I didn't notice this until now but it seems that it's defaulting to EST. The server is definitely at UTC and none of my jobs have the TZ specified on the job config page. Today I realized, what da..., my jobs are all running 4 hours earlier than I expected, or 4 hours later. Now I'm confused.

I'm at 2.9.2-1 CentOS 7

screen shot 2017-10-25 at 7 42 05 pm

screen shot 2017-10-25 at 7 45 02 pm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment