All Resources

Klocwork - Bringing static code analysis to continuous integration

It starts at the developer's desktop. It's here where code is written, tested, reviewed, and written again. Finding problems here, at the earliest possible point before the build, means less testing later on and fewer downstream impacts to cost and schedule. Klocwork puts static code analysis and continuous integration, including support for Jenkins and TeamCity, where you need it.  

Continue Reading Here

Lessons learned: Using a static analysis tool within a continuous integration system

Static analysis tools are used for improving software quality and reliability. Since these tools can be time consuming when used for analysis of big codebases, they are normally run during scheduled (e.g. nightly) builds. However, the sooner a defect is found, the easier it is to fix efficiently.

In order to detect defects faster, some analysis tools offer an integration with the integrated development environment of the developers at the cost of not always detecting all the issues. To detect defects earlier and still provide a reliable solution, one could think of running an analysis tool at every build of a continuous integration system.

In this IEEE paper, we share the lessons learned during the integration of the static analysis tool Klocwork (that we are developing) with our continuous integration system. We think that the lessons learned will be beneficial for most companies developing safety-critical software (or less critical systems) that wish to run their analysis tool more often in their build system. We report these lessons learned along with examples of our successes and failures.

Continue Reading Here

Fitting static code analysis into continuous integration

One of the hottest topics in DevOps is Continuous Integration (CI), a software development practice where members of a team integrate their new code frequently — perhaps multiple times per day. Each integration kicks off an automated build and test process to expose any defects and report status as quickly as possible.

Learn about the benefits of CI and how to maximize their impact on your software development practices.

Continue Reading Here

Category Tags
academic aerospace agile development Akana case study Akana datasheet Akana Lifecycle Manager Akana Platform Akana video Akana white paper API analytics API development API Gateway API management API microservices API portal API security Apigility automotive brochure brochures case study CentOS cloud CodeDynamics CodeDynamics video coding standards continuous delivery continuous integration datasheet debugging defect detection developer productivity DevOps digital media dynamic analysis ecommerce Elixir embedded analytics energy & environment enterprise php Expressive Family finance government HostAccess how-to HydraExpress IBM i IBM WebSphere DataPower IMSL IMSL C Library IMSL Family IMSL Fortran Library IMSL Java Library IMSL NET Library infographic insurance JMSL JViews Klocwork language: c language: java legal & compliance license life sciences & healthcare manufacturing MemoryScape MISRA mobile network and telecom equipment NoSQL OAuth OEM & ISV open banking open source Open Source Audit open source management open source support OpenLogic Other Industries php presentation product publishing PV-WAVE PyIMSL Studio Python real estate ReplayEngine research REST retail scanning & governance security Semantics Manager services SmartRank SOA SOAP software policy software quality software security software verification SOLA source code analysis SourcePro static analysis static code analysis Stingray Studio supply chain support support & services survey results telecom TotalView training transportation video Views Visualization web development white paper Zend Zend case study Zend datasheet Zend Framework Zend Guard Zend Server Zend Studio Zend video Zend white paper Z-Ray