DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones AWS Cloud
by AWS Developer Relations
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones
AWS Cloud
by AWS Developer Relations
Securing Your Software Supply Chain with JFrog and Azure
Register Today

Trending

  • Cucumber Selenium Tutorial: A Comprehensive Guide With Examples and Best Practices
  • 5 Key Concepts for MQTT Broker in Sparkplug Specification
  • Getting Started With the YugabyteDB Managed REST API
  • 10 Traits That Separate the Best Devs From the Crowd

Trending

  • Cucumber Selenium Tutorial: A Comprehensive Guide With Examples and Best Practices
  • 5 Key Concepts for MQTT Broker in Sparkplug Specification
  • Getting Started With the YugabyteDB Managed REST API
  • 10 Traits That Separate the Best Devs From the Crowd
  1. DZone
  2. Testing, Deployment, and Maintenance
  3. Deployment
  4. Continuous integration versus delayed integration

Continuous integration versus delayed integration

Michael Mainguy user avatar by
Michael Mainguy
·
Apr. 17, 14 · Interview
Like (0)
Save
Tweet
Share
10.59K Views

Join the DZone community and get the full member experience.

Join For Free

A vigorous area of debate in the development and architecture community exists around the value of Continuous Integration. To give context, when a software development team gets to a certain amount of concurrent work that involves multiple teams making changes in the same codebase, there are two main ways to handle this:

  • Each individual stream of work take a copy of the code and start working on their own
  • Each team coordinate all work streams within the same codebase

In my experience, the former method seems like a great idea, especially when folks start worrying about "what happens when project A impacts project B's timeline?". Everybody just works on your own feature and at the end of each team's work stream, just merge all the individual team's efforts back together in a shared location. The great advantage here is that if Feature A is pulled from the delivery, Feature B can be deployed independently. What is frequently overlooked is the fact that eventually, Features A and B still need to be mixed together. The longer we wait to do this, the greater the risk of integration problems and the less time we have to resolve them.

On the other hand, having everybody pushing work into the same development stream immediately introduces some problems that need to be resolved at build time. It's immediately necessary to have a process to allow reconciling competing Features and disable features should it not be complete before delivery. The major downside continuous (or at least frequent) integration is that individual developers and Feature teams are a bit slower day to day as they uncover unanticipated problems due to competing requirements in the various work streams, but the upside is that these are discovered early in the process instead of at a very late stage.

In short, delayed integration doesn't actually save any time in the long run as the will eventually still manifest themselves, just later in the process when you have less time to fix them. To all folks doing multi-stream development, seriously investigate limiting your work to "one branch per environment", and work out how to independently configure the environments to know which features they should enable.

Integration Continuous Integration/Deployment

Published at DZone with permission of Michael Mainguy, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Trending

  • Cucumber Selenium Tutorial: A Comprehensive Guide With Examples and Best Practices
  • 5 Key Concepts for MQTT Broker in Sparkplug Specification
  • Getting Started With the YugabyteDB Managed REST API
  • 10 Traits That Separate the Best Devs From the Crowd

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com

Let's be friends: