{"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\/et\/blog\/administrirovanie\/gitlab-11-11-neskolko-otvetstvennyh-dlya-merdzh-rekvestov-i-uluchsheniya-dlya-kontejnerov","title":{"rendered":"GitLab 11.11: mitu vastutavat isikut merge-p\u00e4ringutele ja t\u00e4iustused konteineritele","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"GitLab 11.11: mitu vastutavat isikut merge-p\u00e4ringutele ja t\u00e4iustused konteineritele\" 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\">Rohkem v\u00f5imalusi koost\u00f6\u00f6ks ja lisateated<\/h3>\n<p><\/p>\n<p>GitLabis otsime pidevalt uusi viise, kuidas parandada koost\u00f6\u00f6d kogu DevOpsi eluts\u00fckli v\u00e4ltel. Meil on hea meel teatada, et alates sellest v\u00e4ljalaskest toetame <noindex><a rel=\"nofollow\" href=\"https:\/\/about.gitlab.com\/2019\/05\/22\/gitlab-11-11-released\/#multiple-assignees-for-merge-requests\">mitut vastutavat isikut \u00fche merge request'i jaoks<\/a><\/noindex>! See funktsioon on saadaval GitLab Starter tasemelt ja t\u00f5eliselt kehastab meie motto: <strong>\u201eIga\u00fchel on v\u00f5imalus panustada\u201c<\/strong>. Teame, et \u00fche merge request'i juures v\u00f5ib t\u00f6\u00f6tada palju inimesi, et k\u00f5ik oleks \u00f5igesti, ja n\u00fc\u00fcd on teil v\u00f5imalus m\u00e4\u00e4rata mitu vastutavat isikut merge request'ide korral!<\/p>\n<p><\/p>\n<p>Ja DevOps meeskonnad saavad n\u00fc\u00fcd <noindex><a rel=\"nofollow\" href=\"https:\/\/about.gitlab.com\/2019\/05\/22\/gitlab-11-11-released\/#deployment-notifications-for-slack-and-mattermost\">automaatseid teateid juurutamise s\u00fcndmustest Slackis ja Mattermostis<\/a><\/noindex>. Lisage need uued teated nende kahe chat'i h\u00e4\u00e4lestamise s\u00fcndmuste nimekirja ja teie meeskond saab peaaegu kohe teada uutest juurutamistest.<\/p>\n<p><\/p>\n<h3 id=\"sokraschenie-izderzhek-s-podderzhkoy-konteynerov-docker-v-windows-i-podgotovkoy-klasterov-kubernetes-na-urovne-ekzemplyara\">Kulude v\u00e4hendamine Docker konteinerite toetamisega Windowsis ja Kubernetes klastrite ettevalmistamine instantsi tasemel<\/h3>\n<p><noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<p>Me armastame konteinereid! Konteinerid kasutavad v\u00e4hem s\u00fcsteemi ressursse v\u00f5rreldes virtuaalmasinate ja parandavad rakenduste kaasaskantavust. Alates GitLab 11.11 v\u00e4ljalaskest toetame <noindex><a rel=\"nofollow\" href=\"https:\/\/about.gitlab.com\/2019\/05\/22\/gitlab-11-11-released\/#windows-container-executor-for-gitlab-runner\">Windows Container Executor GitLab Runner'ile<\/a><\/noindex>, seega saate n\u00fc\u00fcd kasutada Docker konteinerite Windowsis ja nautida laienenud orkestreerimise, torude ja haldamise v\u00f5imalusi.<\/p>\n<p><\/p>\n<p>GitLab Premium (ainult iseseisvalt hallatavatele instantsidele) pakub n\u00fc\u00fcd <noindex><a rel=\"nofollow\" href=\"https:\/\/about.gitlab.com\/2019\/05\/22\/gitlab-11-11-released\/#caching-dependency-proxy-for-container-registry\">vahem\u00e4luproksit s\u00f5ltuvuste jaoks Docker piltide jaoks<\/a><\/noindex>. See t\u00e4iendus kiirendab tarnimist, kuna n\u00fc\u00fcd on teil vahem\u00e4luproks sageli kasutatavatele Docker piltidele.<\/p>\n<p><\/p>\n<p>Iseseisvalt hallatavad GitLab'i kasutajad saavad n\u00fc\u00fcd ette valmistada <noindex><a rel=\"nofollow\" href=\"https:\/\/about.gitlab.com\/2019\/05\/22\/gitlab-11-11-released\/#instance-level-kubernetes-cluster-configuration\">Kubernetes klastrit instantside tasemel<\/a><\/noindex>, ja k\u00f5ik grupid ja projektid instantsis kasutavad seda oma juurutamiseks. T\u00e4nu sellele integreerimisele loob GitLab koos Kubernetes'ega automaatselt ressursid konkreetsete projektide jaoks lisaturvalisuse saavutamiseks.<\/p>\n<p><\/p>\n<h3 id=\"i-eto-esche-ne-vse\">Ja see pole veel k\u00f5ik!<\/h3>\n<p><\/p>\n<p>Lisaks uutele koost\u00f6\u00f6v\u00f5imalustele ja lisateadetele oleme lisanud <noindex><a rel=\"nofollow\" href=\"https:\/\/about.gitlab.com\/2019\/05\/22\/gitlab-11-11-released\/#guest-access-to-releases\">k\u00fclalisjuurdep\u00e4\u00e4su versioonidele<\/a><\/noindex>, suurendanud <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\">t\u00e4iendavaid CI Runneri minuteid GitLab Free'ile<\/a><\/noindex>, lihtsustanud \u00fclevaatust <noindex><a rel=\"nofollow\" href=\"https:\/\/about.gitlab.com\/2019\/05\/22\/gitlab-11-11-released\/#applying-a-suggestion-now-automatically-resolves-the-discussion\">automaatse arutelu lahendamise kaudu, kui rakendate soovitust<\/a><\/noindex>, ja palju muud!<\/p>\n<p><\/p>\n<blockquote><p>Selle kuu v\u00e4\u00e4rtuslik t\u00f6\u00f6taja (<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>Selles v\u00e4ljaandes lisasime v\u00f5imaluse laadida alla \u00fcksikuid kaustasid repositooriumidest, mitte kogu sisu. N\u00fc\u00fcd saate alla laadida vaid m\u00f5ned vajalikud failid. Ait\u00e4h, Kia Mei Somabes!<\/p><\/blockquote>\n<p><\/p>\n<h2 id=\"glavnye-fichi-gitlab-1111\">GitLabi 11.11 peamised funktsioonid<\/h2>\n<p><\/p>\n<h3 id=\"windows-container-executor-dlya-gitlab-runner\">Windows Container Executor GitLab Runner'ile<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>GitLab 11.11-s lisasime GitLab Runnerisse uue t\u00e4itja, et Docker-konteinereid saaks kasutada Windowsis. Varem tuli Docker-konteinerite orkestreerimiseks Windowsis kasutada k\u00e4sureast, n\u00fc\u00fcd saab Docker-konteinereid Windowsis kasutada otse, peaaegu nagu Linuxis. Praegu on Microsofti platvormide kasutajatele saadaval rohkem v\u00f5imalusi pipeline'ide orkestreerimiseks ja haldamiseks.<\/p>\n<p><\/p>\n<p>See v\u00e4rskendus sisaldab paranenud PowerShelli tuge GitLab CI\/CD-s ja uusi abikoode erinevat t\u00fc\u00fcpi Windowsi konteinerite jaoks. Teie omad Windowsi jooksjad v\u00f5ivad loomulikult toimida GitLab.com-is, kuid praegu ei kuulu nad avalike t\u00f6\u00f6riistade nimekirja.<\/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: mitu vastutavat isikut merge-p\u00e4ringutele ja t\u00e4iustused konteineritele\" 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\">Dekodeerimise iseseisev vahem\u00e4lu konteinerite registris<\/h3>\n<p><\/p>\n<p><em>PREMIUM, ULTIMATE<\/em><\/p>\n<p><\/p>\n<p>Meeskonnad kasutavad sageli konteinerite pipeline'ides ja iseseisev vahem\u00e4lu sageli kasutatavatele piltidele ja pakettidele upstream'is on suurep\u00e4rane viis pipeline'ide kiirusel t\u00f5hustada. Koos kohaliku koopia vajalikest kihtidest, mis on saadaval uue vahem\u00e4lu kaudu, saab laialdaselt kasutatavates piltides teie keskkonnas efektiivsemalt t\u00f6\u00f6tada.<\/p>\n<p><\/p>\n<p>Praegu on konteinerite vahem\u00e4lu saadaval ainult enda hallatavates instantsides veebiserveris <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.gitlab.com\/omnibus\/settings\/puma.html\">Puma (eksperimentaalses re\u017eiimis)<\/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: mitu vastutavat isikut merge-p\u00e4ringutele ja t\u00e4iustused konteineritele\" 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\">M\u00f5ned vastutavad mergitamise p\u00e4ringute eest<\/h3>\n<p><\/p>\n<p><em>STARTER, PREMIUM, ULTIMATE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>Sageli t\u00f6\u00f6tavad mitu inimest funktsiooni kallal \u00fchises haru ja mergitamise p\u00e4ringus, n\u00e4iteks kui esiplaan ja tagak\u00fclje arendajad teevad tihedat koost\u00f6\u00f6d v\u00f5i kui arendajad t\u00f6\u00f6tavad paarides nagu \u00e4\u00e4rmuslik programmeerimine.<\/p>\n<p><\/p>\n<p>GitLab 11.11-s saab mergitamise p\u00e4ringutele m\u00e4\u00e4rata mitu inimest. Nagu mitme \u00fclesande vastutajaga, saab seda teha nimekirjade, filtrite, teadete ja API kaudu.<\/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: mitu vastutavat isikut merge-p\u00e4ringutele ja t\u00e4iustused konteineritele\" 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\">Kubernetes klastrite konfigureerimine instantsi tasemel<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE<\/em><\/p>\n<p><\/p>\n<p>Kuberneteses arenev turbe- ja ettevalmistusmudel v\u00f5imaldab n\u00fc\u00fcd teenindada suurt hulka kliente \u00fche \u00fcldise klastriga.<\/p>\n<p><\/p>\n<p>GitLab 11.11-s kasutajatel iseloomustatud instantside klastrite seadistamine on n\u00fc\u00fcd v\u00f5imalik, ja k\u00f5ik gruppide ja projektide instantsid kasutavad seda nende juurutamiseks. Selle integreerimise t\u00f5ttu luuakse GitLabis koos Kubernetesega automaatselt ressursside loomine konkreetselt projektide jaoks, et tagada t\u00e4iendav turvalisus.<\/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: mitu vastutavat isikut merge-p\u00e4ringutele ja t\u00e4iustused konteineritele\" 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\">Juhtimisteated Slackis ja Mattermostis<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>N\u00fc\u00fcd saate seadistada automaatseid teadet sisestamis\u00fcrituste kohta meeskonna kanalisse, t\u00e4nu integreerimisele vestlustega, <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.gitlab.com\/ee\/user\/project\/integrations\/slack.html\">Slack<\/a><\/noindex> ja <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.gitlab.com\/ee\/user\/project\/integrations\/mattermost.html\">Mattermost<\/a><\/noindex>, ja teie meeskond on kursis k\u00f5igi oluliste s\u00fcndmustega.<\/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: mitu vastutavat isikut merge-p\u00e4ringutele ja t\u00e4iustused konteineritele\" 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\">K\u00fclastaja juurdep\u00e4\u00e4s v\u00e4ljalasetele<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>N\u00fc\u00fcd saavad teie projektide k\u00fclastajad vaadata v\u00e4ljalaseid, mis on avaldatud v\u00e4ljalasete lehe peal. Nad saavad laadida alla avaldatud artefakte, kuid ei saa allalaadida l\u00e4htekoodi ega n\u00e4ha teavet repode kohta, nagu sildid v\u00f5i commit'id.<\/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: mitu vastutavat isikut merge-p\u00e4ringutele ja t\u00e4iustused konteineritele\" 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\">Teised t\u00e4iustused GitLab 11.11-s<\/h2>\n<p><\/p>\n<h3 id=\"serializovannye-grafy-kommitov-dlya-povysheniya-proizvoditelnosti\">Seerialiseeritud commit-graafid j\u00f5udluse parandamiseks<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>Paljude Git'i toimingute tegemiseks tuleb commit-graaf v\u00f5imalikult kiirusel k\u00f5ndida, n\u00e4iteks sulandumise baasi arvutamine v\u00f5i harude v\u00e4ljund, mis sisaldab commit'i. Mida rohkem commit'e on, seda aeglasemalt need toimingud edenevad, kuna k\u00f5ndimise ajal tuleb igast objektist lahti saada kettalt, et lugeda selle viiteid.<\/p>\n<p><\/p>\n<p>GitLab 11.11-s lisasime seerialiseeritud commit-graafide funktsiooni, mis on esitatud viimastes Git'i v\u00e4ljaannetes, et eelnevalt arvutada ja salvestada need andmed. N\u00fc\u00fcd k\u00e4ivad suurtes repodes k\u00f5ndimised palju kiiremini. Commit-graaf luuakse automaatselt j\u00e4rgmise pr\u00fcgihaldamise k\u00e4igus repodes.<\/p>\n<p><\/p>\n<p>Lugege, kuidas seerialiseeritud commit-graaf loodi, <noindex><a rel=\"nofollow\" href=\"https:\/\/devblogs.microsoft.com\/devops\/supercharging-the-git-commit-graph\/\">artiklite seeriast<\/a><\/noindex> \u00fche selle funktsiooni autori poolt.<\/p>\n<p><\/p>\n<h3 id=\"dopolnitelnye-minuty-ci-runner-teper-i-dlya-besplatnyh-planov\">Lisaminutid CI Runnerile: n\u00fc\u00fcd ka tasuta plaanide jaoks<\/h3>\n<p><\/p>\n<p><em>FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>Eelmisel kuul lisasime v\u00f5imaluse osta lisaminuteid CI Runnerile, kuid ainult tasuliste plaanide jaoks GitLab.com-is. Selles v\u00e4ljaandes saab minuteid osta ka tasuta plaanides.<\/p>\n<p><\/p>\n<h3 id=\"zagruzka-arhivov-direktoriy-v-repozitorii\">Kataloogide arhiivide \u00fcleslaadimine repositories<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>S\u00f5ltuvalt projekti t\u00fc\u00fcbist ja suurusest v\u00f5ib kogu projekti arhiivne \u00fcleslaadimine v\u00f5tta kaua aega ja ei pruugi alati vajalik olla, eriti suurte monorepositorite puhul. GitLab 11.11-s on v\u00f5imalik laadida \u00fcles praeguse katalooge sisu arhiiv, sealhulgas alamkatalooge, et valida vaid vajalikud kaustad.<\/p>\n<p><\/p>\n<p>Ait\u00e4h t\u00f6\u00f6 eest, <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: mitu vastutavat isikut merge-p\u00e4ringutele ja t\u00e4iustused konteineritele\" 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\">Pakkumise rakendamine lubab n\u00fc\u00fcd automaatselt arutada<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>Muutuste ettepanek lihtsustab koost\u00f6\u00f6d mergerequestide kallal: n\u00fc\u00fcd ei ole enam vaja kopeerida ja kleepida, et aktsepteerida ettepanekut. GitLab 11.11-s tegime selle protsessi veelgi lihtsamaks: n\u00fc\u00fcd arutelu automaatselt lahendatakse, kui ettepanek rakendatakse.<\/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=\"M\u00e4ngi videot\" 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\">Aja arvesti \u00fclesande tahvli k\u00fclgpaneelil<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>\u00dclesande tahvlite k\u00fclgpaneelid peaksid v\u00e4lja n\u00e4gema samamoodi tahvli ja \u00fclesande vaadetes. Seega on GitLabis n\u00fc\u00fcd \u00fclesande tahvli k\u00fclgpaneelil aega arvesti. Lihtsalt minge \u00fclesande tahvlile, kl\u00f5psake \u00fclesandel ja k\u00fclgpaneel avaneb koos aega arvestiga.<\/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: mitu vastutavat isikut merge-p\u00e4ringutele ja t\u00e4iustused konteineritele\" 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\">Teave juurutamise kohta Environments API-s<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>Olemas on v\u00f5imalus k\u00fcsida Environments API-lt teavet konkreetse keskkonna kohta, et teada, milline commit on keskkonnas praegu juurutatud. See lihtsustab automatiseerimist ja aruandlust GitLabi keskkonna kasutajatele.<\/p>\n<p><\/p>\n<h3 id=\"otricatelnye-sovpadeniya-peremennyh-dlya-pravil-payplayna\">Negatiivsed muutujate vastavused toru reeglite jaoks<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>N\u00fc\u00fcd on v\u00f5imalik kontrollida negatiivset v\u00f5rdsust v\u00f5i mustrite vastavust (<code>!=<\/code> ja <code>!~<\/code>) faili <code>.gitlab-ci.yml<\/code> keskkonna muutuja v\u00e4\u00e4rtuste kontrollimisel, seega on torude k\u00e4itumise kontroll muutunud paindlikumaks.<\/p>\n<p><\/p>\n<h3 id=\"zapusk-vseh-vypolnyaemyh-vruchnuyu-dzhobov-na-etape-odnim-schelchkom\">K\u00e4ivita k\u00f5ik k\u00e4sitsi k\u00e4ivitatavad t\u00f6\u00f6\u00fclesanded etapis \u00fche kl\u00f5psuga<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>GitLab 11.11-s saavad kasutajad, kellel on etappidel palju k\u00e4sitsi k\u00e4ivitatavaid t\u00f6\u00f6\u00fclesandeid, n\u00fc\u00fcd k\u00e4ivitada k\u00f5ik sellised t\u00f6\u00f6\u00fclesanded \u00fches etapis, klikkides nupule <strong>\u201eK\u00e4ivita k\u00f5ik\u201d<\/strong> ('Play all') etapi nime paremal k\u00fcljel torude vaates.<\/p>\n<p><\/p>\n<h3 id=\"sozdanie-fayla-napryamuyu-iz-peremennoy-sredy\">Faili loomine otse keskkonna muutuja kaudu<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>Keskkonna muutujaid kasutatakse sageli failide loomiseks, eriti saladuste jaoks, mis vajavad kaitset ja on saadaval ainult teatud keskkonna torudes. Selleks m\u00e4\u00e4rate muutuja sisuks faili sisu ja loote failis t\u00f6\u00f6\u00fclesandes, mille v\u00e4\u00e4rtus sisaldab. Uue muutuja abil <code>file<\/code> saate seda teha \u00fche sammuna isegi ilma <code>.gitlab-ci.yml-d muutmata.<\/code><\/p>\n<p><\/p>\n<h3 id=\"konechnaya-tochka-api-dlya-svedeniy-ob-uyazvimostyah\">API l\u00f5pp-punkt haavatavuse teabe jaoks<\/h3>\n<p><\/p>\n<p><em>ULTIMATE, GOLD<\/em><\/p>\n<p><\/p>\n<p>N\u00fc\u00fcd saate GitLab API-lt k\u00fcsida k\u00f5iki teie projekti tuvastatud haavatavusi. Selle API abil saab luua masinaliselt loetavaid haavatavuste loendeid, filtreerides t\u00fc\u00fcbi, usaldusv\u00e4\u00e4rsuse ja t\u00f5siduse j\u00e4rgi.<\/p>\n<p><\/p>\n<h3 id=\"vozmozhnost-polnogo-dinamicheskogo-skanirovaniya-dlya-dast\">T\u00e4ieliku d\u00fcnaamilise skannimise v\u00f5imalus DAST-ile<\/h3>\n<p><\/p>\n<p><em>ULTIMATE, GOLD<\/em><\/p>\n<p><\/p>\n<p>GitLab v\u00f5imaldab teil testida rakenduste turvalisust d\u00fcnaamiliselt (Dynamic Application Security Testing, DAST) CI-pipeline'i raames. Alates sellest v\u00e4ljaandest on v\u00f5imalik valida t\u00e4ielik d\u00fcnaamiline skaneerimine standardse passiivse skaneerimise asemel. T\u00e4ielik d\u00fcnaamiline skaneerimine kaitseb rohkemate haavatavuste eest.<\/p>\n<p><\/p>\n<h3 id=\"ustanovka-prometheus-v-klasterah-na-urovne-gruppy\">Prometheuse paigaldamine grupitasandi klastritesse<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>Selles v\u00e4ljaandes on GitLabis v\u00f5imalik kinnitada Kubernetes klaster kogu grupile. Oleme lisanud ka v\u00f5imaluse paigaldada \u00fcks Prometheuse eksemplar sellele klastrile, et lihtsustada k\u00f5igi projektide j\u00e4lgimist klastris.<\/p>\n<p><\/p>\n<h3 id=\"svedeniya-ob-ignorirovanii-uyazvimostey-na-paneli-bezopasnosti\">Teave haavatavuste ignoreerimise kohta turvapaneelil<\/h3>\n<p><\/p>\n<p><em>ULTIMATE, GOLD<\/em><\/p>\n<p><\/p>\n<p>GitLabi turvapaneelidel saavad administraatorid vaadata ignoreeritud haavatavusi. T\u00f6\u00f6voo optimeerimiseks lisasime v\u00f5imaluse vaadata teavet ignoreerimise kohta otse turvapaneelil.<\/p>\n<p><\/p>\n<h3 id=\"sozdanie-polzovatelskih-diagramm-metrik-na-paneli-monitoringa\">Kohandatud meetri diagrammide loomine m\u00f5\u00f5dikupaneelil<\/h3>\n<p><\/p>\n<p><em>PREMIUM, ULTIMATE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>Looge uusi diagramme kohandatud j\u00f5udlusmeetritega otse m\u00f5\u00f5dikupaneeli t\u00f6\u00f6riistaribal. N\u00fc\u00fcd saavad kasutajad luua, v\u00e4rskendada ja kustutada m\u00f5\u00f5dikuvisualiseeringuid m\u00f5\u00f5dikupaneelil, vajutades nuppu <strong>\u00abAdd Metric\u00bb<\/strong> (\u00abLisa m\u00f5\u00f5de\u00bb) paremas \u00fclanurgas m\u00f5\u00f5dikupaneeli t\u00f6\u00f6riistaribal.<\/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: mitu vastutavat isikut merge-p\u00e4ringutele ja t\u00e4iustused konteineritele\" 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\">Teavitustest avanevad \u00fclesanded n\u00fc\u00fcd GitLab Alert Boti nimel<\/h3>\n<p><\/p>\n<p><em>PREMIUM, ULTIMATE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>N\u00fc\u00fcd on \u00fclesannete autor, mis avatakse teavitustest, GitLab Alert Bot, et n\u00e4eksite kohe, et \u00fclesanne on automaatselt loodud olulise teavituse p\u00f5hjal.<\/p>\n<p><\/p>\n<h3 id=\"avtosohranenie-opisaniy-epikov-v-lokalnoe-hranilische\">Epikute kirjelduste automaatne salvestamine kohalikku salvestusse<\/h3>\n<p><\/p>\n<p><em>ULTIMATE, GOLD<\/em><\/p>\n<p><\/p>\n<p>Epikute kirjeldusi ei salvestatud kohalikku salvestusse, seega kadusid muudatused, kui te ei salvestanud neid otseselt, kui muutsid epiku kirjeldust. GitLab 11.11-s on v\u00f5imalik salvestada epikute kirjeldusi kohalikku salvestusse. See t\u00e4hendab, et n\u00fc\u00fcd saate h\u00f5lpsasti naasta epiku kirjelduste muutmise juurde, kui ilmnes viga, kui teid segati v\u00f5i kui te kogemata brauserist v\u00e4lja logisite.<\/p>\n<p><\/p>\n<h3 id=\"podderzhka-otzerkalivaniya-na-gitlab-dlya-git-lfs\">Git LFS-i peegelduse tugi GitLabis<\/h3>\n<p><\/p>\n<p><em>STARTER, PREMIUM, ULTIMATE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>Peegelduse abil saab Git reposte kopeerida \u00fchest kohast teise. See lihtsustab GitLabi serveris asuva reposte peegeldamise s\u00e4ilitamist, mis asub kuskil mujal. N\u00fc\u00fcd toetab GitLab peegeldamist Git LFS reposte jaoks, mist\u00f5ttu on see funktsioon kergesti k\u00e4ttesaadav ka suurte failidega reposte puhul, n\u00e4iteks m\u00e4ngude tekstuuride v\u00f5i teaduslike andmete korral.<\/p>\n<p><\/p>\n<h3 id=\"prava-na-chtenie-i-zapis-v-repozitorii-dlya-personalnyh-tokenov-dostupa\">Juurdep\u00e4\u00e4su\u00f5igused lugemiseks ja kirjutamiseks reposte jaoks isiklike juurdep\u00e4\u00e4sutokenite kaudu<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>Paljudel isiklike juurdep\u00e4\u00e4sutokenitel on muudatus\u00f5igused tasemel <code>api<\/code>, kuid API-le t\u00e4ielik juurdep\u00e4\u00e4s v\u00f5ib anda m\u00f5nele kasutajale v\u00f5i organisatsioonile liiga palju \u00f5igusi.<\/p>\n<p><\/p>\n<p>Ait\u00e4h kogukonna panuse eest saavad n\u00fc\u00fcd isiklikud juurdep\u00e4\u00e4sutokenid olla ainult lugemis- ja kirjutamis\u00f5igusega projekti reposte suhtes, mitte s\u00fcgavam juurdep\u00e4\u00e4s API tasemel nii delikaatsetele aladele nagu GitLabi konfiguratsioon ja liikmed.<\/p>\n<p><\/p>\n<p>Ait\u00e4h, 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\">Baastoetuse lisamine r\u00fchmade GraphQL p\u00e4ringutele<\/h3>\n<p><\/p>\n<p><em>FREE, BRONZE, SILVER, GOLD, CORE, STARTER, PREMIUM, ULTIMATE<\/em><\/p>\n<p><\/p>\n<p>GraphQL API kaudu saavad kasutajad t\u00e4pselt m\u00e4\u00e4rata, milliseid andmeid nad vajavad, ja saada k\u00f5ik vajalikud andmed vaid m\u00f5ne p\u00e4ringuga. Alates k\u00e4esolevast versioonist toetab GitLab r\u00fchma p\u00f5hiteabe lisamist GraphQL API-sse.<\/p>\n<p><\/p>\n<h3 id=\"vhod-s-uchetnymi-dannymi-salesforce\">Sisenemine Salesforce'i kasutajateandmetega<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>GitLab armastab Salesforce'i arendajaid ja selle kogukonna toetamiseks lubame kasutajatel sisse logida GitLabi Salesforce.com kasutajateandmete abil. Praegu saab instantsidest seadistada GitLabi rakenduseks, mis on \u00fchendatud Salesforce'iga, et kasutada Salesforce.comi GitLabi sisenemiseks \u00fche puudutusega.<\/p>\n<p><\/p>\n<h3 id=\"saml-sso-teper-obyazatelen-dlya-veb-dostupa\">SAML SSO on n\u00fc\u00fcd veebip\u00e4\u00e4su jaoks kohustuslik<\/h3>\n<p><\/p>\n<p><em>PREMIUM, ULTIMATE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>Meie <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ee\/issues\/5291\">laiendades \u00fchtse sisenemise (SSO) n\u00f5uet<\/a><\/noindex> gruppide tasemel, mis viidi sisse versioonis 11.8, rangete grupi ja projekti ressursside kontrollimisega, et kasutajad saaksid juurde p\u00e4\u00e4seda ainult SAML-iga sisse logides. See on lisakontrolli tase organisatsioonidele, kes hindavad turvalisust ja kasutavad GitLab.com-i l\u00e4bi SAML SSO. N\u00fc\u00fcd saate muuta SSO kohustuslikuks n\u00f5udeks, teades, et teie grupis kasutavad k\u00f5ik kasutajad SSO-d.<\/p>\n<p><\/p>\n<h3 id=\"filtraciya-po-nedavno-sozdannym-ili-izmenennym-dannym-dlya-api-epikov\">Filtreerimine hiljuti loodud v\u00f5i muudetud andmete j\u00e4rgi epikute API-s<\/h3>\n<p><\/p>\n<p><em>ULTIMATE, GOLD<\/em><\/p>\n<p><\/p>\n<p>Varem oli GitLabis epikute API kaudu hiljuti loodud v\u00f5i muudetud andmete p\u00e4rimine keeruline. Versioonis 11.11 lisasime t\u00e4iendavad filtrid <code>created_after<\/code>, <code>created_before<\/code>, <code>uuendatud p\u00e4rast<\/code> ja <code>uuendatud enne<\/code>, et tagada koosk\u00f5la \u00fclesannete API-ga ja kiiresti leida muudetud v\u00f5i hiljuti loodud epikud.<\/p>\n<p><\/p>\n<h3 id=\"biometricheskaya-autentifikaciya-s-ultraauth\">Biomeetriline autentimine UltraAuthiga<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>Ettev\u00f5te <noindex>UltraAuth<\/noindex> spetsialiseerub paroolivabale biomeetrilisele autentimisele. N\u00fc\u00fcd toetame seda autentimismeetodit GitLabis!<\/p>\n<p><\/p>\n<p>Ait\u00e4h, 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>T\u00e4na vabastasime GitLab Runneri 11.11! GitLab Runner on avatud allikaga projekt, mida kasutatakse CI\/CD \u00fclesannete k\u00e4ivitamiseks ja tulemuste tagasi saatmiseks GitLabi.<\/p>\n<p><\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/merge_requests\/1298\"><code>Parandatud probleem, kus git lfs<\/code> ei saanud alammoduli objekte.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/merge_requests\/1292\">Suurte j\u00e4lgimisfailide t\u00f6\u00f6tlemine on optimeeritud.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/merge_requests\/1321\">Funktsioonide parameetreid saab seadistada faili config.toml kaudu.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/merge_requests\/1319\"><code>Funktsioonide parameetreid saab kasutada ka kausta \/builds seadistamiseks.<\/code>.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/merge_requests\/1243\">Docker Executor jaoks on lisatud PowerShelli tugi.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/merge_requests\/1269\">Windows Dockeri mahtude konfiguratsiooni tugi.<\/a><\/noindex><\/li>\n<\/ul>\n<p><\/p>\n<h3 id=\"uluchsheniya-omnibus\">Omnibus'i parandused<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE<\/em><\/p>\n<p><\/p>\n<p>Oleme teinud j\u00e4rgmised t\u00e4iustused Omnibusis GitLab 11.11:<\/p>\n<p><\/p>\n<ul>\n<li>GitLab 11.11 sisaldab <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\/\">Slacki avatud koodiga alternatiivi<\/a><\/noindex>, mille uus v\u00e4ljalase sisaldab interaktiivseid efemeerseid s\u00f5numeid ja palju muud. See versioon sisaldab <noindex><a rel=\"nofollow\" href=\"https:\/\/mattermost.com\/security-updates\/\">turvauuendusi<\/a><\/noindex>, ja soovitame uuendust teha.<\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/omnibus-gitlab\/merge_requests\/3241\"><code>Grafana on uuendatud versioonile 1.1.0<\/code>, et j\u00e4rele j\u00f5uda viimaste Omnibusi armatuurlaudadega.<\/a><\/noindex>.<\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/omnibus-gitlab\/merge_requests\/3142\">PostreSQL 10 pakett sisaldab n\u00fc\u00fcd Omnibusit.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/omnibus-gitlab\/merge_requests\/3249\/diffs\"><code>Sentry DSN-i saab n\u00fc\u00fcd edastada gitlab.yml faili<\/code>.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/omnibus-gitlab\/merge_requests\/3082\"><code>RubyGems on uuendatud versioonile 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>liblzma uuendamine<\/code> kuni <code>5.2.4<\/code> jot <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>libtool uuendamine<\/code> kuni <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 k\u00e4ivitub pg-upgrade k\u00e4su j\u00e4rgi<\/code>.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/omnibus-gitlab\/merge_requests\/3182\">Prometheuse komponentide uuendamine viimastele versioonidele.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/omnibus-gitlab\/merge_requests\/3220\"><code>git on uuendatud versioonile 2.21.0<\/code>.<\/a><\/noindex><\/li>\n<\/ul>\n<p><\/p>\n<h3 id=\"uluchshenie-shem\">Schema t\u00e4iustamine<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE<\/em><\/p>\n<p><\/p>\n<p>Oleme teinud j\u00e4rgmised t\u00e4iustused Helm-graafikutes GitLab 11.11:<\/p>\n<p><\/p>\n<ul>\n<li>GitLab 11.11-s on v\u00f5imalik <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/charts\/gitlab\/issues\/705\">liita mahutavus tmp\/work kataloogis<\/a><\/noindex>.<\/li>\n<li>Administraatoritele on saadaval <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/charts\/gitlab\/merge_requests\/776\">t\u00e4iendavad seadistamisvalikud<\/a><\/noindex>, sealhulgas <code>memoryKiller<\/code>, <code>maxRss<\/code>, <code>graceTime<\/code> ja <code>shutdownWait<\/code>.<\/li>\n<li>Helm-graafikuid n\u00fc\u00fcd <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/charts\/gitlab\/issues\/1132\">katsetatakse pidevalt<\/a><\/noindex> 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\">T\u00f5hususe parandused<\/h3>\n<p><\/p>\n<p><em>CORE, STARTER, PREMIUM, ULTIMATE, FREE, BRONZE, SILVER, GOLD<\/em><\/p>\n<p><\/p>\n<p>J\u00e4tkame GitLabi j\u00f5udluse parandamist iga v\u00e4ljalaskega GitLabi mis tahes suurusega eksemplaridele. M\u00f5ned t\u00e4iustused GitLab 11.11-s:<\/p>\n<p><\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ce\/merge_requests\/27866\">Kasutajate automaatse t\u00e4itmise kiirus, kui vastustes on palju avataride teid.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ce\/merge_requests\/27825\">Sidekiqi koormuse v\u00e4henemine todo-de eemaldamisel.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ee\/merge_requests\/11575\">GraphQL resolvija keerukuse arvutamine elementide alusel.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ce\/merge_requests\/27817\">Globaalsete otsingutulemuste j\u00f5udluse parandamine.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ce\/merge_requests\/27413\">T\u00e4iskohaga diff-faili juurutamisel j\u00f5udluse parandamine.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ce\/merge_requests\/27625\">Kinnitatud blob-objektide p\u00e4ring ainult \u00fches paketis.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ce\/merge_requests\/22801\">Wiki-lehek\u00fclgede loendi v\u00e4ljastamine ilma sisu laadimata.<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ce\/merge_requests\/24038\">Ajutiste linkide loomise keeld \u00fche projekti harude v\u00f5rdlemiseks.<\/a><\/noindex><\/li>\n<\/ul>\n<p><\/p>\n<h2 id=\"ustarevshie-fichi\">Vananevad funktsioonid<\/h2>\n<p><\/p>\n<h3 id=\"gitlab-geo-obespechit-heshirovannoe-hranenie-v-gitlab-120\">GitLab Geo tagab hashitud salvestamise GitLab 12.0-s<\/h3>\n<p><\/p>\n<p>GitLab Geo on vajalik <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.gitlab.com\/ee\/administration\/repository_storage_types.html#hashed-storage\">hashitud salvestamine<\/a><\/noindex> teisej\u00e4rguliste s\u00f5lmede konkurentsi leevendamiseks. See on registreeritud <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>GitLabis <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/groups\/gitlab-org\/-\/milestones\/20\">11.5<\/a><\/noindex> oleme selle n\u00f5ude lisanud Geo dokumentatsioonisse: <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>GitLabis <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> kontrollib, kas hashitud salvestamine on lubatud ja kas k\u00f5ik projektid kantakse \u00fcle. Vaata. <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ee\/issues\/8289\">gitlab-ee#8289<\/a><\/noindex>. Kui kasutate Geo-d, palun k\u00e4ivitage see kontroll ja migreerige v\u00f5imalikult kiiresti.<\/p>\n<p><\/p>\n<p>GitLabis <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/groups\/gitlab-org\/-\/milestones\/23\">11.8<\/a><\/noindex> p\u00fcsivalt v\u00e4lja l\u00fclitatav hoiatuse kuvamine lehel <strong>Admin Ala \u203a Geo \u203a S\u00f5lmed<\/strong>, kui \u00fclalmainitud kontrollid ei ole lubatud. <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>GitLabis <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/groups\/gitlab-org\/-\/milestones\/33\">12.0<\/a><\/noindex> Geo kasutab hashitud salvestamise n\u00f5udeid. Vaata. <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>Kustutamise kuup\u00e4ev: <strong>22. juuni 2019.<\/strong><\/p>\n<p><\/p>\n<h3 id=\"gitlab-geo-obespechit-ispolzovanie-pg-fdw-v-gitlab-120\">GitLab Geo kindlustab PG FDW kasutamise GitLab 12.0-s<\/h3>\n<p><\/p>\n<p>See on vajalik Geo Log Cursor'i jaoks, kuna see parandab oluliselt teatud s\u00fcnkroniseerimise toimingute j\u00f5udlust. Samuti paraneb Geo s\u00f5lmede olekute p\u00e4ringute j\u00f5udlus. Eelmised p\u00e4ringud olid suurtes projektides liiga madala j\u00f5udlusega. Vaata, kuidas seda seadistada <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.gitlab.com\/ee\/administration\/geo\/replication\/database.html\">Geo andmebaasi replikatsioonis<\/a><\/noindex>. GitLabis <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/groups\/gitlab-org\/-\/milestones\/33\">12.0<\/a><\/noindex> Geo n\u00f5uab PG FDW-d. Vaata. <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>Kustutamise kuup\u00e4ev: <strong>22. juuni 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\">Sentry konfigureerimise seaded veateadete ja logimise jaoks eemaldatakse kasutajaliidesest GitLab 12.0-s<\/h3>\n<p><\/p>\n<p>Need seaded eemaldatakse kasutajaliidesest GitLab 12.0-s ja need on saadaval failis <code>gitlab.yml<\/code>. Lisaks saate m\u00e4\u00e4rata Sentry keskkonna, et eristada mitmeid juurutusi. N\u00e4iteks arendus, etapp ja tootmine. Vaata. <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>Kustutamise kuup\u00e4ev: <strong>22. juuni 2019.<\/strong><\/p>\n<p><\/p>\n<h3 id=\"ogranichenie-maksimalnogo-kolichestva-payplaynov-sozdavaemyh-odnoy-otpravkoy\">Maksimaalsete pipeline'ide arvu piiramine, mida v\u00f5ib \u00fche pushiga luua<\/h3>\n<p><\/p>\n<p>Varem l\u00f5i GitLab pipeline'e <code>HEAD<\/code> iga l\u00f5igus push'is. See on mugav arendajatele, kes saadavad mitu muudatust korraga (n\u00e4iteks funktsiooniharusse ja <code>develop<\/code>).<\/p>\n<p><\/p>\n<p>Kuid suurte hoidlate pushimisel, kus on palju aktiivseid harusid, pole vaja iga haru jaoks pipeline'i luua. Alates GitLab 11.10 loome <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ce\/merge_requests\/27205\">kuni 4 pipeline'i<\/a><\/noindex> push'iga.<\/p>\n<p><\/p>\n<p>Kustutamise kuup\u00e4ev: <strong>22. mai 2019.<\/strong><\/p>\n<p><\/p>\n<h3 id=\"ustarevshie-puti-legacy-koda-gitlab-runner\">GitLab Runneri vananenud legacy koodide teed<\/h3>\n<p><\/p>\n<p>Alates GitLab 11.9 kasutab GitLab Runner <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/merge_requests\/1203\">uut meetodit <\/a><\/noindex> hoidla kloonimiseks\/kutsumiseks. Praegu kasutab GitLab Runner vana meetodit, kui uut ei toetata. Rohkem teavet leiate <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/issues\/4069\">sellest \u00fchisest<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>GitLab 11.0-s muutsime GitLab Runneri metrikate serveri konfiguratsiooni v\u00e4limust. <code>metrics_server<\/code>kustutatakse <code>listen_address<\/code> GitLab 12.0-s. Rohkem teavet leiate <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/issues\/4072\">sellest \u00fchisest<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>GitLab Runner hakkas 11.3 versioonis toetama <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/merge_requests\/968\">mitmeid vahem\u00e4lu pakkujaid<\/a><\/noindex>; mis t\u00f5i kaasa uued seadistused <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.gitlab.com\/runner\/configuration\/advanced-configuration.html#the-runnerscaches3-section\">konkreetse S3 konfiguratsiooni jaoks<\/a><\/noindex>. Failis <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.gitlab.com\/runner\/configuration\/advanced-configuration.html#the-runnerscache-section\">dokumentatsioon<\/a><\/noindex> Need teed ei ole enam saadaval GitLab 12.0-s. Kasutajana ei ole teil vaja midagi muuta, lihtsalt veenduge, et GitLab'i eksemplar t\u00f6\u00f6taks versiooniga 11.9+ enne \u00fcleminekut GitLab Runner 12.0-le. <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/issues\/4070\">sellest \u00fchisest<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>Need to know that these paths will be unavailable in GitLab 12.0. As a user, you do not need to change anything; just ensure that your GitLab instance is running version 11.9+ when upgrading to GitLab Runner 12.0.<\/p>\n<p><\/p>\n<p>Kustutamise kuup\u00e4ev: <strong>22. juuni 2019.<\/strong><\/p>\n<p><\/p>\n<h3 id=\"ustarevshiy-parametr-dlya-fichi-tochki-vhoda-dlya-gitlab-runner\">Deprecated parameter for the entry point feature for GitLab Runner<\/h3>\n<p><\/p>\n<p>In 11.4, GitLab Runner introduced a feature parameter <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> to resolve issues such as <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/issues\/2338\">#2338<\/a><\/noindex> ja <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/issues\/3536\">#3536<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>In GitLab 12.0, we will switch to the correct behavior as if the feature parameter were disabled. For more details, see <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/issues\/4073\">sellest \u00fchisest<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>Kustutamise kuup\u00e4ev: <strong>22. juuni 2019.<\/strong><\/p>\n<p><\/p>\n<h3 id=\"ustarevshaya-podderzhka-distributiva-linux-dostigshego-eol-dlya-gitlab-runner\">Deprecated support for Linux distributions that reached EOL for GitLab Runner<\/h3>\n<p><\/p>\n<p>Some Linux distributions where GitLab Runner can be installed have reached their end of life.<\/p>\n<p><\/p>\n<p>In GitLab 12.0, GitLab Runner will no longer distribute packages to such Linux distributions. A complete list of distributions that are no longer supported can be found in our <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.gitlab.com\/runner\/install\/linux-repository.html\">dokumentatsioon<\/a><\/noindex>. Ait\u00e4h, Javier Ardo (<noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/jjardon\">Javier Jard\u00f3n<\/a><\/noindex>), sinu <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/merge_requests\/1130\">\u2014 funktsioon, mida kogukond on kaua oodanud GitLab'is. See on t\u00f5eliselt oluline panus keeruliste muudatustega, mis n\u00f5udsid pidevat koost\u00f6\u00f6d GitLab'i meeskonna liikmetega ja h\u00f5lmasid mitmeid projekti valdkondi, nagu UX, frontend ja backend.<\/a><\/noindex>!<\/p>\n<p><\/p>\n<p>Kustutamise kuup\u00e4ev: <strong>22. juuni 2019.<\/strong><\/p>\n<p><\/p>\n<h3 id=\"udalenie-staryh-komand-gitlab-runner-helper\">Removal of old GitLab Runner Helper commands<\/h3>\n<p><\/p>\n<p>Kuna lisame toe <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/groups\/gitlab-org\/-\/epics\/535\">Windows Docker executor<\/a><\/noindex> some old commands used for <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>In GitLab 12.0, GitLab Runner will run using new commands. This only affects users who <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.gitlab.com\/runner\/configuration\/advanced-configuration.html#overriding-the-helper-image\">override the helper image<\/a><\/noindex>. For more details, see <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/issues\/4013\">sellest \u00fchisest<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>Kustutamise kuup\u00e4ev: <strong>22. juuni 2019.<\/strong><\/p>\n<p><\/p>\n<h3 id=\"udalenie-legacy-mehanizma-git-clean-iz-gitlab-runner\">Removal of the legacy git clean mechanism from GitLab Runner<\/h3>\n<p><\/p>\n<p>GitLab Runner 11.10-s <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/merge_requests\/1281\">oleme andnud v\u00f5imaluse.<\/a><\/noindex> configure how the Runner performs the command <code>git clean<\/code>Lisaks eemaldab uus puhastamisstrateegia kasutamise <code>git reset<\/code> and places the command <code>git clean<\/code> after the unload step.<\/p>\n<p><\/p>\n<p>Since this change in behavior might affect some users, we have prepared a parameter <code>FF_USE_LEGACY_GIT_CLEAN_STRATEGY<\/code>. Setting it to <code>true<\/code>, it will restore the legacy cleaning strategy. More details on using feature parameters in GitLab Runner can be found <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.gitlab.com\/runner\/configuration\/feature-flags.html\">in the documentation<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>GitLab Runner 12.0-s eemaldame legacy-puhastamisstrateegise toe ja v\u00f5imaluse taastada seda funktsiooni parameetri kaudu. Vaata <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/issues\/4175\">sellest \u00fchisest<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>Kustutamise kuup\u00e4ev: <strong>22. juuni 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\">Grupi projektide mallid<\/a><\/noindex> on saadaval ainult Silver\/Premium plaanide jaoks<\/h3>\n<p><\/p>\n<p>Kui esitlesime grupitaseme projektide malle v\u00e4ljaandes 11.6, tegime selle funktsiooni Premium\/Silver jaoks valejuhuslikult k\u00f5igile plaanidele kergesti k\u00e4ttesaadavaks.<\/p>\n<p><\/p>\n<p>Meie <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ee\/issues\/10926\">parandame selle vea<\/a><\/noindex> v\u00e4ljaandes 11.11 ja anname veel 3 kuud k\u00f5igile kasutajatele ja instantsidele, mis on allpool Silver\/Premium taset.<\/p>\n<p><\/p>\n<p>Alates 22. augustist 2019 on grupi projektide mallid saadaval ainult Silver\/Premium ja k\u00f5rgemate plaanide jaoks, nagu on kirjeldatud dokumentatsioonis.<\/p>\n<p><\/p>\n<p>Kustutamise kuup\u00e4ev: <strong>22. august 2019.<\/strong><\/p>\n<p><\/p>\n<h3 id=\"prekraschena-podderzhka-paketnyh-zadaniy-windows\">Windowsi skriptide toe l\u00f5petamine<\/h3>\n<p><\/p>\n<p>GitLab 13.0-s (22. juuni 2020) plaanime l\u00f5petada Windowsi k\u00e4surea skriptide toe GitLab Runner'is (nt, <code>cmd.exe<\/code>) laiendatud Windows PowerShelli toe nimel. Lisainfot leiate <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/issues\/4163\">sellest \u00fchisest<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>N\u00fc\u00fcd vastab meie ettev\u00f5tte DevOps visioon Microsofti positsioonile, et PowerShell on parim lahendus ettev\u00f5tte rakenduste automatiseerimiseks Windowsi keskkondades. Kui soovite j\u00e4tkata kasutamist <code>cmd.exe<\/code>, neid k\u00e4sud saab PowerShellist k\u00e4ivitada, kuid me ei toeta Windowsi partii\u00fclesandeid otseselt, kuna mitmed vastuolud toovad kaasa k\u00f5rged hooldus- ja arenduskulud.<\/p>\n<p><\/p>\n<p>Kustutamise kuup\u00e4ev: <strong>22. september 2019<\/strong><\/p>\n<p><\/p>\n<h3 id=\"trebuetsya-git-2210-ili-vyshe\">N\u00f5utav on Git 2.21.0 v\u00f5i uuem<\/h3>\n<p><\/p>\n<p>Alates GitLab 11.11 on k\u00e4ivitamiseks vajalik Git 2.21.0. <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/omnibus-gitlab\/merge_requests\/3220\">Omnibus GitLab on juba varustatud Git 2.21.0 versiooniga<\/a><\/noindex>, kuid varasemate Git versioonidega kasutajatel tuleb uuendada.<\/p>\n<p><\/p>\n<p>Kustutamise kuup\u00e4ev: <strong>22. mai 2019.<\/strong><\/p>\n<p><\/p>\n<h3 id=\"ustarevshiy-shablon-servisa-kubernetes\">Aegunud Kubernetes teenuse mall<\/h3>\n<p><\/p>\n<p>GitLab 12.0-s plaanime loobuda Kubernetes teenuse mallist <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ce\/issues\/39840\">instantsi tasemel<\/a><\/noindex> instantsi tasemel klastrikonfiguratsiooni kasuks, mis on esitatud GitLab 11.11-s.<\/p>\n<p><\/p>\n<p>K\u00f5ik iseteenindavad instantsid, kus kasutatakse teenuse malli, kantakse uuendamisel GitLab 12.0-s instantsi tasemel klastrisse.<\/p>\n<p><\/p>\n<p>Kustutamise kuup\u00e4ev: <strong>22. juuni 2019.<\/strong><\/p>\n<p><\/p>\n<h3 id=\"otkaz-ot-sopostavleniya-po-yarlyku-app-na-panelyah-deploya-kubernetes\">Sildiga s\u00fcnkroonimise l\u00f5petamine <code>app<\/code> Kubernetes\u2019i juurutamise paneelides<\/h3>\n<p><\/p>\n<p>GitLab 12.0-s plaanime loobuda app sildi s\u00fcnkroonimisest Kubernetes\u2019i juurutamise valijas. GitLab 11.10-s tutvustasime <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-ee\/issues\/9221\">uut s\u00fcnkroonimismehhanismi<\/a><\/noindex>, mis otsib vasteid <code>app.example.com\/app<\/code> ja <code>app.example.com\/env<\/code>, et kuvada juurutamisi paneelil.<\/p>\n<p><\/p>\n<p>Et need juurutamised kuvatakse juurutamise paneelides, tuleb lihtsalt saata uus juurutamine ja GitLab rakendab uusi silte.<\/p>\n<p><\/p>\n<p>Kustutamise kuup\u00e4ev: <strong>22. juuni 2019.<\/strong><\/p>\n<p><\/p>\n<h3 id=\"pakety-gitlab-120-budut-podpisyvatsya-rasshirennoy-podpisyu\">GitLab 12.0 paketid allkirjastatakse laiendatud allkirjaga<\/h3>\n<p><\/p>\n<p>2. mai 2019, GitLab <noindex><a rel=\"nofollow\" href=\"https:\/\/gitlab.com\/gitlab-org\/omnibus-gitlab\/issues\/3897\">pikendas allkirjastamise v\u00f5tmete kehtivust<\/a><\/noindex> Omnibus GitLab paketid alates 01.08.2019 kuni 01.07.2020. Kui kontrollite paketi allkirju ja soovite uuendada v\u00f5tmeid, j\u00e4rgige lihtsalt veel kord juhiseid <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.gitlab.com\/omnibus\/update\/package_signatures.html\">Omnibus paketite allkirjastamise dokumentatsioonist<\/a><\/noindex>.<\/p>\n<p><\/p>\n<p>Kustutamise kuup\u00e4ev: <strong>22. juuni 2019.<\/strong><\/p>\n<p><\/p>\n<h3 id=\"zhurnal-izmeneniy\">Change Log<\/h3>\n<p><\/p>\n<p>Find all these changes in the change log:<\/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'i<\/a><\/noindex><\/li>\n<\/ul>\n<p><\/p>\n<h3 id=\"ustanovka\">Paigaldamine<\/h3>\n<p><\/p>\n<p>If you're setting up a new GitLab installation, visit <noindex><a rel=\"nofollow\" href=\"https:\/\/about.gitlab.com\/install\/\">the GitLab download page<\/a><\/noindex>.<\/p>\n<p><\/p>\n<h3 id=\"obnovlenie\">Upgrade<\/h3>\n<p><\/p>\n<p>\u2192 Vaadake <noindex><a rel=\"nofollow\" href=\"https:\/\/about.gitlab.com\/update\/\">updates page<\/a><\/noindex><\/p>\n<p>Allikas: <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.1.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\/et\/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.1.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"et_EE\" \/>\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\/et\/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: mitmed vastutavad \u00fchinemisp\u00e4ringud ja t\u00e4iustused konteineritele | ProHoster","description":".","canonical_url":"https:\/\/prohoster.info\/et\/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":"et_EE","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\/et\/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\/et\/wp-json\/wp\/v2\/posts\/34683","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/comments?post=34683"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/34683\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media\/26134"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media?parent=34683"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/categories?post=34683"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/tags?post=34683"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}