For everyone's information, it looks like they took a lot of feedback I (and certainly others) gave them last year to heart. Sounds like it's possible to fully automate a Coverity scan. Anyone want to take a stab at hooking the automation into our continuous integration setup?
We also need to collectively decide whether to go with Jenkins or Buildbot at this point. With both set up under GCI, I found both perfectly suitable for our needs. They are definitely different, though.
Jenkins is better looking. It has a very clean interface for viewing reports and is easy to navigate. It runs as it's own web process daemon. Configuration of jobs is primarily done through the web interface. Adding new jobs can be cumbersome, but it is a simple process.
Buildbot is more flexible. Interface has the same report information but not as well organized. It runs under Apache. Configuration is achieved by editing python configuration files. Adding new jobs is more flexible/programmable and they're quick text edits, but you have to learn basic API.
Not fond of Jenkins being a separate process, but there's some docs for running it behind Apache. I loved the simplicity of editing Buildbot's files but hesitate to base a decision solely on that awesomeness. I'm currently leaning towards Jenkins because I think we'll spend FAR more time viewing and navigating reports than we will be setting up jobs.
Thoughts? Preferences? I'd like to hear other inputs even with this being a bikeshed color question, because we do need to decide. We've gone far too long without.
Cheers!
Sean
Begin forwarded message:
From: [email protected]
Date: June 20, 2013 3:26:08 PM
To: [email protected]
Subject: New Enhancements in Coverity ScanHello Sean Morrison,Thank you for your participation in the Coverity Scan program. We are pleased to announce that we have enhanced our service to address the feedback of our members. These enhancements enable you to:
Please visit us at http://scan.coverity.comto take advantage of these new capabilities.
- Receive an automatic email notification when new defects are found in the latest build
- Automate the upload of your build to Coverity Scan
- Group your defects into different components and fix what matters most
- Easily identify the defects that you are responsible for based on component definition
- Ignore defects in third party components
- Easily invite other contributors to participate in your project in Coverity Scan
- Grant read only access to specific users
- Easily add Google Summer Code users and other similar internship users and grant them read only permission.
- Improve the accuracy of analysis through the use of modeling
Thanks
Dakshesh Vyas | Technical Manager - Coverity Scan
Coverity | 185 Berry Street | Suite 6500, Lobby 3 | San Francisco, CA 94107
Office: 415.935.2957 | [email protected]
http://scan.coverity.com/
The Leader in Development Testing#################################################################################Some of the talks about Coverity Scan within Open Source community. GPSD - Coverity is a code-analysis tool - an extremely good one, probably at this moment the best in the world http://esr.ibiblio.org/?p=4340 Linux - "Coverity points out that we do not free in one case the pr_backup - and sure enough we forgot." https://lkml.org/lkml/2012/7/3/297 Mesa - "Coverity Uncovers More Problems In Mesa" http://www.phoronix.com/scan.php?page=news_item&px=MTI0MDA #################################################################################
------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev
_______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
