{"id":32497,"date":"2019-10-31T21:47:23","date_gmt":"2019-10-31T18:47:23","guid":{"rendered":"https:\/\/prohoster.info\/blog\/devopsforum-2019-vnedryat-devops-nelzya-zhdat\/"},"modified":"2019-10-31T21:47:23","modified_gmt":"2019-10-31T18:47:23","slug":"devopsforum-2019-vnedryat-devops-nelzya-zhdat","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/devopsforum-2019-vnedryat-devops-nelzya-zhdat","title":{"rendered":"DevOpsForum 2019. Duhet t\u00eb implementohet DevOps pa pritur","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

S\u00eb fundmi, kam marr\u00eb pjes\u00eb n\u00eb DevOpsForum 2019, t\u00eb organizuar nga Logrocon. N\u00eb k\u00ebt\u00eb konferenc\u00eb, pjes\u00ebmarr\u00ebsit p\u00ebrpiqeshin t\u00eb gjenin zgjidhje dhe mjete t\u00eb reja p\u00ebr nj\u00eb bashk\u00ebpunim efektiv mes bizneseve dhe specialist\u00ebve t\u00eb zhvillimit dhe sh\u00ebrbimeve teknologjike.<\/p>\n

\"DevOpsForum
\n
\nKonferenca ishte e suksesshme: kishte v\u00ebrtet shum\u00eb prezantime t\u00eb dobishme, formate interesante t\u00eb fjalimeve dhe shum\u00eb biseda me fol\u00ebsit. Dhe ve\u00e7an\u00ebrisht e r\u00ebnd\u00ebsishme ishte se askush nuk p\u00ebrpiqej t\u00eb m\u00eb shiste ndonj\u00eb gj\u00eb, gj\u00eb q\u00eb \u00ebsht\u00eb b\u00ebr\u00eb e zakonshme n\u00eb konferencat e m\u00ebdha koh\u00ebve t\u00eb fundit.<\/p>\n

P\u00ebrmbledhje nga prezantimet e Raiffeisen Bank, Alpha Insurance, p\u00ebrvoja e Mango Telecom n\u00eb zbatimin e automatizimit dhe detaje t\u00eb tjera m\u00eb posht\u00eb. <\/a><\/noindex><\/p>\n

M\u00eb quajn\u00eb Yana, punoj si testuese, merrem me automatizim, si dhe DevOps dhe e adhuroj t\u00eb shkoj n\u00eb konferenca dhe meetupa. Gjat\u00eb dy viteve t\u00eb fundit kam qen\u00eb n\u00eb konferencat e Oleg Bunin (HighLoad++, TeamLead Conf), n\u00eb ngjarjet Jug (Heisenbug, JPoint), n\u00eb TestCon Moscow, DevOps Pro Moscow, Big Data Moscow. <\/p>\n

Gj\u00ebja e par\u00eb q\u00eb e v\u00eb re \u00ebsht\u00eb programu i konferenc\u00ebs. N\u00eb nj\u00eb far\u00eb mase, shoh se p\u00ebr \u00e7far\u00eb do t\u00eb flitet, por n\u00eb mas\u00eb m\u00eb t\u00eb madhe, shoh fol\u00ebsin. Edhe n\u00ebse prezantimi del t\u00eb jet\u00eb shum\u00eb teknologjik dhe interesant, nuk ka garanci q\u00eb do t\u00eb mund t\u00eb aplikosh ndonj\u00eb praktik\u00eb t\u00eb mir\u00eb nga ai prezantim n\u00eb kompanin\u00eb t\u00ebnde. Dhe at\u00ebher\u00eb, t\u00eb nevojitet nj\u00eb fol\u00ebs.\n<\/p><\/blockquote>\n

Drita n\u00eb fund t\u00eb pipeline n\u00eb Raiffeisen Bank<\/h2>\n

\nZakonisht, organizoj nj\u00eb p\u00ebrndjekje p\u00ebr fol\u00ebsit interesante p\u00ebr mua n\u00eb kuluar\u00eb. N\u00eb DevOpsForum 2019, n\u00eb qendr\u00ebn e interesit tim ra nj\u00eb fol\u00ebs nga Raiffeisen Bank - Mikhail Bijan. Gjat\u00eb prezantimit, ai tregoi se si ata gradualisht po e kalojn\u00eb ekipet e tyre n\u00eb DevOps, p\u00ebrse u nevojitet kjo dhe se si t\u00eb shesin iden\u00eb e transformimit DevOps n\u00eb biznes. Po ashtu, ai foli p\u00ebr se si t\u00eb shohim drit\u00ebn n\u00eb fund t\u00eb pipeline-it.<\/p>\n

\"DevOpsForum
\nMikhail Bijan, drejtor i automatizimit n\u00eb Raiffeisen Bank<\/i><\/p>\n

Tani n\u00eb kompanin\u00eb e tyre nuk ka \"trush DevOps\". Pra, \u00ebsht\u00eb real, por jo n\u00eb t\u00eb gjitha ekipet. Gjat\u00eb zbatimit t\u00eb DevOps, ata mb\u00ebshteten n\u00eb gatishm\u00ebrin\u00eb e ekipeve si nga pik\u00ebpamja e inxhinier\u00ebve konkret\u00eb ashtu edhe nga pik\u00ebpamja e nevojave t\u00eb produktit dhe pjekuris\u00eb s\u00eb platform\u00ebs mbi t\u00eb cil\u00ebn \u00ebsht\u00eb nd\u00ebrtuar ky produkt. Misha tregoi se si t'u shpjegosh biznesit pse u nevojitet DevOps. <\/p>\n

Sektori bankar ka disa motor\u00eb rritjeje: kostot e sh\u00ebrbimeve dhe zgjerimi i baz\u00ebs s\u00eb klient\u00ebve. Rritja e kostove t\u00eb sh\u00ebrbimeve nuk \u00ebsht\u00eb nj\u00eb motor shum\u00eb i mir\u00eb, nd\u00ebrsa rritja e baz\u00ebs s\u00eb klient\u00ebve \u00ebsht\u00eb e kund\u00ebrta. N\u00ebse konkurent\u00ebt nxjerrin nj\u00eb produkt objektivisht t\u00eb shk\u00eblqyer, t\u00eb gjith\u00eb klient\u00ebt shkojn\u00eb atje, pastaj me kalimin e koh\u00ebs tregu stabilizohet. Prandaj, lan\u00e7imi i produkteve t\u00eb reja dhe shpejt\u00ebsia e lan\u00e7imit t\u00eb tyre \u00ebsht\u00eb gj\u00ebja kryesore ndaj s\u00eb cil\u00ebs bankat orientohen. Pik\u00ebrisht p\u00ebr k\u00ebt\u00eb q\u00ebllim \u00ebsht\u00eb e nevojshme DevOps, dhe biznesi e kupton k\u00ebt\u00eb.<\/p>\n

Nj\u00eb v\u00ebrejtje tjet\u00ebr e r\u00ebnd\u00ebsishme: DevOps nuk i redukton gjithmon\u00eb koh\u00ebt p\u00ebr tregun. DevOps nuk mund t\u00eb punoj\u00eb vet\u00ebm, ai \u00ebsht\u00eb thjesht nj\u00eb pjes\u00eb e procesit t\u00eb krijimit dhe lan\u00e7imit t\u00eb produktit n\u00eb treg nga zhvillimi deri te prodhimi (nga kodi te klienti). Por gjith\u00e7ka para kodit, nuk ka t\u00eb b\u00ebj\u00eb drejtp\u00ebrdrejt me DevOps. Kjo do t\u00eb thot\u00eb se marketer\u00ebt mund t\u00eb studiojn\u00eb tregun p\u00ebr vite me radh\u00eb dhe t\u00eb mbajn\u00eb hapin me konkurent\u00ebt gjith\u00eb jet\u00ebn. \u00cbsht\u00eb e nevojshme t\u00eb kuptojm\u00eb shpejt se \u00e7far\u00eb d\u00ebshiron klienti dhe t\u00eb planifikojm\u00eb realizimin e ndonj\u00eb ve\u00e7orie - shpesh pik\u00ebrisht kjo u mungon q\u00eb DevOps t\u00eb funksionoj\u00eb dhe kompania t\u00eb arrij\u00eb q\u00ebllimin. Prandaj, fillimisht n\u00eb Raiffeisen Bank u dakordua me biznesin q\u00eb duhet t\u00eb m\u00ebsojn\u00eb t\u00eb p\u00ebrdorin DevOps. Automatizimi p\u00ebr hir t\u00eb automatizimit nuk do t\u00eb ndihmoj\u00eb shum\u00eb n\u00eb luft\u00ebn p\u00ebr klient\u00eb t\u00eb rinj.<\/p>\n

N\u00eb p\u00ebrgjith\u00ebsi, Misha mendon se DevOps duhet t\u00eb implementohet, por me arsyetim. Dhe duhet t\u00eb jesh i gatsh\u00ebm q\u00eb n\u00eb fillim t\u00eb transformimit, ekipi do t\u00eb ket\u00eb r\u00ebnie t\u00eb produktivitetit, do t\u00eb fitoj\u00eb m\u00eb pak para, por m\u00eb pas kjo do t\u00eb justifikohet.<\/p>\n

Automatizimi i testimit n\u00eb 'Mango Telecom'<\/h2>\n

\nNj\u00eb tjet\u00ebr paraqitje interesant p\u00ebr mua si testues ishte b\u00ebr\u00eb nga Egor Maslov nga \u00abMango Telecom\u00bb. Prezentimi titullohej \u00abAutomatizimi i ciklit t\u00eb plot\u00eb t\u00eb testimit n\u00eb ekipin SCRUM\u00bb. Egor beson se DevOps \u00ebsht\u00eb krijuar pik\u00ebrisht p\u00ebr SCRUM, por gjithashtu \u00ebsht\u00eb mjaft problematike t\u00eb implementosh DevOps n\u00eb nj\u00eb ekip SCRUM. Kjo ndodh sepse ekipi SCRUM gjithmon\u00eb \u00ebsht\u00eb n\u00eb nj\u00eb gar\u00eb, nuk ka koh\u00eb p\u00ebr t\u00eb theksuar risit\u00eb dhe p\u00ebr t\u00eb ristrukturuar procesin. Problemi \u00ebsht\u00eb gjithashtu se SCRUM nuk parashikon ndarjen e sub-ekipave n\u00eb ekip (ekipi i testuesve, ekipi i zhvilluesve dhe k\u00ebshtu me radh\u00eb). P\u00ebr m\u00eb tep\u00ebr, p\u00ebr t\u00eb automatizuar procesin ekzistues nevojitet dokumentacion, dhe n\u00eb SCRUM zakonisht dokumentacioni \u00ebsht\u00eb krejt\u00ebsisht i munguar \u2014 \u00abprodukti \u00ebsht\u00eb m\u00eb i r\u00ebnd\u00ebsish\u00ebm se ndonj\u00eb shkrim\u00bb.<\/p>\n

Pas kalimit n\u00eb SCRUM, testuesit filluan t\u00eb konsultoheshin me zhvilluesit se si t\u00eb testonin karakteristikat. Gradualisht, volumi i funksionaliteteve u rrit, dokumentacioni mungonte, dhe ata filluan t\u00eb zbulojn\u00eb shum\u00eb gabime n\u00eb funksionalitetet q\u00eb nuk kishin mbulim me teste dhe p\u00ebr m\u00eb tep\u00ebr nuk ishte e qart\u00eb kush dhe kur e kishte testuar at\u00eb. N\u00eb dy fjal\u00eb \u2014 kaos dhe shp\u00ebrndarje. Ata vendos\u00ebn t\u00eb kalonin n\u00eb automatizimin e testimit. Por edhe at\u00ebher\u00eb ndodhi nj\u00eb d\u00ebshtim total. Ata angazhuan specialist\u00eb t\u00eb jasht\u00ebm p\u00ebr automatizimin, t\u00eb cil\u00ebt shkruanin n\u00eb nj\u00eb stack t\u00eb panjohur p\u00ebr testuesit e brendsh\u00ebm. Framworku p\u00ebr testet automatike sigurisht funksionoi, por pasi q\u00eb specialist\u00ebt e jasht\u00ebm u larguan, ai jetoi vet\u00ebm dy jav\u00eb. Pastaj ishte p\u00ebrpjekja e dyt\u00eb p\u00ebr t\u00eb futur testimin automatizues. Ajo filloi me iden\u00eb se gjith\u00e7ka duhet t\u00eb nd\u00ebrtohet brenda kompanis\u00eb, me forcat e veta (direksioni i duhur: rritni ekspertiz\u00ebn brenda), n\u00eb kuad\u00ebr t\u00eb SCRUM, dhe gjat\u00eb procesit t\u00eb krijoni dokumentacion. Stack p\u00ebr automatizim duhet t\u00eb jet\u00eb i barabart\u00eb me stack-un e produktit (k\u00ebt\u00eb e mb\u00ebshtes fort, mos e testoni projektin n\u00eb JavaScript me di\u00e7ka tjet\u00ebr). N\u00eb fund t\u00eb sprintit, ata organizonin nj\u00eb demo se si funksiononte testi automatizues, me pjes\u00ebmarrjen e gjith\u00eb ekipit (e dobishme). N\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb, p\u00ebrfshirja e t\u00eb gjith\u00eb an\u00ebtar\u00ebve t\u00eb ekipit n\u00eb procesin e automatizimit u rrit, si dhe besimi n\u00eb testet automatizuese dhe mund\u00ebsia q\u00eb ky test automatizues do t\u00eb p\u00ebrdorej me siguri (nuk do t\u00eb ishte shenj\u00ebzuar pas nj\u00eb muaji p\u00ebr shkak t\u00eb d\u00ebshtimeve t\u00eb vazhdueshme).<\/p>\n

N\u00eb DevOpsForum 2019 kishte nj\u00eb mikrofon t\u00eb hapur \u2014 nj\u00eb format i njohur prej koh\u00ebsh dhe, sipas mendimit tim, shum\u00eb i dobish\u00ebm p\u00ebr l\u00ebshimin e fjalimeve. Ti shkon, d\u00ebgjon prezantimet dhe pastaj vendos se \u00ebsht\u00eb e nevojshme t\u00eb diskutosh nj\u00eb tem\u00eb ose problem brenda konferenc\u00ebs, duke ndar\u00eb p\u00ebrvoj\u00ebn relevante t\u00eb zgjidhjes s\u00eb detyrave.<\/p>\n

Gjithashtu, vura re se organizator\u00ebt kishin krijuar nj\u00eb rrjedh\u00eb prezantimesh t\u00eb shkurtra. \u00c7do prezantim zgjat jo m\u00eb shum\u00eb se 10 minuta, pastaj ndodhin pyetje. N\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb, mund t\u00eb kapesh me shum\u00eb tema dhe t'u drejtohesh pyetjeve fol\u00ebsve q\u00eb t\u00eb kan\u00eb interesuar.<\/p><\/blockquote>\n

\"DevOpsForum
\n\"DevOpsForum
\nMes prezantimeve, b\u00ebra nj\u00eb sh\u00ebtitje mes standeve t\u00eb partner\u00ebve t\u00eb konferenc\u00ebs dhe fitova shum\u00eb gj\u00ebra t\u00eb ndryshme. Ah, sa e dua ndarjen e materialeve!<\/i><\/p>\n

Tavolina e rrumbullak\u00ebt dhe pyetje DevOps me drejtorin p\u00ebr zhvillim n\u00eb Alfastosurance<\/h2>\n

\nKirshta mbi tort\u00ebn DevOpsForum 2019 p\u00ebr mua ishte nj\u00eb sesion plen i nj\u00eb ore me ekspert\u00ebt e DevOps. U ftuan kat\u00ebr pjes\u00ebmarr\u00ebs n\u00eb sesion, t\u00eb cil\u00ebt duhej t\u00eb shihnin DevOps nga k\u00ebndv\u00ebshtrime t\u00eb ndryshme: Anton Isanin (Alfastosurance, drejtor i zhvillimit), Nailya Zamashkina (Fintech Lab, drejtoresh\u00eb operative), Oleg Yegorkin (Rostelecom, trajner Agile) dhe Anton Martyjanov (ekspert i pavarur, q\u00eb e shikonte DevOps nga k\u00ebndv\u00ebshtrimi i biznesit). <\/p>\n

Ekspert\u00ebt u ul\u00ebn pran\u00eb publikut dhe k\u00ebtu filloi: p\u00ebr nj\u00eb or\u00eb t\u00eb t\u00ebr\u00eb pjes\u00ebmarr\u00ebsit nga salla i drejtonin pyetjet e tyre, nd\u00ebrsa ekspert\u00ebt u p\u00ebrball\u00ebn me to. Ndonj\u00ebher\u00eb, ndodhnin debate t\u00eb v\u00ebrteta. Pyetjet ishin nga m\u00eb t\u00eb ndryshmet, p\u00ebr shembull: a jan\u00eb t\u00eb nevojsh\u00ebm inxhinier\u00ebt DevOps, pse nuk mund t'i rrisim ata nga administratoret e sistemeve, duhet t'u ofrohet t\u00eb gjith\u00ebve DevOps, cil\u00ebsia e tij dhe k\u00ebshtu me radh\u00eb.<\/p>\n

M\u00eb pas, pata nj\u00eb bised\u00eb personale me Anton Isaninin. Diskutuam p\u00ebr nevoj\u00ebn p\u00ebr t\u00eb sjell\u00eb kultur\u00ebn DevOps n\u00eb \u00e7do sht\u00ebpi dhe zbuluam an\u00ebn e err\u00ebt t\u00eb transformimit DevOps.<\/p>\n

Supozoni q\u00eb t\u00eb gjith\u00eb u mblodh\u00ebn dhe vendos\u00ebn se DevOps \u00ebsht\u00eb i nevojsh\u00ebm si p\u00ebr produktin ashtu edhe p\u00ebr biznesin dhe ekipin. Filluam ta implementojm\u00eb. Gjith\u00e7ka shkoi mir\u00eb. U qet\u00ebsuam. DevOps na afroi me klientin, tani mund t\u00eb p\u00ebrmbushim shpejt t\u00eb gjitha k\u00ebrkesat e tij. N\u00eb fund t\u00eb fundit, kemi nj\u00eb departament t\u00eb madh Ops me rregulla t\u00eb rrepta dhe k\u00ebrkesa, dhe ai vazhdon t\u00eb d\u00ebrgoj\u00eb defekte n\u00eb produkt, duke krijuar shum\u00eb k\u00ebrkesa. Dhe t\u00eb gjitha defektet vijn\u00eb me statusin \" urgjent \", edhe n\u00ebse klienti papritmas d\u00ebshiron t\u00eb ngjyros\u00eb butonin n\u00eb t\u00eb verdh\u00eb n\u00eb vend t\u00eb gjelb\u00ebrt. Projekti rritet, numri i publikimeve rritet dhe p\u00ebr rrjedhoj\u00eb, rritet edhe numri i defekteve dhe moskuptimeve rreth funksionaliteteve t\u00eb reja nga klient\u00ebt. Ops angazhon edhe 10 njer\u00ebz p\u00ebr t\u00eb arritur t\u00eb raportojn\u00eb defektet, nd\u00ebrsa zhvillimi angazhon edhe 15, p\u00ebr t\u2019i mbyllur ato. Dhe n\u00eb vend q\u00eb t\u00eb implementojn\u00eb funksionalitete t\u00eb reja, ekipi punon me SD t\u00eb pafundme, duke shpjeguar funksionalitetet p\u00ebrdoruesit dhe gjithashtu mb\u00ebshtetjes. N\u00eb fund t\u00eb fundit, t\u00eb dy Ops dhe zhvillimi jan\u00eb t\u00eb angazhuar, por klienti dhe biznesi jan\u00eb t\u00eb pak\u00ebnaqur: funksionalitetet e reja ngecin. K\u00ebshtu q\u00eb, duket se ka DevOps, por gjithashtu nuk duket t\u00eb ket\u00eb.<\/p>\n

P\u00ebr domosdoshm\u00ebrin\u00eb e implementimit t\u00eb DevOps, Anton e deklaroi gjithashtu se kjo varet drejtp\u00ebrdrejt nga shkalla e biznesit. N\u00ebse sh\u00ebrbimi p\u00ebr nj\u00eb klient n\u00eb vit sjell nj\u00eb miliard p\u00ebr kompanin\u00eb \u2013 DevOps nuk \u00ebsht\u00eb i nevojsh\u00ebm (n\u00ebn kushtin se nuk ke nevoj\u00eb t\u00eb publikosh ndryshime t\u00eb reja p\u00ebr at\u00eb klient rregullisht). Gjith\u00e7ka \u00ebsht\u00eb n\u00eb rregull. Por n\u00ebse biznesi rritet, shfaqen m\u00eb shum\u00eb klient\u00eb, at\u00ebher\u00eb duhet t\u00eb p\u00ebrputhemi. Si rregull, nj\u00eb Ops i shk\u00eblqyer nuk ekziston fillimisht n\u00eb kompanin\u00eb. Fillimisht ne zhvillojm\u00eb produktin dhe m\u00eb pas kuptojm\u00eb se p\u00ebr t\u00eb funksionuar produkti, duhet t\u00eb mbajm\u00eb n\u00ebn mbik\u00ebqyrje, server\u00eb<\/a>, t\u00eb mbajm\u00eb n\u00ebn mbik\u00ebqyrje furnizimet. At\u00ebher\u00eb shfaqet Ops. Duhet t\u00eb kuptojm\u00eb se Ops, si nj\u00eb nj\u00ebsi e ve\u00e7ant\u00eb do t\u00eb filloj\u00eb t\u00eb vendos\u00eb shum\u00eb barriera p\u00ebr zhvillimin dhe t\u00eb gjitha furnizimet do t\u00eb fillojn\u00eb t\u00eb pengohen. Pra, n\u00eb k\u00ebt\u00eb rast kultura DevOps \u00ebsht\u00eb aktuale, vet\u00ebm duhet t\u00eb mos harrojm\u00eb an\u00ebn e saj t\u00eb err\u00ebt.
\n
Burimi: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u041d\u0435\u0434\u0430\u0432\u043d\u043e \u044f \u043f\u043e\u0431\u044b\u0432\u0430\u043b\u0430 \u043d\u0430 DevOpsForum 2019, \u043a\u043e\u0442\u043e\u0440\u0443\u044e \u0443\u0441\u0442\u0440\u0430\u0438\u0432\u0430\u043b Logrocon. \u041d\u0430 \u044d\u0442\u043e\u0439 \u043a\u043e\u043d\u0444\u0435\u0440\u0435\u043d\u0446\u0438\u0438 \u0443\u0447\u0430\u0441\u0442\u043d\u0438\u043a\u0438 \u043f\u044b\u0442\u0430\u043b\u0438\u0441\u044c \u043d\u0430\u0439\u0442\u0438 \u0440\u0435\u0448\u0435\u043d\u0438\u044f \u0438 \u043d\u043e\u0432\u044b\u0435 \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442\u044b \u0434\u043b\u044f \u044d\u0444\u0444\u0435\u043a\u0442\u0438\u0432\u043d\u043e\u0433\u043e \u0432\u0437\u0430\u0438\u043c\u043e\u0434\u0435\u0439\u0441\u0442\u0432\u0438\u044f \u0431\u0438\u0437\u043d\u0435\u0441\u0430 \u0438 \u0441\u043f\u0435\u0446\u0438\u0430\u043b\u0438\u0441\u0442\u043e\u0432 \u043f\u043e \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0435 \u0438 \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u043e\u043d\u043d\u043e-\u0442\u0435\u0445\u043d\u043e\u043b\u043e\u0433\u0438\u0447\u0435\u0441\u043a\u043e\u043c\u0443 \u043e\u0431\u0441\u043b\u0443\u0436\u0438\u0432\u0430\u043d\u0438\u044e. \u041a\u043e\u043d\u0444\u0435\u0440\u0435\u043d\u0446\u0438\u044f \u0443\u0434\u0430\u043b\u0430\u0441\u044c: \u0431\u044b\u043b\u043e \u0440\u0435\u0430\u043b\u044c\u043d\u043e \u043c\u043d\u043e\u0433\u043e \u043f\u043e\u043b\u0435\u0437\u043d\u044b\u0445 \u0434\u043e\u043a\u043b\u0430\u0434\u043e\u0432, \u0438\u043d\u0442\u0435\u0440\u0435\u0441\u043d\u044b\u0435 \u0444\u043e\u0440\u043c\u0430\u0442\u044b \u0432\u044b\u0441\u0442\u0443\u043f\u043b\u0435\u043d\u0438\u0439 \u0438 \u043a\u0443\u0447\u0430 \u043e\u0431\u0449\u0435\u043d\u0438\u044f \u0441 \u0434\u043e\u043a\u043b\u0430\u0434\u0447\u0438\u043a\u0430\u043c\u0438. \u0418 \u043e\u0441\u043e\u0431\u0435\u043d\u043d\u043e \u0432\u0430\u0436\u043d\u043e, \u0447\u0442\u043e \u043c\u043d\u0435 \u043d\u0438\u043a\u0442\u043e \u043d\u0438\u0447\u0435\u0433\u043e \u043d\u0435 \u043f\u044b\u0442\u0430\u043b\u0441\u044f \u043f\u0440\u043e\u0434\u0430\u0442\u044c, […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":24300,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-32497","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47DevOpsForum 2019. Nuk duhet pritur p\u00ebr t\u00eb implementuar DevOps | ProHoster","description":"S\u00eb fundmi vizitova DevOpsForum 2019, q\u00eb organizoi Logrocon.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/devopsforum-2019-vnedryat-devops-nelzya-zhdat","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47DevOpsForum 2019. \u0412\u043d\u0435\u0434\u0440\u044f\u0442\u044c DevOps \u043d\u0435\u043b\u044c\u0437\u044f \u0436\u0434\u0430\u0442\u044c | ProHoster","og:description":"\u041d\u0435\u0434\u0430\u0432\u043d\u043e \u044f \u043f\u043e\u0431\u044b\u0432\u0430\u043b\u0430 \u043d\u0430 DevOpsForum 2019, \u043a\u043e\u0442\u043e\u0440\u0443\u044e \u0443\u0441\u0442\u0440\u0430\u0438\u0432\u0430\u043b Logrocon.","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/devopsforum-2019-vnedryat-devops-nelzya-zhdat","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T18:47:23+00:00","article:modified_time":"2019-10-31T18:47:23+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"32497","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-02-19 09:14:07","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 02:57:23","updated":"2026-02-19 09:14:07","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/32497","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=32497"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/32497\/revisions"}],"predecessor-version":[{"id":161790,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/32497\/revisions\/161790"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/24300"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=32497"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=32497"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=32497"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}