-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Schedule build plugin: 502.v9379e178e65b_
Jenkins Core 2.426.3
The default schedule time that one gets proposed is not returning the expected value.
Also it is totally unclear in which timezone the build will run.
Steps to reproduce
- Setup your controller to run in GMT timezone
- Configure the default start time to 22:00 PM and the timezone to Australia/Sydney
- Create a job
- Click Schedule build from sidepanel
- Click Schedule without modifying date and time
Expected
It is clear at which time the build will start and the build will really start at at 10 PM Sydney time
Actual
The proposed date / time is wrong, e.g.
When triggering at 1 PM GMT (that means this is after 10 PM in Sydney so it should start the next day) I would expect to be shown date+1, 10 PM, but what I get is date+1, 9:00:00 AM. The build now start at date+1 9 AM Sydney time.
And it is totally unclear that the given timestamp is calculated in Sydney timezone, something one can only know by looking at the system config.
- links to