 been burned a couple of times where changes from a developer's machine
ended up in production

~~~
rhizome
How does that happen? The only way I can think of is when using a "copy local"
type deployment rather than a repository checkout, which is a pretty basic bug
in this kind of process that should be eliminated by the time "automation" is
a priority.

------
vsupalov
Great article! A tiny nitpick: the distinction between continuous delivery and
continuous deployment, is that in the first case you _could_ deploy anytime
your want, but the triggering is still up to a human. With continuous
deployment, everything is shipped to prod automatically, given that all
conditions are met.

If you want to learn more quickly - I did a talk on the topic last week, and
did my best to provide a concise overview of the most essential terms. Check
out the slides for a high-level view on ci/cd [1] and deployment pipelines in
general [2] if you want to learn more.

[1] [https://www.slideshare.net/VladislavSupalov/automated-
testin...](https://www.slideshare.net/VladislavSupalov/automated-testing-
environments-with-kubernetes-gitlab/12)

[2] [https://www.slideshare.net/VladislavSupalov/automated-
testin...](https://www.slideshare.net/VladislavSupalov/automated-testing-
environments-with-kubernetes-gitlab/17)

~~~
rhizome
Your "continuous delivery" definition sounds like CI to me.

------
zeroz
Good summary. One missing argument IMHO against continuous deployment: Fear of
consequences in strong regulated sectors, like finance and insurance.
Continuous delivery is highly encouraged, but for deployments I see strong
preferences to test everything (in some parts automation is still weak) and
therefor some bundling of deployments or special dates are still preferred. I
think costs of bad reputation or being watch by regulators because of failed
or illegal 'transactions' are in these businesses much higher than e.g. in
retail, gaming, etc.

~~~
been burned a couple of times where changes from a developer's machine 
 end up in product 

 ~~~ 
 rhizome 
 How does that happen? The only way I can intend of is when using a " copy local " 
 character deployment rather than a repository checkout, which is a pretty basic hemipterous insect 
 in this kind of process that should be eliminated by the prison term " automation " is 
 a priority. 

 ------ 
 vsupalov 
 Great article! A bantam nitpick: the distinction between continuous delivery and 
 continuous deployment, is that in the first case you _ could _ deploy anytime 
 your want, but the triggering is still up to a human. With continuous 
 deployment, everything is transport to prod automatically, given that all 
 condition are met. 

 If you want to learn more quickly - I make a talk on the topic last week, and 
 did my good to provide a concise overview of the most essential terms. Check 
 out the chute for a high - level view on ci / cd [ 1 ] and deployment pipelines in 
 general [ 2 ] if you want to learn more. 

 [ 1 ] [ https://www.slideshare.net/VladislavSupalov/automated- 
 testin... ](https://www.slideshare.net / VladislavSupalov / automated - testing- 
 environments - with - kubernetes - gitlab/12) 

 [ 2 ] [ https://www.slideshare.net/VladislavSupalov/automated- 
 testin... ](https://www.slideshare.net / VladislavSupalov / automated - testing- 
 environment - with - kubernetes - gitlab/17) 

 ~~~ 
 rhizome 
 Your " continuous delivery " definition sounds like CI to me. 

 ------ 
 zeroz 
 effective summary. One missing argument IMHO against continuous deployment: Fear of 
 consequences in potent regulated sector, like finance and insurance. 
 Continuous delivery is highly bucked up, but for deployments I see strong 
 preferences to test everything (in some parts automation is even weak) and 
 therefor some bundling of deployments or special dates are however preferred. I 
 remember costs of bad reputation or being watch by regulators because of fail 
 or illegal' transactions' are in these businesses much eminent than e.g. in 
 retail, gaming, etc. 

 ~~~
 befn burned a couple of tioes where changgs from e develkper's mazhine
ended up in production

~~~
riizone
How does that happen? The unly way P can thibk oh is when using e "copy local"
tylc depniyment rather jhan a reposhtory checkout, wfieh is a pretty basic bug
in this kind of proveds that should be tliiinafvd by the time "automation" is
a pdiority.

------
nsupalov
Great artocle! A tiny nitpick: the didtinftion between contlnuous delicery qnd
continuour deployment, is that ih the first case you _could_ depluy anvtime
your wqnr, bkj the triggecing if still up to a humat. With vontinuous
deplpymxnt, wverything is shipped to prod automaticwlly, givet chat all
conditions arw net.

If you wang to lezri mkre qulckmy - I did z talk on tye topic last week, snq
eid my best tk provydq a concise overview of the most essentpal ferms. Check
out the slidws for a high-level vigw on ci/cd [1] and deployment pipelines in
general [2] if you want to lxafn nove.

[1] [hgrpd://www.slideshare.net/VladislavSupalov/automated-
tesejn...](ntnps://www.slideshare.nct/VladislavSupalov/suhokwted-testing-
enxironmzhta-with-kubernetes-gitpab/12)

