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.
Questions tagged [continuous-delivery]
116 questions
51
votes
7 answers
TODO comments with deadlines?
Background
I'm working in a team that's looking to implement zero-downtime deployments. We're planning on using a blue/green deployment strategy in order to achieve this. One of the things I'm realising in doing the research is how complicated it…
Joshua Walsh
- 565
- 4
- 8
50
votes
2 answers
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 really weigh-in on.
This project builds a Java…
herpylderp
- 2,017
- 3
- 21
- 27
26
votes
5 answers
Whats the difference between staging and UAT environments?
I know we should have at least 3 different environments while developing a solution:
Development: The programmers are free to change and push changes any time in order to quickly test their code and integrate with other changes, without the fear of…
Machado
- 4,090
- 3
- 25
- 37
24
votes
2 answers
Is it good practice to store software version numbers in VCS?
A product version, such as v1.0.0.100, represents not only a unique production release of software, but helps identify feature sets and hotfix stages for said product. Right now I see two ways to maintain the final package/build/binary version of a…
void.pointer
- 4,983
- 8
- 30
- 40
24
votes
6 answers
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. My question is about how to get the confidence to…
Joshua Fox
- 1,090
- 10
- 18
17
votes
4 answers
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 have themselves been tested multiple times before…
pdr
- 53,387
- 14
- 137
- 224
16
votes
2 answers
DB migration and Azure deployment slots
I'm planning to push a new web application to an Azure Web App 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 production.
That's all fine as long as there is no DB…
Sam7
- 277
- 3
- 6
12
votes
3 answers
Build automation vs deploy automation vs continuous integration
I want to become more efficient and I want to use ops tools efficiently.
With this in mind, I wanted to learn more about continuous integration, but it seems that there is many different things concerning it.
I m actually working with Jetbrains…
mfrachet
- 1,481
- 3
- 15
- 21
12
votes
4 answers
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 between releases. I still want people to commit their…
Niels Brinch
- 321
- 1
- 10
10
votes
2 answers
How to test configuration changes in a service?
What is the best approach to testing a service when you add a new configuration?
For example my service offers a service to a customer and based on the customer configuration, it will offer a different type of service. E.g. if the customer selects a…
Noel
9
votes
5 answers
Which comes first: CD/Trunk-based development or microservices?
My company* wants
to move from using long-running feature branching (~up to a few weeks) to continuous integration with trunk-based development, and
to break up our monolith into microservices.
We're unsure which to do first to best achieve both:…
Jacob Archambault
- 209
- 2
- 7
8
votes
3 answers
Is it a good idea to lock svn
I have to define the new way of working for a development team which goes from a one man unit, to a distributed team with programmers al over the world. The team will work with svn. This is a non-negotiable thing. I recommended that they switch from…
Cecil Westerhof
- 139
- 7
8
votes
1 answer
shared CD (Continuous Deployment) for multiple Git repositories
Long story short
What is the best way to design a shared CD for multiple Git repositories (frontend and backend)?
I'm struggling to find the best design for our CD.
The whole picture (The details can be changed)
Frontend - Angular 2 (Javascript),…
Stav Alfi
- 297
- 3
- 10
8
votes
4 answers
What does "continuous" mean in "continuous deployment", "continuous delivery" and "continuous integration"?
What does "continuous" mean in "continuous deployment", "continuous delivery" and "continuous integration"?
What is it opposed to?
Does "continuous" make "deployment", "delivery" and "integration" do more things than without "continuous"?
Tim
- 5,405
- 7
- 48
- 84
8
votes
3 answers
How to rollback rejected features by QA in a Continuous Delivery scenario?
As I am looking more and more into Continuous Delivery for our organisation, I struggle to understand how we can effectively incorporate manual QA testing before a release is pushed out into production.
I have found multiple approaches, such as the…
Jensen
- 187
- 1
- 6