Insight: Continuous integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily – leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. Many teams find that this approach leads to significantly reduced integration problems and allows a team to develop cohesive software more rapidly. Continuous integration (CI) was created for agile development. It organizes development into functional user stories. These user stories are put into smaller groups of work, sprints. The idea of continuous integration is to find issues quickly, giving each developer feedback on their work and TDD evaluates that work quickly. Continuous Integration helps teams work more efficiently. These teams can be cross-functional, they can be geographically distributed, because the constant integration work will ensure that you don’t get deviating designs. At Apiumhub we use this development practice at our projects such as Dexeus, AXA, Cornerjob, Grifols & Carnovo.
Related Post: Back to the roots: towards true Continuous Integration
Insight: Stow is a symlink farm manager which takes distinct sets of software and/or data located in separate directories on the filesystem, and makes them all appear to be installed in a single directory tree. Stow was born to administer, upgrade, install, and remove files in independent software packages without confusing them with other files sharing the same file system space.
Related Post: Managing dotfiles with stow
Insight: Liquibase is an open-source database-independent library for tracking, managing and applying database schema changes. It allows to easily define changes in SQL, XML, JSON, or YAML. Also, it controls when, where, and how database changes are deployed.
Related Post: Liquibase on Kubernetes