{"id":34683,"date":"2019-10-31T21:59:48","date_gmt":"2019-10-31T18:59:48","guid":{"rendered":"https:\/\/prohoster.info\/blog\/gitlab-11-11-neskolko-otvetstvennyh-dlya-merdzh-rekvestov-i-uluchsheniya-dlya-kontejnerov\/"},"modified":"2019-10-31T21:59:48","modified_gmt":"2019-10-31T18:59:48","slug":"gitlab-11-11-neskolko-otvetstvennyh-dlya-merdzh-rekvestov-i-uluchsheniya-dlya-kontejnerov","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/gitlab-11-11-neskolko-otvetstvennyh-dlya-merdzh-rekvestov-i-uluchsheniya-dlya-kontejnerov","title":{"rendered":"GitLab 11.11: mai multe persoane responsabile pentru cererile de fuziune \u0219i \u00eembun\u0103t\u0103\u021biri pentru containere","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"GitLab 11.11: mai multe persoane responsabile pentru cererile de fuziune \u0219i \u00eembun\u0103t\u0103\u021biri pentru containere\" src=\"\/wp-content\/uploads\/2019\/05\/0887dec341b6fcd6b12422babac990e1.png\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><\/p>\n<h3 id=\"bolshe-vozmozhnostey-dlya-sovmestnoy-raboty-i-dopolnitelnye-uvedomleniya\">Mai multe oportunit\u0103\u021bi pentru colaborare \u0219i notific\u0103ri suplimentare<\/h3>\n<p><\/p>\n<p>La GitLab, c\u0103ut\u0103m constant noi modalit\u0103\u021bi de a \u00eembun\u0103t\u0103\u021bi colaborarea pe \u00eentregul ciclu de via\u021b\u0103 DevOps. Suntem \u00eenc\u00e2nta\u021bi s\u0103 anun\u021b\u0103m c\u0103 din aceast\u0103 versiune sus\u021binem <noindex><a rel=\"nofollow\" href=\"https:\/\/about.gitlab.com\/2019\/05\/22\/gitlab-11-11-released\/#multiple-assignees-for-merge-requests\">mai mul\u021bi responsabili pentru o cerere de \u00eembinare<\/a><\/noindex>! Aceast\u0103 caracteristic\u0103 este disponibil\u0103 de la nivelul GitLab Starter \u0219i \u00eentruchipeaz\u0103 cu adev\u0103rat deviza noastr\u0103: <strong>\u201eOricine poate contribui\u201d<\/strong>. \u0218tim c\u0103 la o cerere de \u00eembinare pot lucra multe persoane pentru a se asigura c\u0103 totul este \u00een regul\u0103, iar acum ave\u021bi posibilitatea de a desemna mai mul\u021bi responsabili pentru cererile de \u00eembinare!<\/p>\n<p><\/p>\n<p>De asemenea, echipele DevOps primesc acum <noindex><a rel=\"nofollow\" href=\"https:\/\/about.gitlab.com\/2019\/05\/22\/gitlab-11-11-released\/#deployment-notifications-for-slack-and-mattermost\">notific\u0103ri automate despre evenimentele de livrare \u00een Slack \u0219i Mattermost<\/a><\/noindex>. Ad\u0103uga\u021bi noi notific\u0103ri \u00een lista de evenimente trimise \u00een aceste dou\u0103 chat-uri, iar echipa dumneavoastr\u0103 va afla aproape instantaneu despre noile livr\u0103ri.<\/p>\n<p><\/p>\n<h3 id=\"sokraschenie-izderzhek-s-podderzhkoy-konteynerov-docker-v-windows-i-podgotovkoy-klasterov-kubernetes-na-urovne-ekzemplyara\">Reducerea costurilor cu suportul pentru containere Docker \u00een Windows \u0219i preg\u0103tirea clusterelor Kubernetes la nivel de instan\u021b\u0103<\/h3>\n<p><noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<p>Ne plac containerele! Containerele consum\u0103 mai pu\u021bine resurse de sistem \u00een compara\u021bie cu ma\u0219inile virtuale \u0219i \u00eembun\u0103t\u0103\u021besc portabilitatea aplica\u021biei. Din versiunea GitLab 11.11, sus\u021binem <noindex><a rel=\"nofollow\" href=\"https:\/\/about.gitlab.com\/2019\/05\/22\/gitlab-11-11-released\/#windows-container-executor-for-gitlab-runner\">Executor Container Windows pentru GitLab Runner<\/a><\/noindex>, a\u0219a c\u0103 acum pute\u021bi folosi containere Docker \u00een Windows \u0219i beneficia de capacit\u0103\u021bi extinse de orchestrare a pipeline-urilor \u0219i management.<\/p>\n<p><\/p>\n<p>GitLab Premium (doar pentru instan\u021bele auto-g\u0103zduite) ofer\u0103 acum <noindex><a rel=\"nofollow\" href=\"https:\/\/about.gitlab.com\/2019\/05\/22\/gitlab-11-11-released\/#caching-dependency-proxy-for-container-registry\">proxy de cache pentru dependen\u021be pentru imaginile Docker<\/a><\/noindex>. Aceast\u0103 extensie va accelera livrarea, deoarece acum ve\u021bi avea un proxy de cache pentru imaginile Docker utilizate frecvent.<\/p>\n<p><\/p>\n<p>Utilizatorii instan\u021belor auto-g\u0103zduite GitLab pot acum s\u0103 preg\u0103teasc\u0103 <noindex><a rel=\"nofollow\" href=\"https:\/\/about.gitlab.com\/2019\/05\/22\/gitlab-11-11-released\/#instance-level-kubernetes-cluster-configuration\">cluster Kubernetes la nivel de instan\u021be<\/a><\/noindex>, iar toate grupurile \u0219i proiectele din instan\u021b\u0103 \u00eel vor folosi pentru livr\u0103rile lor. Datorit\u0103 acestei integr\u0103ri \u00eentre GitLab \u0219i Kubernetes, resursele pentru proiectele specifice vor fi create automat pentru o securitate suplimentar\u0103.<\/p>\n<p><\/p>\n<h3 id=\"i-eto-esche-ne-vse\">\u0218i asta nu e tot!<\/h3>\n<p><\/p>\n<p>Pe l\u00e2ng\u0103 noile oportunit\u0103\u021bi pentru colaborare \u0219i notific\u0103ri suplimentare, am ad\u0103ugat <noindex><a rel=\"nofollow\" href=\"https:\/\/about.gitlab.com\/2019\/05\/22\/gitlab-11-11-released\/#guest-access-to-releases\">acces pentru invita\u021bi la lans\u0103ri<\/a><\/noindex>, am crescut <noindex><a rel=\"nofollow\" href=\"https:\/\/about.gitlab.com\/2019\/05\/22\/gitlab-11-11-released\/#add-on-ci-runner-minutes-have-been-extended-to-free-plans\">minutele suplimentare CI Runner pentru GitLab Free<\/a><\/noindex>, am simplificat Revizuirile cu ajutorul <noindex><a rel=\"nofollow\" href=\"https:\/\/about.gitlab.com\/2019\/05\/22\/gitlab-11-11-released\/#applying-a-suggestion-now-automatically-resolves-the-discussion\">rezolv\u0103rii automate a discu\u021biilor atunci c\u00e2nd aplica\u021bi o sugestie<\/a><\/noindex>, \u0219i multe altele!<\/p>\n<p><\/p>\n<blockquote><p>Angajatul lunii (<noindex><a rel=\"nofollow\" href=\"https:\/\/about.gitlab.com\/community\/mvp\/\">MVP<\/a><\/noindex>) \u2014 Kia Mei Somabes (<noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/kiameisomabes\">Kia Mei Somabes<\/a><\/noindex>)<\/p>\n<p>\u00cen aceast\u0103 edi\u021bie am ad\u0103ugat posibilitatea de a desc\u0103rca foldere individuale din repositorii, nu doar tot con\u021binutul. Acum pute\u021bi desc\u0103rca doar c\u00e2teva fi\u0219iere necesare. Mul\u021bumim, Kia Mei Somabes!<\/p><\/blockquote>\n<p><\/p>\n<h2 id=\"glavnye-fichi-gitlab-1111\">Func\u021bionalit\u0103\u021bile principale GitLab 11.11<\/h2>\n<p><\/p>\n<h3 id=\"windows-container-executor-dlya-gitlab-runner\">Executor Container Windows pentru GitLab Runner<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>\u00cen GitLab 11.11, am ad\u0103ugat un nou executor \u00een GitLab Runner, astfel \u00eenc\u00e2t containerele Docker s\u0103 poat\u0103 fi utilizate \u0219i \u00een Windows. Anterior, trebuia s\u0103 folosi\u021bi un shell pentru orchestrarea containerelor Docker \u00een Windows, dar acum pute\u021bi lucra cu containere Docker \u00een Windows direct, aproape ca \u00een Linux. Acum utilizatorii platformelor de la Microsoft au la dispozi\u021bie mai multe op\u021biuni pentru orchestrarea pipeline-urilor \u0219i gestionare.<\/p>\n<p><\/p>\n<p>Aceast\u0103 actualizare include suport \u00eembun\u0103t\u0103\u021bit pentru PowerShell \u00een GitLab CI\/CD \u0219i noi imagini auxiliare pentru diferite versiuni ale containerelor Windows. Runners-urile dumneavoastr\u0103 Windows pot fi bine\u00een\u021beles utilizate cu GitLab.com, dar momentan nu se afl\u0103 pe lista instrumentelor disponibile public.<\/p>\n<p><\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habrastorage.org\/webt\/ox\/p1\/pt\/oxp1ptcfi53ctd6bmhlejt52t_8.png\"><img decoding=\"async\" alt=\"GitLab 11.11: mai multe persoane responsabile pentru cererile de fuziune \u0219i \u00eembun\u0103t\u0103\u021biri pentru containere\" src=\"\/wp-content\/uploads\/2019\/05\/3d991e4acc92816901582596537ad12d.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/p>\n<p><\/p>\n<h3 id=\"keshiruyuschiy-proksi-zavisimostey-dlya-reestra-konteynerov\">Proxy de cache a dependen\u021belor pentru registrul containerelor<\/h3>\n<p><\/p>\n<p><em>PREMIUM, ULTIMATE<\/em><\/p>\n<p><\/p>\n<p>Echipele folosesc adesea containere \u00een pipeline-urile de build, iar un proxy de cache pentru imaginile \u0219i pachetele utilizate frecvent din upstream este o modalitate excelent\u0103 de a accelera pipeline-urile. Cu o copie local\u0103 a straturilor necesare disponibil\u0103 prin noul proxy de cache, se poate lucra mai eficient cu imaginile comune \u00een mediu.<\/p>\n<p><\/p>\n<p>P\u00e2n\u0103 acum, proxy-ul pentru containere este disponibil doar pentru instan\u021bele auto-g\u0103zduite pe serverul web <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.gitlab.com\/omnibus\/settings\/puma.html\">Puma (\u00een modul experimental)<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habrastorage.org\/webt\/zx\/k0\/a_\/zxk0a_ctmegblwe0i_qrhivtvjw.png\"><img decoding=\"async\" alt=\"GitLab 11.11: mai multe persoane responsabile pentru cererile de fuziune \u0219i \u00eembun\u0103t\u0103\u021biri pentru containere\" src=\"\/wp-content\/uploads\/2019\/05\/9cb077673935974d6af0e7980276c525.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/p>\n<p><\/p>\n<h3 id=\"neskolko-otvetstvennyh-dlya-merdzh-rekvestov\">Mai mul\u021bi responsabili pentru cererile de fuzionare<\/h3>\n<p><\/p>\n<p><em>STARTER, PREMIUM, ULTIMATE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>Destul de des, mai multe persoane lucreaz\u0103 simultan la o func\u021bie \u00een aceea\u0219i ramur\u0103 \u0219i cerere de fuzionare, de exemplu, c\u00e2nd dezvoltatorii front-end \u0219i back-end colaboreaz\u0103 str\u00e2ns sau c\u00e2nd dezvoltatorii lucreaz\u0103 \u00een perechi, ca \u00een programarea extrem\u0103.<\/p>\n<p><\/p>\n<p>\u00cen GitLab 11.11, mai multe persoane pot fi desemnate pentru cererile de fuzionare. Ca \u0219i \u00een cazul mai multor responsabili pentru sarcini, aici pot fi folosite liste, filtre, notific\u0103ri \u0219i API.<\/p>\n<p><\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habrastorage.org\/webt\/v4\/so\/x5\/v4sox5skhu3uot8g724wgbnkgws.png\"><img decoding=\"async\" alt=\"GitLab 11.11: mai multe persoane responsabile pentru cererile de fuziune \u0219i \u00eembun\u0103t\u0103\u021biri pentru containere\" src=\"\/wp-content\/uploads\/2019\/05\/3416db7e19ba5a7ee5fc91e38490fed7.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/p>\n<p><\/p>\n<h3 id=\"konfiguraciya-klastera-kubernetes-na-urovne-ekzemplyara\">Configurarea clusterului Kubernetes la nivel de instan\u021b\u0103<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE<\/em><\/p>\n<p><\/p>\n<p>Modelul de securitate \u0219i preg\u0103tire \u00een Kubernetes evolueaz\u0103, iar acum este posibil s\u0103 gestiona\u021bi un num\u0103r mare de clien\u021bi printr-un singur cluster comun.<\/p>\n<p><\/p>\n<p>\u00cen GitLab 11.11, utilizatorii instan\u021belor auto-g\u0103zduite pot acum s\u0103 preg\u0103teasc\u0103 un cluster la nivel de instan\u021b\u0103, iar toate grupurile \u0219i proiectele din instan\u021b\u0103 vor folosi acest cluster pentru implement\u0103rile lor. Datorit\u0103 acestei integr\u0103ri, GitLab cu Kubernetes va crea automat resurse pentru proiecte specifice pentru o securitate suplimentar\u0103.<\/p>\n<p><\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habrastorage.org\/webt\/gq\/f7\/ia\/gqf7iald9i3j80ww4cu2t4gd_8m.png\"><img decoding=\"async\" alt=\"GitLab 11.11: mai multe persoane responsabile pentru cererile de fuziune \u0219i \u00eembun\u0103t\u0103\u021biri pentru containere\" src=\"\/wp-content\/uploads\/2019\/05\/fc8b3b09aa400556c7eeec63b8efc785.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/p>\n<p><\/p>\n<h3 id=\"uvedomleniya-o-deployah-v-slack-i-mattermost\">Notific\u0103ri despre implement\u0103ri \u00een Slack \u0219i Mattermost<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>Acum pute\u021bi configura notific\u0103ri automate despre evenimentele de implementare \u00een canalul echipei, datorit\u0103 integr\u0103rii cu chat-urile. <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.gitlab.com\/ee\/user\/project\/integrations\/slack.html\">Slack<\/a><\/noindex> \u0219i <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.gitlab.com\/ee\/user\/project\/integrations\/mattermost.html\">Mattermost<\/a><\/noindex>, iar echipa dvs. va fi la curent cu toate evenimentele importante.<\/p>\n<p><\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habrastorage.org\/webt\/az\/gv\/_d\/azgv_d7ss0efz9misepgduv0vdu.png\"><img decoding=\"async\" alt=\"GitLab 11.11: mai multe persoane responsabile pentru cererile de fuziune \u0219i \u00eembun\u0103t\u0103\u021biri pentru containere\" src=\"\/wp-content\/uploads\/2019\/05\/c7b470294640d2cdf16bde761437c665.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/p>\n<p><\/p>\n<h3 id=\"gostevoy-dostup-k-vypuskam\">Acces gazdelor la versiunile de lansare<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>Acum, utilizatorii invita\u021bi ai proiectelor dvs. pot vizualiza versiunile publicate pe pagina Releases. Ace\u0219tia vor putea desc\u0103rca artefactele publicate, dar nu vor putea desc\u0103rca codul surs\u0103 sau vedea informa\u021bii despre repozitorii, cum ar fi etichetele sau commit-urile.<\/p>\n<p><\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habrastorage.org\/webt\/zn\/0x\/it\/zn0xit3cx4szlvqtgljd7rxyo7g.png\"><img decoding=\"async\" alt=\"GitLab 11.11: mai multe persoane responsabile pentru cererile de fuziune \u0219i \u00eembun\u0103t\u0103\u021biri pentru containere\" src=\"\/wp-content\/uploads\/2019\/05\/60e3216a4228306f136e1229c3ec2e56.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/p>\n<p><\/p>\n<h2 id=\"drugie-uluchsheniya-v-gitlab-1111\">Alte \u00eembun\u0103t\u0103\u021biri \u00een GitLab 11.11<\/h2>\n<p><\/p>\n<h3 id=\"serializovannye-grafy-kommitov-dlya-povysheniya-proizvoditelnosti\">Grafuri de commit serializate pentru o performan\u021b\u0103 \u00eembun\u0103t\u0103\u021bit\u0103<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>Pentru multe opera\u021bii Git, este necesar\u0103 parcurgerea grafului de commit, de exemplu, calcularea bazei de fuziune sau generarea ramurilor care con\u021bin commit. Cu c\u00e2t sunt mai multe commit-uri, cu at\u00e2t aceste opera\u021bii devin mai lente, deoarece pentru parcurgere trebuie s\u0103 se \u00eencarce fiecare obiect de pe disc pentru a citi indicii acestuia.<\/p>\n<p><\/p>\n<p>\u00cen GitLab 11.11, am inclus func\u021bia de grafuri de commit serializate, introdus\u0103 \u00een cele mai recente versiuni Git, pentru a calcula \u0219i stoca aceste informa\u021bii din timp. Acum, parcurgerile \u00een repozitorii mari se efectueaz\u0103 mult mai repede. Graful de commit va fi creat automat la urm\u0103toarea cur\u0103\u021bare a memoriei din repozitoriu.<\/p>\n<p><\/p>\n<p>Citi\u021bi despre cum a fost creat graful de commit serializat \u00een <noindex><a rel=\"nofollow\" href=\"https:\/\/devblogs.microsoft.com\/devops\/supercharging-the-git-commit-graph\/\">seria de articole<\/a><\/noindex> de la unul dintre autorii acestei func\u021bii.<\/p>\n<p><\/p>\n<h3 id=\"dopolnitelnye-minuty-ci-runner-teper-i-dlya-besplatnyh-planov\">Minute suplimentare pentru CI Runner: acum \u0219i pentru planurile gratuite<\/h3>\n<p><\/p>\n<p><em>FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>Luna trecut\u0103, am ad\u0103ugat posibilitatea de a cump\u0103ra minute suplimentare pentru CI Runner, dar doar pentru planurile pl\u0103tite de GitLab.com. \u00cen aceast\u0103 versiune, minutele pot fi cump\u0103rate \u0219i pentru planurile gratuite.<\/p>\n<p><\/p>\n<h3 id=\"zagruzka-arhivov-direktoriy-v-repozitorii\">Desc\u0103rcarea arhivelor directoarelor din repozitorii<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>\u00cen func\u021bie de tipul \u0219i dimensiunea proiectului, arhiva \u00eentregului proiect poate fi desc\u0103rcat\u0103 lent \u0219i nu este \u00eentotdeauna necesar\u0103, \u00een special \u00een cazul monorepozitoriilor mari. \u00cen GitLab 11.11, pute\u021bi desc\u0103rca arhiva con\u021binutului directorului curent, inclusiv subdirectoarele, pentru a selecta doar folderele necesare.<\/p>\n<p><\/p>\n<p>Mul\u021bumim pentru munc\u0103, <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/kiameisomabes\">Kia Mei Somabes<\/a><\/noindex>!<\/p>\n<p><\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habrastorage.org\/webt\/uk\/hr\/3m\/ukhr3mowq-mhsxy_2_fixj2rkay.png\"><img decoding=\"async\" alt=\"GitLab 11.11: mai multe persoane responsabile pentru cererile de fuziune \u0219i \u00eembun\u0103t\u0103\u021biri pentru containere\" src=\"\/wp-content\/uploads\/2019\/05\/4d180f877e5e12a825c98e337487ae75.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/p>\n<p><\/p>\n<h3 id=\"primenenie-predlozheniya-teper-avtomaticheski-razreshaet-obsuzhdenie\">Aplicarea propunerii permite acum automat dezbaterea<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>Propunerea de modific\u0103ri faciliteaz\u0103 colaborarea asupra cererilor de integrare: acum se poate evita copierea \u0219i lipirea pentru a accepta modificarea propus\u0103. \u00cen GitLab 11.11 am simplificat \u0219i mai mult acest proces: acum dezbaterea se rezolv\u0103 automat la aplicarea propunerii.<\/p>\n<p>\n<center><div class=\"youtube-placeholder\" data-id=\"LUG8H46sXCI\" onclick=\"loadVideo(this)\">\r\n        <img decoding=\"async\" src=\"https:\/\/img.youtube.com\/vi\/LUG8H46sXCI\/hqdefault.jpg\" alt=\"Reda\u021bi video\" loading=\"lazy\" width=\"480\" height=\"360\" style=\"width:100%;height:auto;\">\r\n        <div class=\"play-button\"><\/div>\r\n    <\/div><\/center><\/p>\n<h3 id=\"schetchik-vremeni-na-bokovoy-paneli-doski-zadach\">Cronometru pe bara lateral\u0103 a tabloului de sarcini<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>Barele laterale ale sarcinilor trebuie s\u0103 arate identic \u00een vizualiz\u0103rile tabloului \u0219i ale sarcinilor. De aceea, GitLab are acum un cronometru pe bara lateral\u0103 a sarcinilor \u00een tabloul de sarcini. Pur \u0219i simplu accesa\u021bi tabloul de sarcini, face\u021bi clic pe sarcin\u0103, iar bara lateral\u0103 cu cronometru se va deschide.<\/p>\n<p><\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habrastorage.org\/webt\/w2\/5a\/mh\/w25amhv1medrejnpno8qndis1_e.png\"><img decoding=\"async\" alt=\"GitLab 11.11: mai multe persoane responsabile pentru cererile de fuziune \u0219i \u00eembun\u0103t\u0103\u021biri pentru containere\" src=\"\/wp-content\/uploads\/2019\/05\/dfb02562b94459721ac27638c9944fbf.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/p>\n<p><\/p>\n<h3 id=\"svedeniya-o-deployah-v-environments-api\">Informa\u021bii despre desf\u0103\u0219ur\u0103ri \u00een Environments API<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>Am ad\u0103ugat posibilitatea de a solicita informa\u021bii despre un mediu specific de la Environments API pentru a \u0219ti ce commit este desf\u0103\u0219urat \u00een mediu chiar acum. Acest lucru va simplifica automatizarea \u0219i raportarea pentru utilizatorii Environments \u00een GitLab.<\/p>\n<p><\/p>\n<h3 id=\"otricatelnye-sovpadeniya-peremennyh-dlya-pravil-payplayna\">Coeren\u021ba negativ\u0103 a variabilelor pentru regulile pipeline-ului<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>Acum este posibil s\u0103 verifica\u021bi inegalitatea negativ\u0103 sau potrivirea modelului (<code>!=<\/code> \u0219i <code>!~<\/code>) \u00een fi\u0219ier <code>.gitlab-ci.yml<\/code> la verificarea valorilor variabilelor de mediu, astfel \u00eenc\u00e2t controlul comportamentului pipeline-urilor devine mai flexibil.<\/p>\n<p><\/p>\n<h3 id=\"zapusk-vseh-vypolnyaemyh-vruchnuyu-dzhobov-na-etape-odnim-schelchkom\">Rularea tuturor joburilor manuale pe un singur pas cu un clic<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>\u00cen GitLab 11.11, utilizatorii care au multe joburi manuale la etape pot acum s\u0103 execute toate aceste joburi pe un singur pas, f\u0103c\u00e2nd clic pe butonul <strong>\u201eRulaj total\u201d<\/strong> (\u201ePlay all\u201d) din dreapta numelui etap\u0103i \u00een vizualizarea pipeline-urilor.<\/p>\n<p><\/p>\n<h3 id=\"sozdanie-fayla-napryamuyu-iz-peremennoy-sredy\">Crearea unui fi\u0219ier direct dintr-o variabil\u0103 de mediu<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>Variabilele de mediu sunt adesea utilizate pentru a crea fi\u0219iere, \u00een special pentru secrete care necesit\u0103 protec\u021bie \u0219i sunt disponibile doar \u00een anumite pipeline-uri de mediu. Pentru aceasta, seta\u021bi ca \u0219i con\u021binutul variabilei con\u021binutul fi\u0219ierului \u0219i crea\u021bi un fi\u0219ier \u00een job care con\u021bine valoarea. Cu noua variabil\u0103 de mediu de tip <code>file<\/code> aceasta se poate face \u00eentr-un singur pas, chiar \u0219i f\u0103r\u0103 modificarea <code>.gitlab-ci.yml.<\/code><\/p>\n<p><\/p>\n<h3 id=\"konechnaya-tochka-api-dlya-svedeniy-ob-uyazvimostyah\">Punct de terminare API pentru informa\u021bii despre vulnerabilit\u0103\u021bi<\/h3>\n<p><\/p>\n<p><em>ULTIMATE, GOLD<\/em><\/p>\n<p><\/p>\n<p>Acum pute\u021bi solicita de la GitLab API toate vulnerabilit\u0103\u021bile identificate \u00een proiect. Cu acest API, se pot crea liste de vulnerabilit\u0103\u021bi \u00een format ma\u0219inabil cu filtre pe tip, credibilitate \u0219i gravitate.<\/p>\n<p><\/p>\n<h3 id=\"vozmozhnost-polnogo-dinamicheskogo-skanirovaniya-dlya-dast\">Posibilitatea de scanare dinamic\u0103 complet\u0103 pentru DAST<\/h3>\n<p><\/p>\n<p><em>ULTIMATE, GOLD<\/em><\/p>\n<p><\/p>\n<p>\u00cen GitLab, pute\u021bi testa dinamic securitatea aplica\u021biilor (Dynamic Application Security Testing, DAST) \u00een cadrul pipeline-ului CI. \u00cencep\u00e2nd cu aceast\u0103 versiune, se poate alege scanarea dinamic\u0103 complet\u0103 \u00een locul scan\u0103rii pasive standard. Scanarea dinamic\u0103 complet\u0103 protejeaz\u0103 \u00eempotriva unui num\u0103r mai mare de vulnerabilit\u0103\u021bi.<\/p>\n<p><\/p>\n<h3 id=\"ustanovka-prometheus-v-klasterah-na-urovne-gruppy\">Instalarea Prometheus \u00een clustere la nivel de grup<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>\u00cen aceast\u0103 versiune, GitLab ofer\u0103 posibilitatea de a ata\u0219a un cluster Kubernetes \u00eentregului grup. De asemenea, am ad\u0103ugat op\u021biunea de a instala o instan\u021b\u0103 unic\u0103 de Prometheus pe acest cluster pentru a facilita monitorizarea tuturor proiectelor din cluster.<\/p>\n<p><\/p>\n<h3 id=\"svedeniya-ob-ignorirovanii-uyazvimostey-na-paneli-bezopasnosti\">Informa\u021bii despre ignorarea vulnerabilit\u0103\u021bilor pe tabloul de bord de securitate<\/h3>\n<p><\/p>\n<p><em>ULTIMATE, GOLD<\/em><\/p>\n<p><\/p>\n<p>Pe tablourile de bord de securitate GitLab, administratorii pot vizualiza vulnerabilit\u0103\u021bile ignorate. Pentru a optimiza fluxul de lucru, am ad\u0103ugat posibilitatea de a vizualiza informa\u021biile despre ignorare direct pe tabloul de bord de securitate.<\/p>\n<p><\/p>\n<h3 id=\"sozdanie-polzovatelskih-diagramm-metrik-na-paneli-monitoringa\">Crearea diagramelor personalizate de metrici pe tabloul de bord<\/h3>\n<p><\/p>\n<p><em>PREMIUM, ULTIMATE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>Creeaz\u0103 noi diagrame cu metrici personalizate de performan\u021b\u0103 direct pe tabloul de bord al metricilor. Acum utilizatorii pot crea, actualiza \u0219i \u0219terge vizualiz\u0103ri de metrici pe tabloul de bord, ap\u0103s\u00e2nd butonul <strong>\u201eAdaug\u0103 metric\u0103\u201d<\/strong> (\u201eAdd Metric\u201d) din col\u021bul din dreapta sus al tabloului de bord.<\/p>\n<p><\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habrastorage.org\/webt\/og\/hl\/b3\/oghlb329zijpvemwqjsxjo8qawa.png\"><img decoding=\"async\" alt=\"GitLab 11.11: mai multe persoane responsabile pentru cererile de fuziune \u0219i \u00eembun\u0103t\u0103\u021biri pentru containere\" src=\"\/wp-content\/uploads\/2019\/05\/4959332a02d70ddc932370a49a5797ed.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/p>\n<p><\/p>\n<h3 id=\"zadachi-iz-uvedomleniy-teper-otkryvayutsya-ot-imeni-gitlab-alert-bot\">Sarcinile din notific\u0103ri sunt acum deschise \u00een numele GitLab Alert Bot<\/h3>\n<p><\/p>\n<p><em>PREMIUM, ULTIMATE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>Acum sarcinile care se deschid din notific\u0103ri au ca autor GitLab Alert Bot, astfel \u00eenc\u00e2t s\u0103 vede\u021bi imediat c\u0103 sarcina a fost creat\u0103 automat dintr-o notificare important\u0103.<\/p>\n<p><\/p>\n<h3 id=\"avtosohranenie-opisaniy-epikov-v-lokalnoe-hranilische\">Autosalvarea descrierilor epicilor \u00een stocarea local\u0103<\/h3>\n<p><\/p>\n<p><em>ULTIMATE, GOLD<\/em><\/p>\n<p><\/p>\n<p>Descrierile epicilor nu erau salvate \u00een stocarea local\u0103, astfel \u00eenc\u00e2t modific\u0103rile se pierdeau dac\u0103 nu erau salvate explicit c\u00e2nd se schimba descrierea epicului. \u00cen GitLab 11.11 a fost introdus\u0103 posibilitatea de a salva descrierile epicilor \u00een stocarea local\u0103. Asta \u00eenseamn\u0103 c\u0103 acum po\u021bi reveni cu u\u0219urin\u021b\u0103 la modificarea descrierii epicului, dac\u0103 a ap\u0103rut o eroare, ai fost distras sau ai \u00eenchis accidental browserul.<\/p>\n<p><\/p>\n<h3 id=\"podderzhka-otzerkalivaniya-na-gitlab-dlya-git-lfs\">Suport pentru mirrorizare \u00een GitLab pentru Git LFS<\/h3>\n<p><\/p>\n<p><em>STARTER, PREMIUM, ULTIMATE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>Prin intermediul mirror-ului, pute\u021bi replica repositoarele Git dintr-un loc \u00een altul. Aceasta faciliteaz\u0103 stocarea pe serverul GitLab a unei copii a repositoarului situat \u00een alt\u0103 parte. Acum GitLab suport\u0103 mirroring-ul repositoarelor cu Git LFS, astfel \u00eenc\u00e2t aceast\u0103 func\u021bie este disponibil\u0103 chiar \u0219i pentru repositoarele cu fi\u0219iere mari, cum ar fi texturile pentru jocuri sau datele \u0219tiin\u021bifice.<\/p>\n<p><\/p>\n<h3 id=\"prava-na-chtenie-i-zapis-v-repozitorii-dlya-personalnyh-tokenov-dostupa\">Drepturile de citire \u0219i scriere \u00een repositoare pentru token-urile de acces personale<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>Multe token-uri de acces personale au permisiuni pentru modific\u0103ri la nivel <code>api<\/code>, dar accesul complet la API poate oferi prea multe drepturi unor utilizatori sau organiza\u021bii.<\/p>\n<p><\/p>\n<p>Datorit\u0103 contribu\u021biei comunit\u0103\u021bii, acum token-urile de acces personale pot avea drepturi de citire \u0219i scriere doar pentru repositoarele proiectului, f\u0103r\u0103 un acces mai profund la nivelul API-ului c\u0103tre zonele delicate ale GitLab, cum ar fi set\u0103rile \u0219i apartenen\u021ba.<\/p>\n<p><\/p>\n<p>Mul\u021bumim, Horatiu Eugen Vlad (<noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/hvlad\">Horatiu Eugen Vlad<\/a><\/noindex>)!<\/p>\n<p><\/p>\n<h3 id=\"dobavlenie-bazovoy-podderzhki-dlya-gruppovyh-zaprosov-graphql\">Ad\u0103ugarea unui suport de baz\u0103 pentru cererile de grup GraphQL<\/h3>\n<p><\/p>\n<p><em>FREE, BRONZE, SILVER, GOLD, CORE, STARTER, PREMIUM, ULTIMATE<\/em><\/p>\n<p><\/p>\n<p>Cu ajutorul API-ului GraphQL, utilizatorii pot specifica precis ce date au nevoie \u0219i pot ob\u021bine toate datele necesare \u00een c\u00e2teva cereri. \u00cencep\u00e2nd cu aceast\u0103 versiune, GitLab suport\u0103 ad\u0103ugarea informa\u021biilor de baz\u0103 despre grup \u00een API-ul GraphQL.<\/p>\n<p><\/p>\n<h3 id=\"vhod-s-uchetnymi-dannymi-salesforce\">Autentificare cu acreditivele Salesforce<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>GitLab apreciaz\u0103 dezvoltatorii de la Salesforce, iar pentru a sus\u021bine aceast\u0103 comunitate, permitem utilizatorilor s\u0103 se conecteze la GitLab cu acreditivele Salesforce.com. Acum, instan\u021bele pot fi configurate pentru a face din GitLab o aplica\u021bie conectat\u0103 la Salesforce, utiliz\u00e2nd Salesforce.com pentru a se autentifica pe GitLab cu un singur clic.<\/p>\n<p><\/p>\n<h3 id=\"saml-sso-teper-obyazatelen-dlya-veb-dostupa\">SAML SSO este acum obligatoriu pentru accesul web<\/h3>\n<p><\/p>\n<p><em>PREMIUM, ULTIMATE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>Noi <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ee\/issues\/5291\">extinderea cerin\u021bei de autentificare unic\u0103 (SSO)<\/a><\/noindex> la nivelul grupurilor, introdus\u0103 \u00een versiunea 11.8, cu o verificare riguroas\u0103 a resurselor grupului \u0219i proiectului, astfel \u00eenc\u00e2t utilizatorii s\u0103 poat\u0103 avea acces doar prin SAML. Acesta este un nivel suplimentar de control al accesului pentru organiza\u021biile care apreciaz\u0103 securitatea \u0219i utilizeaz\u0103 GitLab.com prin SAML SSO. Acum pute\u021bi face din SSO o cerin\u021b\u0103 obligatorie, \u0219tiind c\u0103 utilizatorii din grupul dvs. folosesc SSO.<\/p>\n<p><\/p>\n<h3 id=\"filtraciya-po-nedavno-sozdannym-ili-izmenennym-dannym-dlya-api-epikov\">Filtrare dup\u0103 date recent create sau modificate pentru API-ul epicilor<\/h3>\n<p><\/p>\n<p><em>ULTIMATE, GOLD<\/em><\/p>\n<p><\/p>\n<p>Anterior, a fost dificil s\u0103 solicita\u021bi datele recent create sau modificate folosind API-ul epicilor de pe GitLab. \u00cen versiunea 11.11, am adi\u021bionat filtre suplimentare <code>created_after<\/code>, <code>created_before<\/code>, <code>actualizat_dupa<\/code> \u0219i <code>actualizat_inainte<\/code>, pentru a asigura consisten\u021ba cu API-urile sarcinilor \u0219i a g\u0103si rapid epicele modificate sau recent create.<\/p>\n<p><\/p>\n<h3 id=\"biometricheskaya-autentifikaciya-s-ultraauth\">Autentificare biometric\u0103 cu UltraAuth<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>Compania <noindex>UltraAuth<\/noindex> se specializeaz\u0103 \u00een autentificarea biometric\u0103 f\u0103r\u0103 parol\u0103. Acum suport\u0103m aceast\u0103 metod\u0103 de autentificare pe GitLab!<\/p>\n<p><\/p>\n<p>Mul\u021bumesc, Kartikey Tanna (<noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/tannakartikey\">Kartikey Tanna<\/a><\/noindex>)!<\/p>\n<p><\/p>\n<h3 id=\"gitlab-runner-1111\">GitLab Runner 11.11<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>Ast\u0103zi am lansat GitLab Runner 11.11! GitLab Runner este un proiect open-source utilizat pentru a rula sarcini CI\/CD \u0219i a trimite rezultatele \u00eenapoi \u00een GitLab.<\/p>\n<p><\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/merge_requests\/1298\"><code>A fost corectat\u0103 problema \u00een care git lfs<\/code> nu primea obiectele submodulului.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/merge_requests\/1292\">A fost optimizat\u0103 procesarea tras\u0103rilor mari.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/merge_requests\/1321\">Parametrii func\u021biilor pot fi configura\u021bi folosind config.toml.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/merge_requests\/1319\"><code>Se pot utiliza parametrii func\u021biilor pentru a configura folderul \/builds<\/code>.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/merge_requests\/1243\">Ad\u0103ugarea suportului PowerShell pentru Executorul Docker.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/merge_requests\/1269\">Suport pentru configurarea volumelor Windows Docker.<\/a><\/noindex><\/li>\n<\/ul>\n<p><\/p>\n<h3 id=\"uluchsheniya-omnibus\">\u00cembun\u0103t\u0103\u021biri Omnibus<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE<\/em><\/p>\n<p><\/p>\n<p>Am adus urm\u0103toarele \u00eembun\u0103t\u0103\u021biri \u00een Omnibus \u00een GitLab 11.11:<\/p>\n<p><\/p>\n<ul>\n<li>GitLab 11.11 include <noindex><a rel=\"nofollow\" href=\"https:\/\/mattermost.com\/blog\/mattermost-5-10-single-sign-on-for-mobile-richer-integrations-and-more\/\">Mattermost 5.10<\/a><\/noindex> \u2014 <noindex><a rel=\"nofollow\" href=\"https:\/\/mattermost.com\/\">o alternativ\u0103 open-source la Slack<\/a><\/noindex>, cu mesaje efemere interactive \u0219i multe altele. Aceast\u0103 versiune con\u021bine <noindex><a rel=\"nofollow\" href=\"https:\/\/mattermost.com\/security-updates\/\">securitate<\/a><\/noindex>, \u0219i recomand\u0103m s\u0103 face\u021bi actualizarea.<\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/omnibus-gitlab\/merge_requests\/3241\"><code>Grafana a fost actualizat\u0103 la versiunea 1.1.0<\/code>, pentru a se alinia celor mai recente panouri de monitorizare Omnibus<\/a><\/noindex>.<\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/omnibus-gitlab\/merge_requests\/3142\">Pachetul PostreSQL 10 include acum Omnibus.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/omnibus-gitlab\/merge_requests\/3249\/diffs\"><code>DSN-ul Sentry poate fi acum trecut \u00een gitlab.yml<\/code>.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/omnibus-gitlab\/merge_requests\/3082\"><code>Actualizarea RubyGems la 2.7.9<\/code>.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/omnibus-gitlab\/merge_requests\/3197\"><code>Actualizarea liblzma<\/code> la <code>5.2.4<\/code> de <code>5.2.2<\/code>.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/omnibus-gitlab\/merge_requests\/3210\"><code>Actualizarea libtool<\/code> la <code>2.4.6<\/code>.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/omnibus-gitlab\/merge_requests\/3205\"><code>postresql porne\u0219te dup\u0103 comanda pg-upgrade<\/code>.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/omnibus-gitlab\/merge_requests\/3182\">Actualizarea componentelor Prometheus la cele mai recente versiuni.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/omnibus-gitlab\/merge_requests\/3220\"><code>Actualizarea git la 2.21.0<\/code>.<\/a><\/noindex><\/li>\n<\/ul>\n<p><\/p>\n<h3 id=\"uluchshenie-shem\">\u00cembun\u0103t\u0103\u021birea schemelor<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE<\/em><\/p>\n<p><\/p>\n<p>Am adus urm\u0103toarele \u00eembun\u0103t\u0103\u021biri la graficele Helm \u00een GitLab 11.11:<\/p>\n<p><\/p>\n<ul>\n<li>\u00cen GitLab 11.11, este posibil s\u0103 <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/charts\/gitlab\/issues\/705\">ata\u0219a\u021bi un volum pentru stocarea directorului tmp\/work<\/a><\/noindex>.<\/li>\n<li>Administratorii au acces <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/charts\/gitlab\/merge_requests\/776\">la op\u021biuni suplimentare de configurare<\/a><\/noindex>, inclusiv <code>memoryKiller<\/code>, <code>maxRss<\/code>, <code>graceTime<\/code> \u0219i <code>shutdownWait<\/code>.<\/li>\n<li>Graficele Helm sunt acum <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/charts\/gitlab\/issues\/1132\">testate continuu<\/a><\/noindex> \u00een Amazon Elastic Container Service for Kubernetes (<noindex><a rel=\"nofollow\" href=\"https:\/\/aws.amazon.com\/eks\/\">EKS<\/a><\/noindex>)<\/li>\n<\/ul>\n<p><\/p>\n<h3 id=\"uluchsheniya-proizvoditelnosti\">\u00cembun\u0103t\u0103\u021biri ale performan\u021bei<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>Continu\u0103m s\u0103 \u00eembun\u0103t\u0103\u021bim performan\u021ba GitLab cu fiecare lansare pentru instan\u021bele GitLab de orice dimensiune. Unele \u00eembun\u0103t\u0103\u021biri \u00een GitLab 11.11:<\/p>\n<p><\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ce\/merge_requests\/27866\">Accelerarea complet\u0103rii automate a utilizatorilor, atunci c\u00e2nd exist\u0103 multe c\u0103i c\u0103tre avatare \u00een r\u0103spuns.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ce\/merge_requests\/27825\">Reducerea sarcinii utile a Sidekiq-ului la \u0219tergerea todo-urilor.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ee\/merge_requests\/11575\">Calcularea complexit\u0103\u021bii rezolvatorului GraphQL pe baza elementelor.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ce\/merge_requests\/27817\">\u00cembun\u0103t\u0103\u021birea performan\u021bei c\u0103ut\u0103rii globale pentru obiectele emise.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ce\/merge_requests\/27413\">\u00cembun\u0103t\u0103\u021birea performan\u021bei la desf\u0103\u0219urarea unui fi\u0219ier diff complet.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ce\/merge_requests\/27625\">Cererea garantat\u0103 a obiectelor blob \u00eentr-un singur pachet.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ce\/merge_requests\/22801\">Lista paginilor Wiki va fi generat\u0103 f\u0103r\u0103 a \u00eenc\u0103rca con\u021binutul.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ce\/merge_requests\/24038\">Renun\u021barea la crearea de linkuri temporare pentru compararea ramurilor dintr-un singur proiect.<\/a><\/noindex><\/li>\n<\/ul>\n<p><\/p>\n<h2 id=\"ustarevshie-fichi\">Func\u021bii \u00eenvechite<\/h2>\n<p><\/p>\n<h3 id=\"gitlab-geo-obespechit-heshirovannoe-hranenie-v-gitlab-120\">GitLab Geo va asigura stocarea hash-at\u0103 \u00een GitLab 12.0<\/h3>\n<p><\/p>\n<p>GitLab Geo este necesar <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.gitlab.com\/ee\/administration\/repository_storage_types.html#hashed-storage\">stocare hash-at\u0103<\/a><\/noindex> pentru a reduce concuren\u021ba pe nodurile secundare. Acest lucru a fost men\u021bionat \u00een <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ce\/issues\/40970\">gitlab-ce#40970<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>\u00cen GitLab <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/groups\/gitlab-org\/-\/milestones\/20\">11.5<\/a><\/noindex> am ad\u0103ugat aceast\u0103 cerin\u021b\u0103 \u00een documenta\u021bia Geo: <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ee\/issues\/8053\">gitlab-ee#8053<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>\u00cen GitLab <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/groups\/gitlab-org\/-\/milestones\/21\">11.6<\/a><\/noindex> <code>sudo gitlab-rake gitlab:geo:check<\/code> verific\u0103 dac\u0103 stocarea hash-at\u0103 este activat\u0103 \u0219i dac\u0103 toate proiectele sunt migrate. Vezi <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ee\/issues\/8289\">gitlab-ee#8289<\/a><\/noindex>. Dac\u0103 folose\u0219ti Geo, te rug\u0103m s\u0103 rulezi aceast\u0103 verificare \u0219i s\u0103 migrezi c\u00e2t mai cur\u00e2nd posibil.<\/p>\n<p><\/p>\n<p>\u00cen GitLab <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/groups\/gitlab-org\/-\/milestones\/23\">11.8<\/a><\/noindex> o avertizare constant dezactivabil\u0103 va fi afi\u0219at\u0103 pe pagin\u0103 <strong>Zona Admin \u203a Geo \u203a Noduri<\/strong>, \u00een cazul \u00een care verific\u0103rile men\u021bionate nu sunt permise. <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ee\/merge_requests\/8433\">gitlab-ee!8433<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>\u00cen GitLab <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/groups\/gitlab-org\/-\/milestones\/33\">12.0<\/a><\/noindex> Geo va utiliza cerin\u021bele pentru stocarea hash-at\u0103. Vezi <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ee\/issues\/8690\">gitlab-ee#8690<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>Data elimin\u0103rii: <strong>22 iunie 2019.<\/strong><\/p>\n<p><\/p>\n<h3 id=\"gitlab-geo-obespechit-ispolzovanie-pg-fdw-v-gitlab-120\">GitLab Geo va permite utilizarea PG FDW \u00een GitLab 12.0<\/h3>\n<p><\/p>\n<p>Acest lucru este necesar pentru Geo Log Cursor, deoarece \u00eembun\u0103t\u0103\u021be\u0219te semnificativ performan\u021ba unor opera\u021biuni de sincronizare. De asemenea, cre\u0219te performan\u021ba interog\u0103rilor de stare ale nodurilor Geo. Interog\u0103rile anterioare aveau o performan\u021b\u0103 prea mic\u0103 \u00een proiectele mari. Vezi cum s\u0103 configurezi acest lucru \u00een <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.gitlab.com\/ee\/administration\/geo\/replication\/database.html\">replicarea bazei de date Geo<\/a><\/noindex>. \u00cen GitLab <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/groups\/gitlab-org\/-\/milestones\/33\">12.0<\/a><\/noindex> Geo va necesita PG FDW. Vezi <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ee\/issues\/11006\">gitlab-ee#11006<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>Data elimin\u0103rii: <strong>22 iunie 2019.<\/strong><\/p>\n<p><\/p>\n<h3 id=\"parametry-sentry-dlya-otchetov-ob-oshibkah-i-logirovaniya-budut-udaleny-iz-polzovatelskogo-interfeysa-v-gitlab-120\">Op\u021biunile Sentry pentru rapoartele de erori \u0219i logare vor fi eliminate din interfa\u021ba utilizatorului \u00een GitLab 12.0<\/h3>\n<p><\/p>\n<p>Aceste op\u021biuni vor fi eliminate din interfa\u021ba utilizatorului \u00een GitLab 12.0 \u0219i vor fi disponibile \u00een fi\u0219ierul <code>gitlab.yml<\/code>. \u00cen plus, vei putea defini mediu Sentry pentru a distinge \u00eentre mai multe implement\u0103ri. De exemplu, dezvoltare, staging \u0219i produc\u021bie. Vezi <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ce\/issues\/49771\">gitlab-ce#49771<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>Data elimin\u0103rii: <strong>22 iunie 2019.<\/strong><\/p>\n<p><\/p>\n<h3 id=\"ogranichenie-maksimalnogo-kolichestva-payplaynov-sozdavaemyh-odnoy-otpravkoy\">Limitarea num\u0103rului maxim de pipeline-uri create de o singur\u0103 trimitere<\/h3>\n<p><\/p>\n<p>Anterior, GitLab crea pipeline-uri pentru <code>HEAD<\/code> fiecare ramur\u0103 din trimitere. Aceasta este convenabil\u0103 pentru dezvoltatori care trimit mai multe modific\u0103ri deodat\u0103 (de exemplu, \u00een ramura de func\u021bionalitate \u0219i \u00een ramura <code>develop<\/code>).<\/p>\n<p><\/p>\n<p>\u00cens\u0103, atunci c\u00e2nd se trimite un depozit mare, unde exist\u0103 multe ramuri active (de exemplu, pentru mutare, replicare sau ramificare), nu este necesar s\u0103 se creeze un pipeline pentru fiecare ramur\u0103. \u00cencep\u00e2nd cu GitLab 11.10, cre\u0103m <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ce\/merge_requests\/27205\">maxim 4 pipeline-uri<\/a><\/noindex> la trimitere.<\/p>\n<p><\/p>\n<p>Data elimin\u0103rii: <strong>22 mai 2019.<\/strong><\/p>\n<p><\/p>\n<h3 id=\"ustarevshie-puti-legacy-koda-gitlab-runner\">C\u0103r\u021bi de cod legacy \u00eenvechite ale GitLab Runner<\/h3>\n<p><\/p>\n<p>\u00cencep\u00e2nd cu Gitlab 11.9, GitLab Runner folose\u0219te <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/merge_requests\/1203\">metoda nou\u0103 <\/a><\/noindex> clon\u0103rii\/apel\u0103rii repository-ului. \u00cen prezent, GitLab Runner va utiliza vechea metod\u0103, dac\u0103 noua nu este suportat\u0103. Afla\u021bi mai multe \u00een <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/issues\/4069\">aceast\u0103 sarcin\u0103<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>\u00cen GitLab 11.0 am modificat structura de configurare a serverului de metrici pentru GitLab Runner. <code>metrics_server<\/code>va fi eliminat \u00een favoarea <code>listen_address<\/code> \u00een GitLab 12.0. Afla\u021bi mai multe \u00een <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/issues\/4072\">aceast\u0103 sarcin\u0103<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>\u00cen versiunea 11.3, GitLab Runner a \u00eenceput s\u0103 suporte <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/merge_requests\/968\">mai mul\u021bi furnizori de cache<\/a><\/noindex>; ceea ce a dus la noi set\u0103ri pentru <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.gitlab.com\/runner\/configuration\/advanced-configuration.html#the-runnerscaches3-section\">configurarea specific\u0103 S3<\/a><\/noindex>. \u00cen <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.gitlab.com\/runner\/configuration\/advanced-configuration.html#the-runnerscache-section\">documentation<\/a><\/noindex> este prezentat\u0103 o tabel\u0103 cu modific\u0103rile \u0219i instruc\u021biuni pentru tranzi\u021bia la noua configura\u021bie. Afla\u021bi mai multe \u00een <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/issues\/4070\">aceast\u0103 sarcin\u0103<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>Aceste c\u0103i nu vor fi disponibile \u00een GitLab 12.0. Ca utilizator, nu trebuie s\u0103 schimba\u021bi nimic, doar asigura\u021bi-v\u0103 c\u0103 instan\u021ba GitLab func\u021bioneaz\u0103 cu versiunea 11.9+ atunci c\u00e2nd face\u021bi upgrade la GitLab Runner 12.0.<\/p>\n<p><\/p>\n<p>Data elimin\u0103rii: <strong>22 iunie 2019.<\/strong><\/p>\n<p><\/p>\n<h3 id=\"ustarevshiy-parametr-dlya-fichi-tochki-vhoda-dlya-gitlab-runner\">Parametrul \u00eenvechit pentru func\u021bia de punct de intrare pentru GitLab Runner<\/h3>\n<p><\/p>\n<p>\u00cen 11.4, GitLab Runner a introdus parametrul func\u021biei <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.gitlab.com\/runner\/configuration\/feature-flags.html#available-feature-flags\"><code>FF_K8S_USE_ENTRYPOINT_OVER_COMMAND<\/code><\/a><\/noindex> pentru a remedia probleme precum <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/issues\/2338\">#2338<\/a><\/noindex> \u0219i <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/issues\/3536\">#3536<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>\u00cen GitLab 12.0, ne vom schimba comportamentul pentru a fi corect, ca \u0219i cum parametrul func\u021biei ar fi dezactivat. Afla\u021bi mai multe \u00een <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/issues\/4073\">aceast\u0103 sarcin\u0103<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>Data elimin\u0103rii: <strong>22 iunie 2019.<\/strong><\/p>\n<p><\/p>\n<h3 id=\"ustarevshaya-podderzhka-distributiva-linux-dostigshego-eol-dlya-gitlab-runner\">Suportul \u00eenvechit pentru distribu\u021biile Linux care au ajuns la EOL pentru GitLab Runner<\/h3>\n<p><\/p>\n<p>Unele distribuiti Linux \u00een care poate fi instalat GitLab Runner \u0219i-au \u00eencheiat ciclul de via\u021b\u0103.<\/p>\n<p><\/p>\n<p>\u00cen GitLab 12.0, GitLab Runner nu va mai distribui pachete pentru aceste distribu\u021bii Linux. Lista complet\u0103 a distribu\u021biilor care nu mai sunt suportate poate fi g\u0103sit\u0103 \u00een <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.gitlab.com\/runner\/install\/linux-repository.html\">documentation<\/a><\/noindex>. Mul\u021bumesc, Javier Jard\u00f3n (<noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/jjardon\">Javier Jard\u00f3n<\/a><\/noindex>), pentru <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/merge_requests\/1130\">contribu\u021bia ta<\/a><\/noindex>!<\/p>\n<p><\/p>\n<p>Data elimin\u0103rii: <strong>22 iunie 2019.<\/strong><\/p>\n<p><\/p>\n<h3 id=\"udalenie-staryh-komand-gitlab-runner-helper\">Eliminarea comenzilor vechi GitLab Runner Helper<\/h3>\n<p><\/p>\n<p>\u00cen cadrul ad\u0103ug\u0103rii suportului pentru <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/groups\/gitlab-org\/-\/epics\/535\">executorul Docker Windows<\/a><\/noindex> a fost necesar s\u0103 renun\u021b\u0103m la unele comenzi vechi folosite pentru <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.gitlab.com\/runner\/configuration\/advanced-configuration.html#helper-image\">helper image<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>\u00cen GitLab 12.0, GitLab Runner se va lansa cu noi comenzi. Acest lucru se aplic\u0103 doar utilizatorilor care <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.gitlab.com\/runner\/configuration\/advanced-configuration.html#overriding-the-helper-image\">subliniind helper image<\/a><\/noindex>. Afla\u021bi mai multe \u00een <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/issues\/4013\">aceast\u0103 sarcin\u0103<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>Data elimin\u0103rii: <strong>22 iunie 2019.<\/strong><\/p>\n<p><\/p>\n<h3 id=\"udalenie-legacy-mehanizma-git-clean-iz-gitlab-runner\">Eliminarea mecanismului git clean legacy din GitLab Runner<\/h3>\n<p><\/p>\n<p>\u00cen GitLab Runner 11.10 am <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/merge_requests\/1281\">oferit posibilitatea<\/a><\/noindex> de a configura modul \u00een care Runner execut\u0103 comanda <code>git clean<\/code>. \u00cen plus, noua strategie de cur\u0103\u021bare elimin\u0103 utilizarea <code>git reset<\/code> \u0219i plaseaz\u0103 comanda <code>git clean<\/code> dup\u0103 etapa de desc\u0103rcare.<\/p>\n<p><\/p>\n<p>Deoarece aceast\u0103 schimbare de comportament poate afecta anumi\u021bi utilizatori, am preg\u0103tit parametrul <code>FF_USE_LEGACY_GIT_CLEAN_STRATEGY<\/code>. Dac\u0103 se seteaz\u0103 valoarea <code>true<\/code>, va restaura strategia de cur\u0103\u021bare legacy. Mai multe informa\u021bii despre utilizarea parametrilor de func\u021bii \u00een GitLab Runner pot fi g\u0103site <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.gitlab.com\/runner\/configuration\/feature-flags.html\">\u00een documenta\u021bie<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>\u00cen GitLab Runner 12.0, vom elimina suportul pentru strategia de cur\u0103\u021bare legacy \u0219i posibilitatea de a o restabili printr-un parametru de func\u021bie. Consulta\u021bi <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/issues\/4175\">aceast\u0103 sarcin\u0103<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>Data elimin\u0103rii: <strong>22 iunie 2019.<\/strong><\/p>\n<p><\/p>\n<h3 id=\"shablony-gruppovyh-proektovhttpsdocsgitlabcomeeusergroupcustom_project_templateshtmlcustom-group-level-project-templates-premium-only-dostupny-tolko-dlya-planov-silverpremium\"><noindex><a rel=\"nofollow\" href=\"https:\/\/docs.gitlab.com\/ee\/user\/group\/custom_project_templates.html#custom-group-level-project-templates-premium-only\">\u0218abloanele proiectelor de grup<\/a><\/noindex> sunt disponibile doar pentru planurile Silver\/Premium<\/h3>\n<p><\/p>\n<p>C\u00e2nd am introdus \u0219abloanele de proiect la nivel de grup \u00een versiunea 11.6, din gre\u0219eal\u0103 am f\u0103cut aceast\u0103 caracteristic\u0103 pentru Premium\/Silver disponibil\u0103 pentru toate planurile.<\/p>\n<p><\/p>\n<p>Noi <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ee\/issues\/10926\">remediem aceast\u0103 eroare<\/a><\/noindex> \u00een versiunea 11.11 \u0219i oferim \u00eenc\u0103 3 luni tuturor utilizatorilor \u0219i instan\u021belor sub nivelul Silver\/Premium.<\/p>\n<p><\/p>\n<p>\u00cencep\u00e2nd cu 22 august 2019, \u0219abloanele proiectelor de grup vor fi disponibile doar pentru planul Silver\/Premium \u0219i superior, a\u0219a cum este descris \u00een documenta\u021bie.<\/p>\n<p><\/p>\n<p>Data elimin\u0103rii: <strong>22 august 2019.<\/strong><\/p>\n<p><\/p>\n<h3 id=\"prekraschena-podderzhka-paketnyh-zadaniy-windows\">Suportul pentru joburile de tip batch Windows a fost oprit<\/h3>\n<p><\/p>\n<p>\u00cen GitLab 13.0 (22 iunie 2020), planific\u0103m s\u0103 renun\u021b\u0103m la suportul pentru joburile batch \u00een linia de comand\u0103 Windows \u00een GitLab Runner (de exemplu, <code>cmd.exe<\/code>) \u00een favoarea unui suport extins pentru Windows PowerShell. Mai multe detalii \u00een <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/issues\/4163\">aceast\u0103 sarcin\u0103<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>Acum viziunea noastr\u0103 despre DevOps de tip enterprise va corespunde pozi\u021biei Microsoft c\u0103 PowerShell este cea mai bun\u0103 op\u021biune pentru automatizarea aplica\u021biilor enterprise \u00een medii Windows. Dac\u0103 dori\u021bi s\u0103 continua\u021bi s\u0103 utiliza\u021bi <code>cmd.exe<\/code>, aceste comenzi pot fi apelate din PowerShell, dar nu vom sus\u021bine direct joburile batch Windows din cauza mai multor neconcordan\u021be care duc la costuri ridicate de \u00eentre\u021binere \u0219i dezvoltare.<\/p>\n<p><\/p>\n<p>Data elimin\u0103rii: <strong>22 septembrie 2019.<\/strong><\/p>\n<p><\/p>\n<h3 id=\"trebuetsya-git-2210-ili-vyshe\">Este necesar Git 2.21.0 sau mai recent<\/h3>\n<p><\/p>\n<p>\u00cencep\u00e2nd cu GitLab 11.11, este necesar Git 2.21.0 pentru a rula. <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/omnibus-gitlab\/merge_requests\/3220\">Omnibus GitLab vine deja cu Git 2.21.0<\/a><\/noindex>, dar utilizatorii instal\u0103rilor surs\u0103 cu versiuni anterioare de Git vor trebui s\u0103 fac\u0103 upgrade.<\/p>\n<p><\/p>\n<p>Data elimin\u0103rii: <strong>22 mai 2019.<\/strong><\/p>\n<p><\/p>\n<h3 id=\"ustarevshiy-shablon-servisa-kubernetes\">\u0218ablonul de serviciu Kubernetes este \u00eenvechit<\/h3>\n<p><\/p>\n<p>\u00cen GitLab 12.0, planific\u0103m s\u0103 renun\u021b\u0103m la \u0219ablonul de serviciu Kubernetes <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ce\/issues\/39840\">la nivel de instan\u021b\u0103<\/a><\/noindex> \u00een favoarea configura\u021biei clusterei la nivel de instan\u021b\u0103, introdus\u0103 \u00een GitLab 11.11.<\/p>\n<p><\/p>\n<p>Toate instan\u021bele autogestionate care folosesc \u0219ablonul de serviciu vor fi migrate la clusterul la nivel de instan\u021b\u0103 la upgrade-ul la GitLab 12.0.<\/p>\n<p><\/p>\n<p>Data elimin\u0103rii: <strong>22 iunie 2019.<\/strong><\/p>\n<p><\/p>\n<h3 id=\"otkaz-ot-sopostavleniya-po-yarlyku-app-na-panelyah-deploya-kubernetes\">Renun\u021barea la maparea dup\u0103 etichet\u0103 <code>app<\/code> pe panourile de desf\u0103\u0219urare Kubernetes<\/h3>\n<p><\/p>\n<p>\u00cen GitLab 12.0, planific\u0103m s\u0103 renun\u021b\u0103m la maparea dup\u0103 eticheta app \u00een selectorul de desf\u0103\u0219ur\u0103ri Kubernetes. \u00cen GitLab 11.10, am introdus <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ee\/issues\/9221\">un nou mecanism de mapare<\/a><\/noindex>, care caut\u0103 coresponden\u021be dup\u0103 <code>app.example.com\/app<\/code> \u0219i <code>app.example.com\/env<\/code>, pentru a afi\u0219a desf\u0103\u0219ur\u0103rile pe panou.<\/p>\n<p><\/p>\n<p>Pentru ca aceste desf\u0103\u0219ur\u0103ri s\u0103 fie afi\u0219ate pe panourile de desf\u0103\u0219urare, trebuie doar s\u0103 trimite\u021bi o nou\u0103 desf\u0103\u0219urare, iar GitLab va aplica noile etichete.<\/p>\n<p><\/p>\n<p>Data elimin\u0103rii: <strong>22 iunie 2019.<\/strong><\/p>\n<p><\/p>\n<h3 id=\"pakety-gitlab-120-budut-podpisyvatsya-rasshirennoy-podpisyu\">Pachetele GitLab 12.0 vor fi semnate cu o semn\u0103tur\u0103 extins\u0103<\/h3>\n<p><\/p>\n<p>2 mai 2019 GitLab <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/omnibus-gitlab\/issues\/3897\">a extins perioada de valabilitate a cheilor de semnare pentru pachete<\/a><\/noindex> Omnibus GitLab din 01.08.2019 p\u00e2n\u0103 pe 01.07.2020. Dac\u0103 verifica\u021bi semn\u0103turile pachetului \u0219i dori\u021bi s\u0103 actualiza\u021bi cheile, urma\u021bi din nou instruc\u021biunile din <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.gitlab.com\/omnibus\/update\/package_signatures.html\">documenta\u021bia pentru semnarea pachetelor Omnibus<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>Data elimin\u0103rii: <strong>22 iunie 2019.<\/strong><\/p>\n<p><\/p>\n<h3 id=\"zhurnal-izmeneniy\">Jurnal de modific\u0103ri<\/h3>\n<p><\/p>\n<p>C\u0103uta\u021bi toate aceste modific\u0103ri \u00een jurnalul de modific\u0103ri:<\/p>\n<p><\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ce\/blob\/master\/CHANGELOG.md\">GitLab Community Edition<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ee\/blob\/master\/CHANGELOG-EE.md\">GitLab Enterprise Edition<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/blob\/master\/CHANGELOG.md\">GitLab Runner<\/a><\/noindex><\/li>\n<\/ul>\n<p><\/p>\n<h3 id=\"ustanovka\">Instalare<\/h3>\n<p><\/p>\n<p>Dac\u0103 configura\u021bi o nou\u0103 instalare GitLab, vizita\u021bi <noindex><a rel=\"nofollow\" href=\"https:\/\/about.gitlab.com\/install\/\">pagina de desc\u0103rcare GitLab<\/a><\/noindex>.<\/p>\n<p><\/p>\n<h3 id=\"obnovlenie\">Actualizare<\/h3>\n<p><\/p>\n<p>\u2192 Uita\u021bi-v\u0103 la <noindex><a rel=\"nofollow\" href=\"https:\/\/about.gitlab.com\/update\/\">pagina actualiz\u0103rilor<\/a><\/noindex><\/p>\n<p>Sursa: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/southbridge\/blog\/453818\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0411\u043e\u043b\u044c\u0448\u0435 \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u0435\u0439 \u0434\u043b\u044f \u0441\u043e\u0432\u043c\u0435\u0441\u0442\u043d\u043e\u0439 \u0440\u0430\u0431\u043e\u0442\u044b \u0438 \u0434\u043e\u043f\u043e\u043b\u043d\u0438\u0442\u0435\u043b\u044c\u043d\u044b\u0435 \u0443\u0432\u0435\u0434\u043e\u043c\u043b\u0435\u043d\u0438\u044f \u041c\u044b \u0432 GitLab \u043f\u043e\u0441\u0442\u043e\u044f\u043d\u043d\u043e \u0438\u0449\u0435\u043c \u043d\u043e\u0432\u044b\u0435 \u0441\u043f\u043e\u0441\u043e\u0431\u044b \u0443\u043b\u0443\u0447\u0448\u0438\u0442\u044c \u0441\u043e\u0432\u043c\u0435\u0441\u0442\u043d\u0443\u044e \u0440\u0430\u0431\u043e\u0442\u0443 \u043f\u043e \u0432\u0441\u0435\u043c\u0443 \u0436\u0438\u0437\u043d\u0435\u043d\u043d\u043e\u043c\u0443 \u0446\u0438\u043a\u043b\u0443 DevOps. \u041c\u044b \u0441 \u0440\u0430\u0434\u043e\u0441\u0442\u044c\u044e \u043e\u0431\u044a\u044f\u0432\u043b\u044f\u0435\u043c, \u0447\u0442\u043e \u0441 \u044d\u0442\u043e\u0433\u043e \u0432\u044b\u043f\u0443\u0441\u043a\u0430 \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u0438\u0432\u0430\u0435\u043c \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u043e\u0442\u0432\u0435\u0442\u0441\u0442\u0432\u0435\u043d\u043d\u044b\u0445 \u043b\u0438\u0446 \u0434\u043b\u044f \u043e\u0434\u043d\u043e\u0433\u043e \u043c\u0435\u0440\u0434\u0436-\u0440\u0435\u043a\u0432\u0435\u0441\u0442\u0430! \u042d\u0442\u0430 \u0444\u0443\u043d\u043a\u0446\u0438\u044f \u0434\u043e\u0441\u0442\u0443\u043f\u043d\u0430 \u0441 \u0443\u0440\u043e\u0432\u043d\u044f GitLab Starter \u0438 \u043f\u043e-\u043d\u0430\u0441\u0442\u043e\u044f\u0449\u0435\u043c\u0443 \u0432\u043e\u043f\u043b\u043e\u0449\u0430\u0435\u0442 \u043d\u0430\u0448 \u0434\u0435\u0432\u0438\u0437: \u00ab\u041a\u0430\u0436\u0434\u044b\u0439 \u043c\u043e\u0436\u0435\u0442 \u0432\u043d\u0435\u0441\u0442\u0438 \u0441\u0432\u043e\u0439 \u0432\u043a\u043b\u0430\u0434\u00bb. [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":26134,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-34683","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.2.1 - aioseo.com -->\n\t<meta name=\"description\" content=\".\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/gitlab-11-11-neskolko-otvetstvennyh-dlya-merdzh-rekvestov-i-uluchsheniya-dlya-kontejnerov\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"ro_RO\" \/>\n\t\t<meta property=\"og:site_name\" content=\"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\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47GitLab 11.11: \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u043e\u0442\u0432\u0435\u0442\u0441\u0442\u0432\u0435\u043d\u043d\u044b\u0445 \u0434\u043b\u044f \u043c\u0435\u0440\u0434\u0436-\u0440\u0435\u043a\u0432\u0435\u0441\u0442\u043e\u0432 \u0438 \u0443\u043b\u0443\u0447\u0448\u0435\u043d\u0438\u044f \u0434\u043b\u044f \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u043e\u0432 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\".\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/gitlab-11-11-neskolko-otvetstvennyh-dlya-merdzh-rekvestov-i-uluchsheniya-dlya-kontejnerov\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-10-31T18:59:48+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T18:59:48+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47GitLab 11.11: c\u00e2teva responsabilit\u0103\u021bi pentru cererile de fuziune \u0219i \u00eembun\u0103t\u0103\u021biri pentru containere | ProHoster","description":".","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/gitlab-11-11-neskolko-otvetstvennyh-dlya-merdzh-rekvestov-i-uluchsheniya-dlya-kontejnerov","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\udd47GitLab 11.11: \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u043e\u0442\u0432\u0435\u0442\u0441\u0442\u0432\u0435\u043d\u043d\u044b\u0445 \u0434\u043b\u044f \u043c\u0435\u0440\u0434\u0436-\u0440\u0435\u043a\u0432\u0435\u0441\u0442\u043e\u0432 \u0438 \u0443\u043b\u0443\u0447\u0448\u0435\u043d\u0438\u044f \u0434\u043b\u044f \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u043e\u0432 | ProHoster","og:description":".","og:url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/gitlab-11-11-neskolko-otvetstvennyh-dlya-merdzh-rekvestov-i-uluchsheniya-dlya-kontejnerov","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:59:48+00:00","article:modified_time":"2019-10-31T18:59:48+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"34683","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-01-21 20:12:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 02:16:33","updated":"2026-01-21 20:12:19","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\/34683","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=34683"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/34683\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/26134"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=34683"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=34683"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=34683"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}