-
Bug
-
Resolution: Unresolved
-
Major
-
None
I'm testing the calendar plugin on our test jenkins server (thus the pink background), but the result is similar on another server.
Jobs for week and day view render on top of each other, at the top of the day instead of around the proper time.
There is also a hover-over js error:
jquery.full.js:1502 Uncaught Error: Syntax error, unrecognized expression: .event-id-view-job%20schedule-job-anothertest-1551471300000
at Function.Sizzle.error (jquery.full.js:1502)
at Sizzle.tokenize (jquery.full.js:2159)
at Sizzle.select (jquery.full.js:2580)
at Function.Sizzle [as find] (jquery.full.js:903)
at jQuery.fn.init.find (jquery.full.js:2826)
at new jQuery.fn.init (jquery.full.js:2949)
at jQuery (jquery.full.js:75)
at a (events.js:45)
at Object.e.select (events.js:77)
at index.js:103
[JENKINS-56350] Week, Day layout incorrect
Hello,
Same issue on my side, all jobs displayed on only one tile at 00:00 in day view or week view.
Tested on IE11 and Chrome 64 with Jenkins ver. 2.89.4
It's really annoying.
On my side, I don't have access to logs as not admin of Jenkins or server hosting Jenkins.
Regards,
Matthieu MERAVILLE
added a comment - - edited Hello,
Same issue on my side, all jobs displayed on only one tile at 00:00 in day view or week view.
Tested on IE11 and Chrome 64 with Jenkins ver. 2.89.4
It's really annoying.
On my side, I don't have access to logs as not admin of Jenkins or server hosting Jenkins.
Regards, 
Wayne Berry
added a comment - Same issue here. Month view renders fine. Issue is only seen on week and day views.
Wayne Berry
added a comment - Same issue here. Month view renders fine. Issue is only seen on week and day views. 
Simon Nicoll
added a comment - Hi,
is anyone going to look at this and give us a fix or is it stop using the plugin time?
Thanks
Simon Nicoll
added a comment - Hi,
is anyone going to look at this and give us a fix or is it stop using the plugin time?
Thanks 
Carlos
added a comment - I am having this same issue, not seeing the sizzle error in the console from javascript... but I do see all of my jenkins scheduled jobs showing up at the very top in time slot 00:00 not in the correct location.
This issue seems to only happen on the Day and Week Page. the Month page looks fine.
Is this because the plugin wants jenkins to use UTC Timestamps? I believe my jenkins uses Eastern Standard Time.
Would love to get this issue resolved but I am not sure where to start digging through the java code.
Carlos
added a comment - I am having this same issue, not seeing the sizzle error in the console from javascript... but I do see all of my jenkins scheduled jobs showing up at the very top in time slot 00:00 not in the correct location.
This issue seems to only happen on the Day and Week Page. the Month page looks fine.
Is this because the plugin wants jenkins to use UTC Timestamps? I believe my jenkins uses Eastern Standard Time.
Would love to get this issue resolved but I am not sure where to start digging through the java code. Carlos
added a comment - I think the sizzle error is because you have a space in your calendar name.
job%20schedule
I dont think javsacript allows class names to have spaces in them.
try naming your calendar job-schedule and see if it works.
I think the sizzle javascript issue is seperate from the issue of all the jobs appearing at 00:00 instead of their correct location.
Carlos
added a comment - I think the sizzle error is because you have a space in your calendar name.
job%20schedule
I dont think javsacript allows class names to have spaces in them.
try naming your calendar job-schedule and see if it works.
I think the sizzle javascript issue is seperate from the issue of all the jobs appearing at 00:00 instead of their correct location. 
Roland Asmann
added a comment - Sorry for the long silence. I've taken over this plugin last year, but hadn't gotten around to checking all issues.
Is this still an issue with the current Jenkins+Plugin?
Roland Asmann
added a comment - Sorry for the long silence. I've taken over this plugin last year, but hadn't gotten around to checking all issues.
Is this still an issue with the current Jenkins+Plugin? 
I am encountering the exact same issue. I noticed it 2 months ago.