I'm having the same problem. When attaching &debug=true to the URL, it prints the following messages:

13:57:39.221: started jenkins wall display
13:57:39.222: url 'http:://ci.chiliproject.org//'
13:57:39.223: view name: 'All'
13:57:39.224: clientHeight: 670, clientWidth: 1024
13:57:39.225: timeOut: 15000ms
13:57:39.226: update interval: 20000ms

The URL is obviously wrong (contains :: instead of . This is also reflected in the fact, that Ajax request are made to

http://ci.chiliproject.org/plugin/jenkinswalldisplay/http:://ci.chiliproject.org///view/All/api/json?depth=1&_=1354712004607

which also contains too many :: and //.

Perhaps this information helps to debug the issue.

We are running the latest Jenkins (1.492) and Wall Display (0.6.15) versions. Testing on FF 18.0 on Mac OS X.

Cheers,

Gregor

Hi everyone. I need this bug/feature so much that I'm willing to pay 5.00 bucks for it.
This offer is registered at FreedomSponsors (http://www.freedomsponsors.org/core/issue/89/wall-display-shows-loading-jobs-forever).
Once you solve it (according to the acceptance criteria described there), just create a FreedomSponsors account and mark it as resolved (oh, you'll need a Paypal account too)
I'll then check it out and will gladly pay up!

If anyone else would like to throw in a few bucks to elevate the priority on this issue, you should check out FreedomSponsors!

I'm the author of the plugin, due to time constraints i currently only have time for the plugin on weekends. So if you wait until tomorrow I'm sure I can sort this out (for free )

I just tried to reproduce the problem with the URL you mentioned: http://ci.chiliproject.org/, there I clicked on the "Wallddisplay" link and everything worked as expected (tested with various Firefox Versions, Chrome and IE) are there any additional steps I have to make to trigger the problem?

You're right. It looks like I was not patient enough. It works fine, when I'm using the link. I tried debugging and removed the jenkinsUrl parameter and then the debug output from above may be observed.

So in fact, it looks like my problem is solved.

On the other hand, it would be nice, if the plugin would emit a proper error message, when the jenkinsUrl parameter is mandatory but not present. So maybe this bug is still valid, though far less critical.

Thanks,

Gregor

Neither I can reproduce the problem. I've upgraded to Jenkins 1.492, Firefox 17.0 and made a lot of changes to my job configurations. Can't really say what it was that solved it. I do know it existed before, because I let it try to load the jobs during a whole night.

Just tried and the plugin does now give an error rather than just loading jobs if the url is incorrect.