By default nothing should happen.

If you as a maintainer would want to have findbugs run and/or mark the
build as unstable you can ask someone with configure job permissions on
jenkins.ci.cloudbees.com to tick one or both of the new checkboxes on the
config page of your plugin job. And update your pom to produce xmlOutput
for findbugs:

Example:
<build>
    <plugins>
        <plugin>
                <groupId>org.codehaus.mojo</groupId>
                <artifactId>findbugs-maven-plugin</artifactId>
                <version>3.0.1</version>
                <configuration>
                    <xmlOutput>true</xmlOutput>
                    <findbugsXmlWithMessages>true</findbugsXmlWithMessages>
                    <failOnError>false</failOnError>
                </configuration>
            </plugin>
    </plugins>
</build>


If you configure your pom to automatically run findbugs or checkstyle
during for example the verify phase the Jenkins job should automatically
pick that up.

/B

On Thu, Jul 2, 2015 at 5:03 PM, Mark Waite <[email protected]>
wrote:

> Can you explain a little further what that will mean?
>
> When I merge a change to the git-plugin, will the
> https://jenkins.ci.cloudbees.com/job/plugins/job/git-plugin/ job now fail
> because findbugs reports are being retrieved?
>
> Will there be another graph on the page which shows the findbugs output
> for that job?
>
> Likewise for checkstyle.
>
> Thanks,
> Mark Waite
>
> On Thu, Jul 2, 2015 at 8:45 AM Robert Sandell <[email protected]>
> wrote:
>
>> I've changed the plugin template for maven to pick up findbugs and
>> checkstyle reports* (on ttps://jenkins.ci.cloudbees.com
>> <http://jenkins.ci.cloudbees.com>)* if any is generated by the build. So
>> if plugin builds starts to fail for that reason you know who to blame ;)
>> But it shouldn't change anything for existing jobs unless you actively do
>> something.
>>
>> I've also added config options to run findbugs and mark the build as
>> unstable if any findbugs issues are found, so maintainers can opt in for
>> that if they want to.
>>
>> For my own plugins I run checkstyle in the compile phase so I didn't
>> bother adding that option there.
>>
>> --
>> Robert Sandell
>> *Software Engineer*
>> *CloudBees Inc.*
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS0bvoSb0CDYCEhhKfiwUHwayZ-mRxaCUNPfZGSC9Gzp7Q%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS0bvoSb0CDYCEhhKfiwUHwayZ-mRxaCUNPfZGSC9Gzp7Q%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>  --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtEYz1rDjaaJV4j9hSZ0cNVwmFNTxw2oRxOh%2BkOD5Dv3rA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtEYz1rDjaaJV4j9hSZ0cNVwmFNTxw2oRxOh%2BkOD5Dv3rA%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS0vwdeyt%2BaLqKSfMFicQCnbG2%3DGKHEmmCwyYL%2Bx50ztTA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to