{"id":71625,"date":"2020-02-27T08:51:18","date_gmt":"2020-02-27T05:51:18","guid":{"rendered":"https:\/\/prohoster.info\/blog\/sem-samyh-rasprostranennyh-oshibok-pri-perehode-na-ci-cd"},"modified":"2020-03-03T16:14:16","modified_gmt":"2020-03-03T13:14:16","slug":"sem-samyh-rasprostranennyh-oshibok-pri-perehode-na-ci-cd","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/sem-samyh-rasprostranennyh-oshibok-pri-perehode-na-ci-cd","title":{"rendered":"Cele \u0219apte cele mai comune gre\u0219eli atunci c\u00e2nd se face tranzi\u021bia la CI\/CD.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Cele
\nDac\u0103 compania dvs. implementeaz\u0103 abia acum DevOps sau instrumente CI\/CD, ar putea fi util s\u0103 v\u0103 familiariza\u021bi cu cele mai frecvente gre\u0219eli, pentru a nu le repeta \u0219i a nu c\u0103lca pe urmele altora.\u00a0<\/p>\n

Comanda Solu\u021bii Cloud Mail.ru<\/a><\/noindex> a tradus articolul Evita\u021bi aceste capcane comune atunci c\u00e2nd trece\u021bi la CI\/CD de Jasmine Chokshi cu ad\u0103ugiri<\/a><\/noindex>.
\n<\/a><\/noindex><\/p>\n

Lipsa de preg\u0103tire pentru schimbarea culturii \u0219i a proceselor<\/h2>\n

\nDac\u0103 privim la diagrama ciclic\u0103 DevOps<\/a><\/noindex>, se observ\u0103 c\u0103 \u00een practicile DevOps, testarea este o activitate continu\u0103, o parte fundamental\u0103 a fiec\u0103rei desf\u0103\u0219ur\u0103ri separate.<\/p>\n

\"Cele
\nDiagrama ciclic\u0103 infinit\u0103 DevOps<\/i><\/p>\n

Testarea \u0219i asigurarea calit\u0103\u021bii \u00een procesul de dezvoltare \u0219i livrare sunt o parte obligatorie a tot ceea ce fac dezvoltatorii. Aceasta necesit\u0103 o schimbare de mentalitate pentru a include testarea \u00een fiecare sarcin\u0103.<\/p>\n

Testarea devine parte din munca de zi cu zi a fiec\u0103rui membru al echipei. Trecerea la testarea constant\u0103 nu este u\u0219oar\u0103, trebuie s\u0103 fi\u021bi preg\u0103ti\u021bi pentru asta.<\/p>\n

Lipsa de feedback<\/h2>\n

\nEficien\u021ba DevOps depinde de feedback-ul constant. \u00cembun\u0103t\u0103\u021birea continu\u0103 nu este posibil\u0103 f\u0103r\u0103 un spa\u021biu pentru colaborare \u0219i comunicare.<\/p>\n

Companiile care nu organizeaz\u0103 \u00eent\u00e2lniri retrospective au dificult\u0103\u021bi \u00een a implementa o cultur\u0103 de feedback continuu \u00een CI\/CD. \u00cent\u00e2lnirile retrospective se desf\u0103\u0219oar\u0103 la sf\u00e2r\u0219itul fiec\u0103rei itera\u021bii, unde membrii grupului discut\u0103 despre ceea ce a mers bine \u0219i ce a mers prost. \u00cent\u00e2lnirile retrospective sunt fundamentale pentru Scrum\/Agile, dar sunt necesare \u0219i pentru DevOps.\u00a0<\/p>\n

Acest lucru se datoreaz\u0103 faptului c\u0103 \u00eent\u00e2lnirile retrospective dezvolt\u0103 obiceiul de a face schimb de feedback \u0219i opinii. Unul dintre cele mai importante aspecte la \u00eenceput este organizarea de \u00eent\u00e2lniri retro repetitive, astfel \u00eenc\u00e2t acestea s\u0103 devin\u0103 clare \u0219i familiare \u00eentregului colectiv.<\/p>\n

C\u00e2nd vine vorba de calitatea software-ului, to\u021bi membrii echipei sunt responsabili pentru men\u021binerea acesteia. De exemplu, dezvoltatorii pot scrie teste modulare, precum \u0219i scrie cod av\u00e2nd \u00een vedere testabilitatea, ajut\u00e2nd la reducerea riscurilor de la bun \u00eenceput.<\/p>\n

Una dintre modalit\u0103\u021bile simple de a reflecta schimbarea percep\u021biilor despre testare este de a numi testerii nu QA, ci tester de software sau inginer de calitate. Aceast\u0103 modificare poate p\u0103rea prea simpl\u0103 sau chiar stupid\u0103. Dar dac\u0103 cineva este numit \u201especialist \u00een asigurarea calit\u0103\u021bii software\u201d, se creeaz\u0103 o impresie gre\u0219it\u0103 despre cine este responsabil pentru calitatea produsului. \u00cen practicile Agile, CI\/CD \u0219i DevOps, to\u021bi sunt responsabili pentru calitatea software-ului.<\/p>\n

Un alt aspect important este \u00een\u021belegerea a ceea ce \u00eenseamn\u0103 calitate pentru \u00eentreaga echip\u0103 \u0219i fiecare membru al acesteia, organiza\u021bie, p\u0103r\u021bi interesate.<\/p>\n

\u00cen\u021belegerea gre\u0219it\u0103 a finaliz\u0103rii etapei<\/h2>\n

\nDac\u0103 calitatea este un proces continuu \u0219i comun, trebuie s\u0103 existe o \u00een\u021belegere comun\u0103 a finaliz\u0103rii etapei. Cum putem \u0219ti c\u0103 etapa este terminat\u0103? Ce se \u00eent\u00e2mpl\u0103 c\u00e2nd etapa este marcat\u0103 ca finalizat\u0103 pe tabloul Trello sau pe alt tablou Kanban?<\/p>\n

Defini\u021bia etapei finalizate (DoD) este un instrument puternic \u00een contextul CD DevOps\/CI. Ajut\u0103 la o mai bun\u0103 \u00een\u021belegere a standardelor de calitate ale a ceea ce \u0219i cum construie\u0219te echipa.<\/p>\n

Echipa de dezvoltare trebuie s\u0103 decid\u0103 ce \u00eenseamn\u0103 \u201eGata\u201d. Este necesar s\u0103 se adune \u0219i s\u0103 \u00eentocmeasc\u0103 o list\u0103 de caracteristici care trebuie \u00eendeplinite la fiecare etap\u0103 pentru a putea fi considerat\u0103 finalizat\u0103.<\/p>\n

DoD face procesul mai transparent \u0219i faciliteaz\u0103 implementarea CI\/CD, dac\u0103 este clar pentru to\u021bi membrii echipei \u0219i este convenit reciproc.<\/p>\n

Lipsa unor obiective clare \u0219i realiste<\/h2>\n

\nAcesta este unul dintre cele mai frecvent citate sfaturi, dar merit\u0103 repetat. Pentru succesul oric\u0103rei ini\u021biative serioase, inclusiv implementarea CI\/CD sau DevOps, este necesar s\u0103 se stabileasc\u0103 obiective reale \u0219i s\u0103 se m\u0103soare performan\u021ba \u00een raport cu acestea. Ce \u00eencerca\u021bi s\u0103 ob\u021bine\u021bi prin CI\/CD? Ofer\u0103 o lansare mai rapid\u0103 cu o calitate mai bun\u0103?<\/p>\n

Orice obiective stabilite trebuie s\u0103 fie nu doar transparente \u0219i realiste, ci \u0219i s\u0103 se alinieze cu activitatea curent\u0103 a companiei. De exemplu, c\u00e2t de des au clien\u021bii dumneavoastr\u0103 nevoie de corec\u021bii sau versiuni noi? Nu este nevoie s\u0103 supra\u00eenc\u0103rca\u021bi procesele \u0219i s\u0103 lansa\u021bi versiuni mai rapid, dac\u0103 nu exist\u0103 beneficii suplimentare pentru utilizatori.<\/p>\n

\u00cen plus, nu trebuie sempre s\u0103 implementa\u021bi at\u00e2t CD, c\u00e2t \u0219i CI. De exemplu, companiile cu un grad ridicat de reglementare, cum ar fi b\u0103ncile \u0219i clinicile medicale, pot func\u021biona doar cu CI.<\/p>\n

CI este un punct de plecare bun pentru orice companie care \u00eemplementeaz\u0103 DevOps. Odat\u0103 cu implementarea sa, abord\u0103rile de livrare a software-ului se schimb\u0103 semnificativ. Dup\u0103 ce a fost st\u0103p\u00e2nit CI, se poate lua \u00een considerare \u00eembun\u0103t\u0103\u021birea \u00eentregului proces, cre\u0219terea vitezei de livrare \u0219i alte modific\u0103ri.<\/p>\n

Pentru multe organiza\u021bii, un singur CI este suficient, iar CD ar trebui implementat doar dac\u0103 aduce un beneficiu suplimentar.<\/p>\n

Absen\u021ba tablourilor de bord \u0219i metricilor corespunz\u0103toare<\/h2>\n

\nOdat\u0103 ce a\u021bi stabilit obiectivele, echipa de dezvoltare poate crea un tablou de bord pentru a m\u0103sura KPI. \u00cenainte de a-l dezvolta, este bine s\u0103 evalua\u021bi parametrii care vor fi urm\u0103ri\u021bi.<\/p>\n

Diversele rapoarte \u0219i aplica\u021bii sunt utile pentru diferite membri ai echipei. Scrum masterii sunt mai interesa\u021bi de status \u0219i acoperire. \u00cen timp ce managementul superior poate fi interesat de rata de epuizare a speciali\u0219tilor.<\/p>\n

Unele echipe utilizeaz\u0103, de asemenea, tablouri de bord cu indicatori ro\u0219ii, galbeni \u0219i verzi pentru a evalua statusul CI\/CD, pentru a \u00een\u021belege dac\u0103 fac totul corect sau dac\u0103 a ap\u0103rut o eroare. Ro\u0219u \u00eenseamn\u0103 c\u0103 trebuie s\u0103 acorde aten\u021bie la ceea ce se \u00eent\u00e2mpl\u0103.<\/p>\n

Cu toate acestea, dac\u0103 panourile informative nu sunt standardizate, ele pot duce la confuzie. Analiza\u021bi ce date sunt necesare tuturor, apoi crea\u021bi o descriere standardizat\u0103 a ceea ce \u00eenseamn\u0103 acestea. Afla\u021bi ce are mai mult sens pentru p\u0103r\u021bile interesate: grafice, text sau numere.<\/p>\n

Absen\u021ba testelor manuale<\/h2>\n

\nAutomatizarea test\u0103rii pune bazele unui bun conveior CI\/CD. Dar testarea automatizat\u0103 \u00een toate etapele nu \u00eenseamn\u0103 c\u0103 nu trebuie s\u0103 realiza\u021bi teste manuale.\u00a0<\/p>\n

Pentru a construi un conveior CI\/CD eficient, sunt necesare \u0219i teste manuale. Vor exista \u00eentotdeauna unele aspecte ale test\u0103rii care necesit\u0103 analiz\u0103 de c\u0103tre o persoan\u0103.<\/p>\n

Merit\u0103 s\u0103 lua\u021bi \u00een considerare integrarea eforturilor de testare manual\u0103 \u00een conveior. Dup\u0103 ce testarea manual\u0103 a unor cazuri de testare este finalizat\u0103, pute\u021bi trece la etapa de desf\u0103\u0219urare.<\/p>\n

Nu \u00eencerca\u021bi s\u0103 \u00eembun\u0103t\u0103\u021bi\u021bi testele<\/h2>\n

\nO pipeline CI\/CD eficient necesit\u0103 acces la instrumentele potrivite, fie c\u0103 este vorba despre gestionarea test\u0103rii sau integrarea \u0219i monitorizarea continu\u0103.<\/p>\n

Crearea unei culturi puternice, orientate spre calitate, se concentreaz\u0103 pe implementarea testelor<\/a><\/noindex>, monitorizarea interac\u021biunilor cu clien\u021bii dup\u0103 desf\u0103\u0219urare \u0219i urm\u0103rirea \u00eembun\u0103t\u0103\u021birilor.\u00a0<\/p>\n

Iat\u0103 c\u00e2teva sfaturi practice pe care le pute\u021bi implementa cu u\u0219urin\u021b\u0103:<\/p>\n

    \n
  1. Asigura\u021bi-v\u0103 c\u0103 testele sunt u\u0219or de scris \u0219i suficient de flexibile pentru a nu se strica atunci c\u00e2nd se refactorizeaz\u0103 codul.<\/li>\n
  2. Echipele de dezvoltare trebuie s\u0103 fie incluse \u00een procesul de testare \u2014 s\u0103 vad\u0103 lista problemelor \u0219i solicit\u0103rilor utilizatorilor care sunt importante pentru verificare \u00een timpul pipeline-urilor CI.<\/li>\n
  3. S-ar putea s\u0103 nu ave\u021bi o acoperire complet\u0103 a testelor, dar asigura\u021bi-v\u0103 c\u0103 fluxurile importante pentru UX \u0219i interac\u021biunea cu clien\u021bii sunt testate.<\/li>\n<\/ol>\n

    <\/p>\n

    Ultimul, dar nu cel din urm\u0103 punct<\/h2>\n

    \nTranzi\u021bia la CI\/CD este de obicei ini\u021biat\u0103 de jos \u00een sus, dar, \u00een cele din urm\u0103, reprezint\u0103 o transformare care necesit\u0103 participarea managementului, timp \u0219i resurse din partea companiei. CI\/CD este un set de abilit\u0103\u021bi, procese, instrumente \u0219i o reorganizare cultural\u0103, iar implementarea acestor schimb\u0103ri se poate face doar sistemic.<\/p>\n

    \nWhat else to read on the topic<\/strong>:<\/p>\n

      \n
    1. Cum datoria tehnic\u0103 ucide proiectele dumneavoastr\u0103<\/a><\/noindex>.<\/li>\n
    2. Cum s\u0103 \u00eembun\u0103t\u0103\u021bi\u021bi DevOps<\/a><\/noindex>.<\/li>\n
    3. Nou\u0103 tendin\u021be principale \u00een DevOps \u00een 2020<\/a><\/noindex>.<\/li>\n<\/ol>\n

      Sursa: habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

      \u0415\u0441\u043b\u0438 \u0432\u0430\u0448\u0430 \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u044f \u0442\u043e\u043b\u044c\u043a\u043e \u0432\u043d\u0435\u0434\u0440\u044f\u0435\u0442 DevOps \u0438\u043b\u0438 \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442\u044b CI\/CD, \u0432\u0430\u043c \u043c\u043e\u0436\u0435\u0442 \u0431\u044b\u0442\u044c \u043f\u043e\u043b\u0435\u0437\u043d\u043e \u043f\u043e\u0437\u043d\u0430\u043a\u043e\u043c\u0438\u0442\u044c\u0441\u044f \u0441 \u0441\u0430\u043c\u044b\u043c\u0438 \u0440\u0430\u0441\u043f\u0440\u043e\u0441\u0442\u0440\u0430\u043d\u0435\u043d\u043d\u044b\u043c\u0438 \u043e\u0448\u0438\u0431\u043a\u0430\u043c\u0438, \u0447\u0442\u043e\u0431\u044b \u043d\u0435 \u043f\u043e\u0432\u0442\u043e\u0440\u0438\u0442\u044c \u0438\u0445 \u0438 \u043d\u0435 \u043d\u0430\u0441\u0442\u0443\u043f\u0430\u0442\u044c \u043d\u0430 \u0447\u0443\u0436\u0438\u0435 \u0433\u0440\u0430\u0431\u043b\u0438.\u00a0 \u041a\u043e\u043c\u0430\u043d\u0434\u0430 Mail.ru Cloud Solutions \u043f\u0435\u0440\u0435\u0432\u0435\u043b\u0430 \u0441\u0442\u0430\u0442\u044c\u044e Avoid These Common Pitfalls When Transitioning to CI\/CD by Jasmine Chokshi \u0441 \u0434\u043e\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u044f\u043c\u0438. \u041d\u0435\u0433\u043e\u0442\u043e\u0432\u043d\u043e\u0441\u0442\u044c \u043a \u0438\u0437\u043c\u0435\u043d\u0435\u043d\u0438\u044e \u043a\u0443\u043b\u044c\u0442\u0443\u0440\u044b \u0438 \u043f\u0440\u043e\u0446\u0435\u0441\u0441\u043e\u0432 \u0415\u0441\u043b\u0438 \u043f\u043e\u0441\u043c\u043e\u0442\u0440\u0435\u0442\u044c […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":71626,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-71625","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\udd47Cele mai frecvente \u0219apte gre\u0219eli \u00een trecerea la CI\/CD | ProHoster","description":"Dac\u0103 compania dumneavoastr\u0103 tocmai implementeaz\u0103.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/sem-samyh-rasprostranennyh-oshibok-pri-perehode-na-ci-cd","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","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\udd47\u0421\u0435\u043c\u044c \u0441\u0430\u043c\u044b\u0445 \u0440\u0430\u0441\u043f\u0440\u043e\u0441\u0442\u0440\u0430\u043d\u0435\u043d\u043d\u044b\u0445 \u043e\u0448\u0438\u0431\u043e\u043a \u043f\u0440\u0438 \u043f\u0435\u0440\u0435\u0445\u043e\u0434\u0435 \u043d\u0430 CI\/CD | ProHoster","og:description":"\u0415\u0441\u043b\u0438 \u0432\u0430\u0448\u0430 \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u044f \u0442\u043e\u043b\u044c\u043a\u043e \u0432\u043d\u0435\u0434\u0440\u044f\u0435\u0442.","og:url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/sem-samyh-rasprostranennyh-oshibok-pri-perehode-na-ci-cd","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":"2020-02-27T05:51:18+00:00","article:modified_time":"2020-03-03T13:14:16+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"71625","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":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 18:58:26","updated":"2022-09-30 03:23:17","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/71625","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=71625"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/71625\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/71626"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=71625"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=71625"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=71625"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}