The race to improve software quality and innovation has been around since the 1970s. Many processes and workflows have been created to help address the historical issues that prevent teams from developing high-quality applications quickly and reliably, yet enterprises continue their struggle to keep up.
Continuous Integration is a way to help build quality, security, and regulatory compliance into the SDLC. In agile development, Continuous Integration, or CI, asks developers to merge code changes into the central code repository often and consistently. Several times a day, builds are automated and unit tests and integration tests are performed. Because there are typically only small changes in code, each test can pinpoint specific changes that introduced a flaw or vulnerability.
The two main goals of CI are to ensure the high quality and good health of code, continuously, and to ensure a seamless flow between development, testing and deployment. Each organization needs to define for themselves how these goals are to be achieved, yet they provide a strong starting point for all organizations – from Netflix to SMB’s – looking to improve their development process.
There’s a lot involved in CI. To help get everyone up to speed, we’ve put together a dictionary of important terms and tools to understand and know, surrounding CI and more broadly, DevOps.
The ABC’s of CI
A – Agile & Apache Ant
Agile – Continuous Integration processes are agile, which means they are characterized by short work phases, frequent reassessments, and adaptation of plans. Everything changes in business, and even more so in software development. The ability to facilitate change in development to better accommodate the business model and involved teams is part of what makes an organization agile – a key component in continuous integration. Agility is a key component of DevOps, as well.
Apache Ant – One of the top tools for build automation, a component of Continuous Integration. Ant is made primarily for Java and uses XML to note the build process and its dependencies.
B – Bamboo & Build Automation
Build Automation is the process of automating a build and its surrounding processes, either through a tool like Apache Ant or Maven, or on a dedicated build server. In short, build automation tools turn source code into executable code. The build automates each step of the process, from compiling source code to producing installers, to updating the database after the build is completed. Automating these areas not only speeds up the process, but eliminates many of the issues that arise with a manual build.
Bamboo is a continuous integration server by Atlassian which automates a build and test process once code is committed to the source repository. Test results are immediate, allowing developers to fix issues in near real-time.
C – Continuous Deployment and Continuous Delivery
Closely related to CI is Continuous Delivery, is a practice in which code can be deployed at any moment to production because of rigorous automated testing. The concept is based on the fact that automated builds and testing are so tightly integrated into the build that shipping is possible at any given moment.
Often paired with CI and following closely after Continuous Delivery, Continuous Deployment refers to the practice of shipping each time a version has passed testing.
The main difference between Continuous Delivery and Continuous Deployment is that deploying to production is manual in the former and automated in the latter.
D – DevOps
DevOps is the umbrella term for many of the processes including and surrounding Continuous Integration. DevOps is a cultural change in IT which adopts agile processes, including CI, Continuous Deployment, and Continuous Delivery, automation tools for builds and tests, and cultural changes like a higher rate of collaboration between development, operations, and security teams. DevOps was created to help businesses succeed in the fast-paced development world.
Dive deeper into DevOps here.
F – Feedback
A tenant of DevOps and a major benefit of implementing Continuous Integration processes is rapid feedback. Feedback, in the form of build and test results, offer a full picture of the project’s state as often as CI takes place. By fixing issues based on feedback, the overall health of the project at hand is increased, which in turn improves software quality.
G – GIT & GitHub
Git is a version control system which tracks source code changes and updates the repository after CI is triggered.
GitHub is a web-based version of the Git version control system and hosts code online for access control, bug tracking, feature requests and task management. Any standard Git command also work on GitHub.
I – Integration Testing
Following unit testing in CI is integration testing, where code units are combined and tested as a group. Types of integration testing include big bang, bottom-up, top-down, and sandwich testing. Integration testing enables faster feedback on problems involving integrations, which can be fixed upon finding rather than at the end of the SDLC.
J – Jenkins & JIRA
Jenkins, like Bamboo, is a Continuous Integration server to help facilitate automated builds and tests. Written in Java, Jenkins also offers various plugins that allow it to work with other languages.
CxSAST Jenkins plugin is a source code analysis solution that helps identify, monitor and fix errors, vulnerability issues and compliance problems found within the source code. The CxSAST plugin scans the source code and supplies scan results as either static or interactive reports; interactive meaning the enablement of runtime tracking per vulnerabilities in the code. This plugin will then administer the necessary remediation guidelines and action items.
Read more about Bamboo vs. Jenkins here
JIRA is a bug and issue tracking tool used within the CI workflow to help detect and highlight issues found through automated testing.
M – Maven
Apache Maven is a build automation tool, primarily used for code written in Java but that can also be used on projects written in C#, Scala, Ruby and more. The tool differentiates the build from its dependencies, making detecting where issues arise much easier.
S – Security Testing & SonarQube
When it comes to Continuous Integration, another benefit could be increased security of the code through automated security testing. While unit testing and integration testing are enormously helpful in detecting functional and quality issues within the project, they don’t necessarily detect security issues. Security testing can be integrated into the CI workflow, however, and will similarly pinpoint security vulnerabilities that can be addressed immediately, rather than at the end of the SDLC.
Read more about Continuous Integration Security here.
T – Test Driven Development
Underpinning CI is the Test-Driven Development (or Test-Driven Design) methodology, driven by building a strong application through meticulous testing. TDD runs on a process of initial testing, coding, and refactoring to solve found issues.
U – Unit Testing
Part of the automated test process involved in CI includes unit testing, which automatically tests the smallest possible code base individually to find issues as early as possible. The concept of unit testing is to isolate a specific area of a project to validate that it was written correctly.
V – Version Control
Version control tools like Git and GitHub log changes to code, configuration files and documentation to enable better management of changes and differing versions of code. These tools are especially helpful when different teams work on the same project, which can often create confusion if not properly tracked.
The AppSec How To: Application Security in Continuous Integration
Latest posts by Sarah Vonnegut (see all)
- How Secure is Your Online Banking App? - February 26, 2018
- Top 5 OWASP Resources No Developer Should Be Without - January 9, 2018
- Smart Cities: Can My City be Hacked? - December 11, 2017