Channels ▼


CircleCI Adds Docker For Continuous Delivery

CircleCI has announced support for Continuous Delivery using Docker containers. The Continuous Integration and Continuous Delivery company reminds us that application containers have emerged as an (arguably) essential solution for developers to provide a more flexible way to build and deploy applications.

The firm says that its support for Docker containers allows developers to build and deploy containers as part of the Continuous Delivery workflow, letting them ship software faster and far more easily at scale.

"Docker is exciting," said Paul Biggar, cofounder and CEO of CircleCI. "Development speed is critical in today's competitive development landscape, and maintaining this speed is difficult as apps grow larger and more complex. By deploying via Docker on CircleCI, our customers can deploy more resilient apps with a higher velocity."

Automating software delivery using CircleCI is (if all the cogs and processes connect correctly) a process that should give developers speedier productivity and better software quality.

"CircleCI's fast, scalable Continuous Integration and Continuous Delivery service frees developers from building and maintaining their own infrastructure and allows them to focus on their core product," said Biggar.

Docker containers let programmers remove almost all of the variables that differ between test and production environments. You can specify everything from your Linux distro to what executables run at startup in a Dockerfile, build all of that information into a Docker image, test it, and deploy the exact same image byte-for-byte to production — you can now run this entire process on CircleCI.

Related Reading

More Insights

Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.