43:(also abbreviated CD), a similar approach in which software functionalities are also frequently delivered and deemed to be potentially capable of being deployed, but are actually not deployed. As such, continuous deployment can be viewed as a more complete form of automation than continuous delivery.
296:
Continuous deployment is the natural outcome of continuous delivery done well. Eventually, the manual approval delivers little or no value and is merely slowly things down. At that point, it is done away with and continuous delivery becomes continuous
64:
provide the functionality, and where the microservices can have multiple instances, continuous deployment consists of instantiating the new version of a microservice and retiring the old version once it has drained all the requests in flight.
51:
A major motivation for continuous deployment is that deploying software into the field more often makes it easier to find, catch, and fix bugs. A bug is easier to fix when it comes from code deployed five minutes ago instead of five days ago.
166:
Holmstrom Olsson, Helena; Alahyari, Hiva; Bosch, Jan (2012). "Climbing the "Stairway to Heaven" -- A Mulitiple-Case Study
Exploring Barriers in the Transition from Agile Development towards Continuous Deployment of Software".
113:
Shahin, Mojtaba; Ali Babara, Muhammad; Zhu, Liming (2017). "Continuous
Integration, Delivery and Deployment: A Systematic Review on Approaches, Tools, Challenges and Practices".
239:
Shahin, Mojtaba; Babar, Muhammad Ali; Zahedi, Mansooreh; Zhu, Liming (2017). "Beyond
Continuous Delivery: An Empirical Investigation of Continuous Deployment Challenges".
212:
Claps, Gerry Gerard; Berntsson
Svenssonb, Richard; Aurum, Aybüke (2014). "On the journey to continuous deployment: Technical and social challenges along the way".
434:
256:
188:
382:
404:
27:
93:
439:
78:
172:
337:
132:
82:
39:
31:
262:
194:
148:
122:
355:
252:
241:
2017 ACM/IEEE International
Symposium on Empirical Software Engineering and Measurement (ESEM)
184:
345:
244:
221:
176:
140:
374:
350:
325:
341:
280:
136:
88:
428:
61:
198:
152:
266:
225:
30:
in which software functionalities are delivered frequently and through automated
169:
2012 38th
Euromicro Conference on Software Engineering and Advanced Applications
144:
359:
248:
180:
326:"A development process of enterprise applications with microservices"
127:
85:, or (less often) continuous integration and continuous deployment
74:
284:
311:Continuous Integration, Delivery, and Deployment
77:, the combined practices of either (more often)
8:
281:"Continuous Deployment: An Essential Guide"
405:"What you should know about microservices"
349:
126:
60:In an environment in which data-centric
105:
330:Journal of Physics: Conference Series
37:Continuous deployment contrasts with
7:
214:Information and Software Technology
14:
375:"Data-centric Software Manifesto"
385:from the original on 2019-10-14
351:10.1088/1742-6596/1126/1/012017
16:A software engineering approach
403:Butler, Brandon (2016-11-09).
1:
28:software engineering approach
435:Software development process
226:10.1016/j.infsof.2014.07.009
324:Vera-Rivera, F. H. (2018).
145:10.1109/ACCESS.2017.2685629
456:
373:Serlet, Bertrand (2019).
309:Rossel, Sander (2017).
79:continuous integration
173:IEEE Computer Society
94:Blue–green deployment
20:Continuous deployment
249:10.1109/ESEM.2017.18
243:. pp. 111–120.
181:10.1109/SEAA.2012.54
175:. pp. 392–399.
342:2018JPhCS1126a2017V
137:2017arXiv170307019S
83:continuous delivery
40:continuous delivery
258:978-1-5090-4039-1
190:978-0-7695-4790-9
447:
440:Software release
419:
418:
416:
415:
400:
394:
393:
391:
390:
370:
364:
363:
353:
321:
315:
314:
306:
300:
299:
293:
292:
277:
271:
270:
236:
230:
229:
209:
203:
202:
163:
157:
156:
130:
110:
455:
454:
450:
449:
448:
446:
445:
444:
425:
424:
423:
422:
413:
411:
402:
401:
397:
388:
386:
372:
371:
367:
323:
322:
318:
308:
307:
303:
290:
288:
279:
278:
274:
259:
238:
237:
233:
211:
210:
206:
191:
165:
164:
160:
112:
111:
107:
102:
71:
58:
49:
17:
12:
11:
5:
453:
451:
443:
442:
437:
427:
426:
421:
420:
395:
365:
316:
301:
272:
257:
231:
204:
189:
158:
104:
103:
101:
98:
97:
96:
91:
89:Canary release
86:
70:
67:
57:
54:
48:
45:
15:
13:
10:
9:
6:
4:
3:
2:
452:
441:
438:
436:
433:
432:
430:
410:
409:Computerworld
406:
399:
396:
384:
380:
376:
369:
366:
361:
357:
352:
347:
343:
339:
336:(1): 012017.
335:
331:
327:
320:
317:
312:
305:
302:
298:
286:
282:
276:
273:
268:
264:
260:
254:
250:
246:
242:
235:
232:
227:
223:
219:
215:
208:
205:
200:
196:
192:
186:
182:
178:
174:
170:
162:
159:
154:
150:
146:
142:
138:
134:
129:
124:
121:: 3909–3943.
120:
116:
109:
106:
99:
95:
92:
90:
87:
84:
80:
76:
73:
72:
68:
66:
63:
62:microservices
55:
53:
46:
44:
42:
41:
35:
33:
29:
25:
21:
412:. Retrieved
408:
398:
387:. Retrieved
378:
368:
333:
329:
319:
310:
304:
295:
289:. Retrieved
287:. 2019-10-02
275:
240:
234:
217:
213:
207:
168:
161:
118:
114:
108:
59:
50:
38:
36:
23:
19:
18:
297:deployment.
115:IEEE Access
32:deployments
429:Categories
414:2019-10-14
389:2019-10-14
291:2022-11-28
128:1703.07019
100:References
47:Motivation
360:1742-6596
220:: 21–31.
383:Archived
379:Fungible
199:15199568
153:11638909
69:See also
338:Bibcode
267:3479812
133:Bibcode
56:Example
26:) is a
358:
265:
255:
197:
187:
151:
263:S2CID
195:S2CID
149:S2CID
123:arXiv
75:CI/CD
356:ISSN
334:1126
253:ISBN
185:ISBN
81:and
346:doi
285:IBM
245:doi
222:doi
177:doi
141:doi
431::
407:.
381:.
377:.
354:.
344:.
332:.
328:.
294:.
283:.
261:.
251:.
218:57
216:.
193:.
183:.
171:.
147:.
139:.
131:.
117:.
34:.
24:CD
417:.
392:.
362:.
348::
340::
313:.
269:.
247::
228:.
224::
201:.
179::
155:.
143::
135::
125::
119:5
22:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.