Jenkins' cron trigger supports specifying timezone (since this PR), and calling the trigger's next() method returns the correct time with timezone information, but somehow next-executions UI does not reflect the time correctly (still uses system timezone)