ALM Dos and Don'ts: CI and Source Control
These tips for Application Lifecycle Management, or ALM, will help you ensure that CI is being monitored and the database is managed properly.
Join the DZone community and get the full member experience.Join For Free
CI Builds Status
We all know the practice of continuous integration.
One of the common pitfalls of CI is that the build status is not monitored and not treated as one of the top priorities for the team.
A healthy/green status of our CI process means that our code is in a good shape as far as our automated tests can tell. Fixing the build status ASAP is easier than leaving it red and fixing it later because the recent changes to the codebase are vivid in the team members’ memory.
Database Source Control
Every application needs to store its data. A (relational) database is the most common choice in many situations. Like every other component of our software project, a database schema must be managed with a version control system. We will never work without source control for our source code files and we must use the same mindset when dealing with a database.
The database is a critical part of our application. If we deploy version 2.0 of our application against version 1.0 of our database, what do we get? A broken application. And that’s why our database should always be under source control right next to our application code.
Published at DZone with permission of Michele Ferracin, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.