Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standalone execution #179

Closed
anantshri opened this issue Feb 17, 2016 · 4 comments
Closed

Standalone execution #179

anantshri opened this issue Feb 17, 2016 · 4 comments

Comments

@anantshri
Copy link

Consider this as a feature request if its not already possible.

Is it possible to run the plugin directly from commandline without integrating with other systems such as jenkins etc.

@dpnishant
Copy link

@anantshri Jenkins too runs a command as you would run it on a shell. You can use mvn findbugs:findbugs to run the plugin. However do keep in mind that can only run on compiled binaries and not on raw .java or .jsp sources.

@h3xstream h3xstream added bug and removed bug labels Feb 17, 2016
@h3xstream
Copy link
Member

@dpnishant is right.

@anantshri What is your build system?
We have put example of configuration for Gradle, Maven and SBT here: https://github.com/find-sec-bugs/find-sec-bugs-demos
The respective plugin can be trigger without CI.

Alternatively, their is a recent experiment .. A CLI client that analyze JAR and classes folder.
https://github.com/find-sec-bugs/find-sec-bugs/wiki/CLI-Tutorial

@mkienenb
Copy link
Contributor

@anantshri Even though it is not currently well-documented, the command-line findbugs tool accepts the -pluginList argument, which you can point to the find-sec-bugs plugin.

@anantshri
Copy link
Author

@dpnishant and @mkienenb thanks for the pointers folks. that should solve my problem.

@h3xstream This is for integrating find-sec-bugs into androidtamer distribution where primarily people will be doing a blackbox review of application and since no CI so needed a CLI way of getting by with the system.

I suppose the answers are adequate and i have ways to achieve this now hence closing the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants