This post is from the CollabNet VersionOne blog and has not been updated since the original publish date.
Exploring Task-based CI with SVN and Git
CI is frequently implemented as a dev process and not tied to the rest of the software development life cycle, resulting in a lack of real time visibility across all stakeholders at the project level. Simply moving CI away from an isolated dev discipline is difficult, let alone scaling CI across an enterprise.
One major challenge is achieving the high frequency of integrations while tying the CI process to the business needs and ensuring functional completeness, such as features that span multiple builds.
Other challenges in scaling CI are governance and Ops. CI tooling and adoption is often driven at team level, resulting in ungoverned CI tooling and lost productivity as teams take spend time establishing and maintaining CI environments.
In this 30 minute webinar, we’ll present solutions for overcoming these challenges, by coupling the CI process with delivery of functionally complete stories–as defined by the business.
Concepts of Task-based CI approach
Utilizing story and feature branches
Triggering Jenkins builds base on task or story status
Demonstration of enterprise-grade Jenkins solution utilizing TeamForge
View these related resources on “Scaling CI/CD & DevOps Across the Enterprise”
Nov 25 – Enterprise CI As-A-Service with Jenkins (register here)