continuous integration | TechWell

continuous integration

Software engineer looking at her computer monitors and integrating code 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.

Steve Berczuk's picture
Steve Berczuk
Looking at code through eyeglasses Fearless Refactoring, Not Reckless Refactoring

Fearless refactoring is the agile concept that a developer should be able to incrementally change code without worrying about breaking it. But it's not believing that you don't need a safety net to detect and correct defects quickly when changes are made—that's just reckless. Here's how to avoid reckless refactoring.

Jeffery Payne's picture
Jeffery Payne
Repeating geometric pattern Achieve Repeatable Builds with Continuous Integration

Continuous integration is essential to provide the feedback needed to keep a team’s code agile. One crucial aspect to a successful CI process is a repeatable build. There are two parts to maintaining a repeatable build: the idioms and practices to define it, and the feedback cycle to maintain it. Here's what you need.

Steve Berczuk's picture
Steve Berczuk
Colorful gears automating processes Continuous Automation, from Source Code to Production

Automation is necessary to achieve the benefits of DevOps principles, so teams may use automation at every step of software development. Depending on how frequently and confidently a team deploys code, they can use automation to enable continuous integration, continuous delivery, and, finally, continuous deployment.

Deepak Vohra's picture
Deepak Vohra
Infinity sign made with a sparkler Key Enablers for Continuous Testing

Continuous testing means testing before, during, and after each software change is made. Testers have long advocated for this, but DevOps has made it more popular by pushing for rapid feedback and shifting testing left in the lifecycle. Here are three practices your company should embrace to enable continuous testing.

Max Saperstone's picture
Max Saperstone
Mobile app icons on a phone A DevOps Approach to Mobile App Development

DevOps has completely transformed the mobile app development scenario, and it’s a good choice for any business looking to create an app. Let's look at what DevOps means in the context of developing a mobile app, some of the key benefits of a DevOps approach, and five crucial factors to keep in mind during development.

Juned Ghanchi's picture
Juned Ghanchi
Lisa Crispin Testing in DevOps: A Slack Takeover with Lisa Crispin

Thought leaders from the software community are taking over the TechWell Hub to answer questions and engage in conversations. Lisa Crispin, who's created many educational materials for software professionals, hosted this Slack takeover and discussed DevOps, test automation skills for manual testers, and starting TDD.

Kelly McGee's picture
Kelly McGee
Long-exposure shot of cars racing along a highway DevOps Isn’t Just about Releasing Faster

When organizations start moving to DevOps, one of the first things they focus on is automation. It makes sense: Automated deployment tools are easy to explain, and implementing them usually shows value right away. But speed isn’t the only (or even the best) reason to move to DevOps and an automated release pipeline.

Gene Gotimer's picture
Gene Gotimer