Continuous delivery requires constant infrastructure evolution

Continuous delivery requires constant infrastructure evolution

Continuous delivery requires constant infrastructure evolution

Date: Sep 12, 2013

Continuous integration tools let application developers go from short release cycles to a smooth stream of constant improvements. Serving up the infrastructure to properly test and deploy those integrations is no trivial matter. At Agile 2013, Michael Ducy, an enterprise architect at OpsCode, explained how Chef can help.

"We call it infrastructure as code," said Ducy, "Essentially you should be able to define how your infrastructure should look in code." Once the code is checked in through something like Jenkins, Chef kicks in to dynamically build a testing environment. It then runs tests, gathers results and tears the testing environments back down again. "As your application goes through its development cycle," Ducy said, "you can have your infrastructure go through the same cycle as well and ensure that your infrastructure changes in sync with your application changes."

View the next item in this Essential Guide: Agile PPM tools from CA Technologies on display at Agile 2013 or view the full guide: Agile 2013 Conference coverage

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to: