On our Jenkins (1.492) I have the Claim Plugin installed. Jenkins is configured to use LDAP using matrix authorization.
After installing the plugin and enabling the plugin in the configuration of each job the /claim view says "Welcome to the Hudson Claim Report. There are no failing builds. Excellent work!" and does not list any builds to claim.
I have both unstable and failed builds.
What have I missed? How can I find the problem?
To troubleshoot Jenkins pipeline failure issues On the Console Output page, check the logs to find the reason for the failure. If required, update the parameters in the deployment input configuration file. Learn about deployment input configuration file parameters at Setting up the deployment input configuration file.
The claim plugin is meant to allow users to claim failing builds and tests from Jenkins to signal they are taking responsibility in fixing them. Supported features. Claiming failed builds. Claiming failed tests.
In order to activate the Claim Plugin you must first add the 'Allow broken build claiming' action to the 'Post-build Action' section of one or more jobs. The next time the job fails after adding this step, it should be available to claim.
Configuring this on a large number of jobs is a bit of a pain but fortunately someone has contributed a Groovy script to allow broken build claiming on every job.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With