Continuous Delivery is an emerging area of software development, which takes continuous integration one step further. Software teams practicing continuous delivery create build pipelines that enable them to integrate, test, and deploy their software products with high frequency.

learn more… | top users | synonyms

16
votes
6answers
2k views

How can Continuous Delivery work in practice?

Continuous Delivery sounds good, but my years of software development experience suggest that in practice it can't work. (Edit: To make it clear, I always have lots of tests running automatically. ...
14
votes
4answers
336 views

At what point should you switch to release build?

One of the practices set out in Jez Humble's Continuous Delivery is that you should build one package and then release it to each environment you deploy to, so that the deployment and the artifacts ...
12
votes
4answers
849 views

How do I learn the right approach to implement half a feature?

I lead a development team and I want to release our product as often as possible (Continuous Delivery). In many cases, we have to implement a feature that takes longer to implement than the time ...
6
votes
5answers
1k views

“Release Early Release Often” for Android and iPhone Apps

I wanted to know the experiences others have about doing the Agile way of "Release Early, Release Often" with iPhone and Android Apps. Its not a problem with webapps as the update happens at the ...
6
votes
3answers
719 views

How do I structure code and builds for continuous delivery of multiple applications in a small team?

Background: 3-5 developers supporting (and building new) internal applications for a non-software company. We use TFS although I don't think that matters much for my question. I want to be able to ...
5
votes
2answers
1k views

Why is build.number an “abuse” of semantic versioning?

I was explaining a proposed build system (Gradle/Artifactory/Jenkins/Chef) to one of our senior architects, and he made a comment to me that I sort of disagree with, but am not experienced enough to ...
5
votes
1answer
147 views

What are the advantages of continuous deployment? [closed]

Continuous deployment require a lot of effort, beyond what is needed for continuous integration. Since every change corresponds to a release (more or less), there is far less time and resources ...
4
votes
4answers
2k views

How to implement Continuous Delivery with Java webapp?

I've been reading about Continuous Delivery and it sounds awesome to automate the deployment process. I've been reading about possibilities how to do this with Java Webapps, but usually it ends up ...
4
votes
2answers
221 views

How to communicate within a company what is being Continually Deployed

I work for a small development company, 20 people total in the entire company, 3 in actual development, and we've adopted CD for our commits to trunk, and it works great, from a code management and ...
3
votes
4answers
363 views

Why does CI stipulate that we should be able to rollback to any version of a software?

I was reading the book "Continuous delivery, reliable software deployments through build, tests and deployment automation ". And the author mentions that one should be able to rollback to any version ...
3
votes
6answers
542 views

Which deployment technologies makes sense in Continuous Deployment?

In my understanding a major point in Continuous Deployment is (well, obviously I guess) that deployment is automatically done as a part of the building process. Conceptually it is easy to understand ...
3
votes
2answers
151 views

Tracking internal builds versus public builds

At our office, we use JIRA to track issues reported by our QA teams. We also have Bamboo which builds each time we commit to our Git (Stash) repository. QA picks a build from Bamboo and they work with ...
2
votes
3answers
685 views

Continous Delivery TFS

Is it possible to achieve Continuous Delivery using TFS e.g. Windows Service? There are > 1000 posts on how to use msdeploy with TFS for WEB projects. I am trying to understand why there are no ...
2
votes
1answer
71 views

How to manage a single branch

I read the Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation book by Jez Humble and David Farley. The part that throw me off balance the most was their ...
2
votes
0answers
50 views

DB migration and Azure deployment slots

I'm planning to push a new web application to an Azure Web Service (former Azure Website). I'd like to make use of the deployment slots to be able to test my deployment before pushing it to ...
2
votes
0answers
53 views

Is using partial classes for supporting multiple versions of data entities for continuous delivery scenarios a bad idea?

When you want to have continuous delivery any data schemas that you have must support multiple versions of your application at the same time (as you may have multiple version deployed when new ...
1
vote
2answers
89 views

What is Quality Assurance's role in a company that practices Continuous Delivery?

I was listening to this podcast on Continuous Delivery and Jez Humble briefly talked about QA's role, but I didn't really get a "big picture" idea of they're doing on a day to day basis. How is their ...
1
vote
1answer
73 views

We'd like to release only the services that have changed, in a continuous delivery context. How would we do that?

I am new to continuous delivery, so please help me understand if my ideas are incorrect, I have XY problems, etc.. My organization runs web services, with services-oriented architecture. Currently, ...
1
vote
2answers
111 views

Client / Server dependencies with Continuous Integration

I'm starting to use continuous integration for one of my projects and had some questions about structure and architecture. It's basically a multi-device webservice that is split into one server ...
1
vote
1answer
185 views

Can continuous delivery work in a big enterprise environment with lots of connected systems?

Much has been said lately of continuous delivery. It does sound appealing, but runs against the grain of convention wisdom in big corporations. Jez Humble - Continuous Delivery Thoughtworks ...
0
votes
2answers
175 views

Continuous Integration / Deployment: Test on commit, pull request, or what?

I read about CI/CD, loved it, but I'm having trouble with the details as everything I read was high level. Some authors seemed to suggest that there couldn't be any failing commits on the repository ...
0
votes
2answers
461 views

Continuous Delivery: Kanban, SCRUM, or other?

I was wondering if there was an SDLC (software development lifecycle) or methodology (Kanban, SCRUM, waterfall, otherwise, etc.) that was particularly well-suited for continuous delivery systems, and ...
0
votes
2answers
264 views

Strategy for storing passwords/credentials in the context of continuous delivery [closed]

It is common sense not to store passwords/credentials into SCM. I would like to know then what would be a good strategy for storing passwords/credentials in the context of continuous delivery. ...
-1
votes
1answer
38 views

A good workflow to start with Continuous Delivery?

My team is facing a couple of new challanges in the near future, as we will start developing a couple of (micro)services which will run in a cloud environment. Therefore we want to establish a ...
-1
votes
0answers
18 views

Concepts and terminology for deploying applications and components with complex dependencies for CI and CD? [on hold]

As an example, consider several applications appA, appB, and appC, all of which depend on a shared database DB. I'd like to be able to handle deploying: appA by itself appA and appB together DB by ...
-2
votes
1answer
57 views

Managing deployment scripts in the process of continuous delivery

My question concerns deployment scripts in the process of continuous delivery. Continuous delivery recommends that deployment scripts should be versioned into SCM just as normal code. What is the ...