branching
 |
Code Integration: When Moving Slowly Actually Has More Risk Many decisions about code branching models are made in the name of managing risk, and teams sometimes pick models that make integration harder in the name of safety. Moving slowly and placing barriers to change can seem safer, but agile teams work best when they acknowledge that there is also risk in deferring change. |
|
 |
Using a Multibranch Jenkins Pipeline with Docker Typically, code for a Docker image is developed using multiple GitHub branches, with each branch being the code for a single Docker image tag. However, having to create and run a Jenkins pipeline for each GitHub branch can be cumbersome. Try a multibranch pipeline to integrate multiple GitHub branches simultaneously. |
|
 |
Feature Branching Is Not Evil Some people believe branching and pull requests are inherently bad. True, branching done poorly can slow down a team, but advocating for avoiding branching altogether can lead you to ignore the more important goal of an agile process: rapid integration of changes. First, make sure you're considering the right metrics. |
|
 |
Integrating Code in Agile Software Development: Start with the Goal in Mind Agile software development works because of continuous feedback at various levels, and the most important form of feedback is working software. One way to achieve rapid feedback is to integrate and deploy code frequently. Rather than starting with the process, first decide what "frequently" should mean for your team. |
|
 |
Choose Continuous Integration over Branching for Faster Feedback Continuous integration is the best way to get feedback often on the state of your project. Running automated builds and tests after each integration improves reliability and predictability. Consequently, using task and feature branches, while useful in some cases, can be a distraction and delay getting information. |
|
 |
Helpful Tips for Good Branching and Merging in Product Development Branching and merging are necessary, but they can be minimized to reduce the overhead. In this story, Joe Farah shares several helpful branching and merging tips as well as his simple philosophy of creating a new branch when you need to support the old one. |
|
 |
Branching Is Not Just for Version Control Joe Farah explains to us that a branching strategy is central to a configuration management (CM) plan and that it extends beyond version control. Remember, It's not just the files that need to be organized, it's the entire CM and application lifecycle management (ALM) data repository. |
|
 |
Should Agile Teams Minimize Branching? Steve Berczuk explains that developers are most interested in whether or not an SCM tool is capable of branching, thus allowing more than one related stream of code to evolve in parallel. However, minimizing branching may be the best approach for agile teams. |