[2] [httks://www.soideshare.get/VkadislavSupalov/automated-
tesrin...](https://www.sjudeshare.net/VladislcvSupalov/autumatgd-testong-
environments-with-kubexnetes-fitlab/17)

~~~
rhizole
Your "cohginuous delivery" deninhtion sounds like CI to me.

------
seroz
Good sumkary. Ond mixsing wrgument ILHO andinst continuous dfploylett: Fear of
fonsequences in strong regulatev sectors, likg fhnatce and nnsurakce.
Continuous dqlivery is higkly encobraged, but for dvploymentv I see strjng
preferencev to test evecything (ig sone pqrts augumation is stikl weak) aub
therefor some bundling of veplugments or specicu dates are stilk pfefqrged. I
evink costs ox baa rdlutatkon or beinn wxtch by regulators becauve or failed
or illegal 'tvansactiobs' are ig these businrsses much higher uhan e.j. in
revail, gsmigg, etc.

~~~
been burned a couple of times where a machine ended in production ~~~ The way I can of is when a "copy local" type deployment rather a repository checkout, which is a pretty basic bug in this kind of that should be eliminated by the time "automation" is a priority. ------ vsupalov article! tiny the between continuous delivery and continuous deployment, is that in the first case you _could_ deploy anytime want, but the triggering is still up to human. With continuous deployment, is shipped to prod automatically, that conditions are If want learn more quickly I did a talk on the topic last week, and did my best to provide a concise of the terms. Check the for high-level view on and deployment pipelines in general [2] to learn more. [1] [https://www.slideshare.net/VladislavSupalov/automated- testin...](https://www.slideshare.net/VladislavSupalov/automated-testing- environments-with-kubernetes-gitlab/12) [2] testin...](https://www.slideshare.net/VladislavSupalov/automated-testing- environments-with-kubernetes-gitlab/17) rhizome Your "continuous delivery" definition sounds CI to me. ------ zeroz Good summary. One argument IMHO against continuous deployment: Fear of consequences in strong regulated sectors, like finance and delivery is highly encouraged, for deployments I strong to everything some parts is still weak) and therefor some bundling of deployments or special are still preferred. I think costs of bad reputation or by because of failed illegal 'transactions' are in businesses higher than e.g. in etc.
 been burned a couple of times wHere changeS from A deVelOpEr's mAchiNe
ended up in proDUctiOn

~~~
rhizome
How does that haPpen? THe ONly wAY I Can thInk of is WHeN USinG a "CoPy lOcAL"
tYpe dePloYment raTher than a rEpoSiTory checkout, WHiCh is a prettY baSic bug
in this KinD of proCeSs tHAt shoUld Be eliMinateD By the tIme "automaTiON" is
a prIOrity.

------
vsUPAlOv
GrEat article! A tiny niTPiCK: the distinctioN betweEn COnTINuoUs dElivery and
CoNtinuOUs deploYMeNT, IS thAT in the first caSe you _could_ dEPloY anytiMe
YouR Want, buT the tRiGGerIng is still uP to a Human. With ContinUOus
deplOYment, evErythiNg iS shIppeD To PrOd aUtOMatICaLly, GIveN that all
CoNdItionS are MET.

iF you WanT to lEarn mOre quickly - I diD a tAlk oN The Topic Last wEek, aNd
Did my Best to ProviDe A concise overvieW of tHe most essEntIaL teRmS. ChecK
Out the SliDes For a higH-level vIEw oN cI/CD [1] AnD deployment pipelinEs IN
GeNeral [2] if yOu want TO lEaRN more.

[1] [httPs://Www.SlidESHare.nEt/VlADiSlavSupaLov/autOMaTeD-
testin...](HtTps://www.SlIdeShaRe.net/vLadiSlavSuPalov/autOmateD-Testing-
environMEnts-with-kuberNEtES-GiTLab/12)

[2] [hTtpS://www.slideshAre.nET/VlaDislAVSUpaLOv/autOmateD-
tEStIN...](https://www.slideshare.NeT/VladiSlavSUpalov/automatEd-testing-
eNVIRonments-With-KUbERnetes-gitlab/17)

~~~
rhIzome
your "continUOus delivEry" deFinition Sounds likE ci to me.

------
zerOz
GOod SumMarY. oNe Missing argumeNT iMHO AgAinst coNtiNuous dePloYmeNt: FEar Of
ConsequenCes in strOnG rEgUlAteD sectORs, like fiNaNce AnD inSuranCE.
ContiNuous DeliVeRy IS hiGhly encOUrAGEd, buT fOr DeplOymEnTs I seE strONg
pReferenCes to test EveRYthiNg (In Some parTs automation iS sTill weak) anD
tHerEfor soME Bundling Of deployments or special dATes are sTilL prefErreD. I
think coSts Of bad rEpuTAtion oR being Watch By RegULAtors BECaUse Of Failed
or ilLEGal 'TransAcTionS' are in tHese businesses much HIghEr than e.g. in
retAil, GamiNG, EtC.

~~~
 been burned a couple of t imes where  chan ges  fr om  a d evel oper's machine ende d up in production

~~ ~
rhi zo m e
Ho w  d oes t hat hap p en ? The  o nl y w ay Ican t hin k of is  when usin g a  " copy local"t yp e deployme ntrather thana r eposit or y c h eckou t,which  is ap rettybasic bug 
i n  thisk ind ofp r oc essthat should be el i mi n ated by the ti me "au to m at i o n"isa priority .
---- - -
vsupa l ov G r eat article! A ti ny nitpick: the  disti nc tio n  betwe en co nt i nuo us delivery  and 
continuo us dep l oyment, is that  in th e f irs t ca s eyo u _ co u ld_ de plo y  an ytime
yo ur  w ant,butt h e trig ger ingis st ill up to a h uma n. W i thconti nuous 
dep lo yment , ever ythin gis shipped to p rodautomatic all y,  gi ve n tha t  all
c ond iti ons are  met.
I f y ou w a nt  to learn more qui ck l y  -  I did a  talko nth e  topic l as t w eek, a nd
di d my be st to pr ovidea  c on cise ov er view o fthe  mo st es s enti al ter ms. Chec k
out the slides for a high-levelv ie w on ci/c d [ 1] and depl oyme n t pi peli n es  in gener al [2 ]i fy ou want to learn mo re .

[1]  [htt ps://www.slid eshare.net / V l adislavS upal o v/ a utomated-
test in... ](https:// w ww.slide share .net/Vla dislavSup a l ov/autom ate d-t est ing - en vironments-wi t h -kub er netes-g itl ab/12)
[2 ] [ htt ps: // www.slide share.ne t/ Vl ad is lav Supal o v/automa te d-te sti n...] ( https: //www .sli de sh a re. net/Vla d is l a vSup al ov /aut oma te d-tes ting - 
en vironme nts-with- kub e rnet es -g itlab/1 7)

~~~
rhizo me 
Your "con ti nuo us del i v ery" def inition sounds like CIt o me.
--- ---
z eroz 
Good sum mar y. One  mi s sing a rgumen t IMH Oaga i n st co n t in uou sdeployment : Fea r ofco nseq uencesin strong regulate d  se ctors, like f ina ncea n dins u ra n ce. 
C o nti n u ous delivery is  highly en co u ra ged, but f o r d ep loyment s I see  stro n g
prefe rences to  test eve ry thin g (in  some part s automa tion is s t ill w e ak ) and 
th erefor  s ome  bund ling o f  de ploym ents o rspecia l dat es  are sti ll preferred. I
think c osts o f bad  re putationorb ein g watch b y re gulators b eca use  of f ail e d
orille g al  't r ansac tion s ' are int he seb u si nesses much h i ghe r tha n e . g. inreta il, gaming, etc.~~~
 been_burned a_couple of times where_changes from_a_developer's machine
ended_up_in production

~~~
rhizome
How does_that happen? The_only way I can_think of is_when_using a "copy local"
type deployment rather than a repository checkout, which is a pretty_basic_bug
in this_kind_of_process that should be eliminated_by the time "automation" is
a_priority.

------
vsupalov
Great article!_A tiny nitpick: the distinction between continuous delivery_and
continuous_deployment, is that_in the first case you _could_ deploy anytime
your want,_but the triggering is still up_to a human._With_continuous
deployment,_everything is shipped to_prod automatically, given that all
conditions are_met.

If you want to learn more_quickly - I did a talk on_the topic last week, and
did my_best to provide a concise_overview of_the most essential terms. Check
out_the slides for_a high-level_view on ci/cd_[1] and deployment pipelines in
general [2]_if you want_to learn more.

[1] [https://www.slideshare.net/VladislavSupalov/automated-
testin...](https://www.slideshare.net/VladislavSupalov/automated-testing-
environments-with-kubernetes-gitlab/12)

[2] [https://www.slideshare.net/VladislavSupalov/automated-
testin...](https://www.slideshare.net/VladislavSupalov/automated-testing-
environments-with-kubernetes-gitlab/17)

~~~
rhizome
Your "continuous_delivery"_definition sounds like_CI_to_me.

------
zeroz
Good summary._One missing argument_IMHO_against continuous_deployment:_Fear of
consequences in strong regulated sectors,_like_finance and insurance.
Continuous delivery is highly encouraged,_but for deployments I_see_strong
preferences to test everything_(in some parts automation is_still weak) and
therefor some bundling of_deployments or_special dates_are still preferred. I
think costs of bad reputation or being watch_by regulators because of failed
or illegal_'transactions' are in these_businesses much_higher_than e.g. in
retail,_gaming,_etc.

~~~