Re: Claim plugin has fallen silent

2016-02-09 Thread douglas3457
Solved! Since commit c2ea74e2a58cddff9219a03ffe261c1f95ea4be5 the claim plugin has included all the Build Failure Analyzer failure causes in the generated JavaScript, like this: var json = '{"First

Re: Claim plugin has fallen silent

2016-02-08 Thread douglas3457
Closer examination of the log reveals that the exception I listed was generated when we had restarted without the plugin installed - yes, we had wiped it manually from the filesystem. After reinstallation, there were no claim plugin exceptions. On Friday, February 5, 2016 at 9:30:42 PM

Re: Claim plugin has fallen silent

2016-02-08 Thread douglas3457
Turns out we are suffering a JS error: "ReferenceError: ShowPopup is not defined" when we are clicking on the Claim It link. I'm not sufficiently familiar with JS to be able to find the error in the code (if any) myself - as far as I can see, the function is there. Presumably, the defect

Claim plugin has fallen silent

2016-02-04 Thread douglas3457
Our Jenkins server suffered a power outage, and since restart, the Claim plugin has refused to work: Clicking on the "Claim it" link for a failed job has no visible effect. We have uninstalled the plugin and restarted, reinstalled and restarted, all to no avail. Nothing appears in the Jenkins

Claim plugin has fallen silent

2016-02-04 Thread douglas3457
Our Jenkins server suffered a power outage, and since restart, the Claim plugin has refused to work: Clicking on the "Claim it" link for a failed job has no visible effect. We have uninstalled the plugin and restarted, reinstalled and restarted, all to no avail. Nothing appears in the Jenkins