{"id":76769,"date":"2020-04-04T13:42:27","date_gmt":"2020-04-04T11:42:27","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/content-based-tagging-v-sborshhike-werf-zachem-i-kak-eto-rabotaet"},"modified":"2020-04-04T13:42:27","modified_gmt":"2020-04-04T11:42:27","slug":"content-based-tagging-v-sborshhike-werf-zachem-i-kak-eto-rabotaet","status":"publish","type":"post","link":"https:\/\/prohoster.info\/hu\/blog\/administrirovanie\/content-based-tagging-v-sborshhike-werf-zachem-i-kak-eto-rabotaet","title":{"rendered":"Tartalom alap\u00fa c\u00edmk\u00e9z\u00e9s a werf build rendszer\u00e9ben: mi\u00e9rt \u00e9s hogyan m\u0171k\u00f6dik ez?","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Tartalom alap\u00fa c\u00edmk\u00e9z\u00e9s a werf build rendszer\u00e9ben: mi\u00e9rt \u00e9s hogyan m\u0171k\u00f6dik ez?\" src=\"\/wp-content\/uploads\/2020\/04\/494346bbee96cc2b6c838491ba1c67fb.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/werf.io\/\">werf<\/a><\/noindex> \u2014 a ny\u00edlt forr\u00e1sk\u00f3d\u00fa GitOps CLI eszk\u00f6z\u00fcnk az alkalmaz\u00e1sok Kubernetesbe t\u00f6rt\u00e9n\u0151 \u00f6ssze\u00e1ll\u00edt\u00e1s\u00e1hoz \u00e9s sz\u00e1ll\u00edt\u00e1s\u00e1hoz. Az <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/493170\/\">v1.1-es kiad\u00e1sban<\/a><\/noindex> bemutattunk egy \u00faj funkci\u00f3t a k\u00e9pk\u00e9sz\u00edt\u0151ben: k\u00e9pek c\u00edmk\u00e9z\u00e9se a tartalom vagy <i>tartalmi alap\u00fa c\u00edmk\u00e9z\u00e9s<\/i>. Eddig a werf c\u00edmk\u00e9z\u00e9si s\u00e9m\u00e1ja az volt, hogy a Docker k\u00e9peket a Git c\u00edmk\u00e9je, Git \u00e1ga vagy Git commitja alapj\u00e1n c\u00edmk\u00e9zt\u00fck. Ennek a h\u00e1rom s\u00e9m\u00e1nak azonban megvannak a h\u00e1tr\u00e1nyai, amelyeket a c\u00edmk\u00e9z\u00e9s \u00faj strat\u00e9gi\u00e1ja teljes m\u00e9rt\u00e9kben megold. R\u00e9szletek a k\u00f6vetkez\u0151 oldalakon.<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h2>Mikroszolg\u00e1ltat\u00e1scsomag kiad\u00e1sa egy Git t\u00e1rol\u00f3b\u00f3l<\/h2>\n<p>\nGyakori helyzet, amikor az alkalmaz\u00e1s t\u00f6bb\u00e9-kev\u00e9sb\u00e9 f\u00fcggetlen szolg\u00e1ltat\u00e1sokra van bontva. Ezeknek a szolg\u00e1ltat\u00e1soknak a kiad\u00e1sai f\u00fcggetlen\u00fcl t\u00f6rt\u00e9nhetnek: egyszerre egy vagy t\u00f6bb szolg\u00e1ltat\u00e1s is kiadhat\u00f3, m\u00edg a t\u00f6bbi szolg\u00e1ltat\u00e1snak v\u00e1ltoztat\u00e1s n\u00e9lk\u00fcl kell m\u0171k\u00f6dnie. K\u00f3d t\u00e1rol\u00e1sa \u00e9s projektkezel\u00e9s szempontj\u00e1b\u00f3l azonban k\u00e9nyelmesebb, ha ezek a szolg\u00e1ltat\u00e1sok egyetlen t\u00e1rol\u00f3ban tal\u00e1lhat\u00f3k.<\/p>\n<p>El\u0151fordulhat, hogy a szolg\u00e1ltat\u00e1sok val\u00f3ban f\u00fcggetlenek \u00e9s nem kapcsol\u00f3dnak egyetlen alkalmaz\u00e1shoz. Ilyen esetben k\u00fcl\u00f6n projektekben helyezkednek el, \u00e9s a kiad\u00e1sokat minden projektben k\u00fcl\u00f6n CI\/CD folyamatokon kereszt\u00fcl hajtj\u00e1k v\u00e9gre.<\/p>\n<p>A val\u00f3s\u00e1gban azonban a fejleszt\u0151k gyakran bontj\u00e1k le az egyes alkalmaz\u00e1sokat t\u00f6bb mikroszolg\u00e1ltat\u00e1sra, de mindegyikhez k\u00fcl\u00f6n t\u00e1rol\u00f3t \u00e9s projektet l\u00e9trehozni\u2026 \u2014 nyilv\u00e1nval\u00f3 overkill. Pontosan err\u0151l a helyzetr\u0151l lesz sz\u00f3: t\u00f6bb ilyen mikroszolg\u00e1ltat\u00e1s tal\u00e1lhat\u00f3 egyetlen projekt t\u00e1rol\u00f3j\u00e1ban, \u00e9s a kiad\u00e1sok egyetlen CI\/CD folyamaton kereszt\u00fcl t\u00f6rt\u00e9nnek.<\/p>\n<h3>C\u00edmk\u00e9z\u00e9s Git \u00e1gon \u00e9s Git c\u00edmk\u00e9n<\/h3>\n<p>\nTegy\u00fck fel, hogy a legelterjedtebb c\u00edmk\u00e9z\u00e9si strat\u00e9gi\u00e1t haszn\u00e1ljuk \u2014 <i>tag-or-branch<\/i>. A Git \u00e1gak eset\u00e9ben a k\u00e9peket az \u00e1gn\u00e9vvel c\u00edmk\u00e9zz\u00fck, egy \u00e1gon egyszerre csak egy publik\u00e1lt k\u00e9p l\u00e9tezhet az \u00e1gn\u00e9v alapj\u00e1n. A Git c\u00edmk\u00e9k eset\u00e9ben a k\u00e9peket a c\u00edmke nev\u00e9vel c\u00edmk\u00e9zz\u00fck.<\/p>\n<p>Amikor \u00faj Git c\u00edmk\u00e9t hozunk l\u00e9tre \u2014 p\u00e9ld\u00e1ul egy \u00faj verzi\u00f3 kiad\u00e1sakor \u2014 a projekt \u00f6sszes k\u00e9p\u00e9hez \u00faj Docker c\u00edmke k\u00e9sz\u00fcl a Docker Registry-ben:<\/p>\n<ul>\n<li> <code>myregistry.org\/myproject\/frontend:v1.1.10<\/code><\/li>\n<li> <code>myregistry.org\/myproject\/myservice1:v1.1.10<\/code><\/li>\n<li> <code>myregistry.org\/myproject\/myservice2:v1.1.10<\/code><\/li>\n<li> <code>myregistry.org\/myproject\/myservice3:v1.1.10<\/code><\/li>\n<li> <code>myregistry.org\/myproject\/myservice4:v1.1.10<\/code><\/li>\n<li> <code>myregistry.org\/myproject\/myservice5:v1.1.10<\/code><\/li>\n<li> <code>myregistry.org\/myproject\/database:v1.1.10<\/code><\/li>\n<\/ul>\n<p>\nEzek az \u00faj k\u00e9pek nevei Helm-sablonokon kereszt\u00fcl ker\u00fclnek be a Kubernetes konfigur\u00e1ci\u00f3ba. A telep\u00edt\u00e9s ind\u00edt\u00e1sakor <code>werf deploy<\/code> az \u00e9rintett mez\u0151 friss\u00edt\u00e9se megt\u00f6rt\u00e9nik <code>k\u00e9p<\/code> a Kubernetes er\u0151forr\u00e1sok manifesztjeiben \u00e9s az \u00e9rintett er\u0151forr\u00e1sok \u00fajraind\u00edt\u00e1sa a k\u00e9p nev\u00e9nek megv\u00e1ltoz\u00e1sa miatt.<\/p>\n<p><b>Probl\u00e9ma<\/b>: ha a kor\u00e1bbi kiad\u00e1s (Git-c\u00edmke) t\u00e9nylegesen nem v\u00e1ltozott meg a k\u00e9p tartalm\u00e1val, csak a Docker-c\u00edmk\u00e9je, akkor <i>t\u00falzott<\/i> az alkalmaz\u00e1s \u00fajraind\u00edt\u00e1sa \u00e9s ennek k\u00f6vetkezt\u00e9ben esetleg n\u00e9mi le\u00e1ll\u00e1s t\u00f6rt\u00e9nik. B\u00e1r nem voltak val\u00f3s okai ennek az \u00fajraind\u00edt\u00e1snak.<\/p>\n<p>Ennek k\u00f6vetkezt\u00e9ben a jelenlegi c\u00edmk\u00e9z\u00e9si s\u00e9ma miatt t\u00f6bb k\u00fcl\u00f6n Git-repozit\u00f3riumot kell l\u00e9trehozni, \u00e9s felmer\u00fcl a probl\u00e9ma az ezeknek a repozit\u00f3riumoknak a kiad\u00e1s\u00e1nak szervez\u00e9s\u00e9vel. \u00d6sszess\u00e9g\u00e9ben ez a s\u00e9ma t\u00falterhelt \u00e9s bonyolult. Jobb, ha sok szolg\u00e1ltat\u00e1st egyetlen repozit\u00f3riumban egyes\u00edt\u00fcnk, \u00e9s olyan Docker-c\u00edmk\u00e9ket hozunk l\u00e9tre, hogy elker\u00fclj\u00fck a felesleges \u00fajraind\u00edt\u00e1sokat.<\/p>\n<h3>C\u00edmk\u00e9z\u00e9s Git-commit alapj\u00e1n<\/h3>\n<p>\nA werf-ben is l\u00e9tezik Git-commitokkal kapcsolatos c\u00edmk\u00e9z\u00e9si strat\u00e9gia.<\/p>\n<p>A Git-commit a Git-repozit\u00f3rium tartalm\u00e1nak azonos\u00edt\u00f3ja, \u00e9s a Git-repozit\u00f3riumban a f\u00e1jlok m\u00f3dos\u00edt\u00e1sainak t\u00f6rt\u00e9net\u00e9t\u0151l f\u00fcgg, ez\u00e9rt logikusnak t\u0171nik, hogy ezt haszn\u00e1ljuk a Docker Registry-ben l\u00e9v\u0151 k\u00e9pek c\u00edmk\u00e9z\u00e9s\u00e9re.<\/p>\n<p>Azonban a Git-commit alapj\u00e1n t\u00f6rt\u00e9n\u0151 c\u00edmk\u00e9z\u00e9snek ugyanazok a h\u00e1tr\u00e1nyai vannak, mint a Git-\u00e1gak vagy Git-c\u00edmk\u00e9k eset\u00e9ben:<\/p>\n<ul>\n<li> Lehetett l\u00e9trehozni \u00fcres commitot, amely nem v\u00e1ltoztat a f\u00e1jlokon, mik\u00f6zben a Docker-k\u00e9p c\u00edmk\u00e9je megv\u00e1ltozik.<\/li>\n<li> Lehetett l\u00e9trehozni merge commitot, amely szint\u00e9n nem v\u00e1ltoztat a f\u00e1jlokon, de a Docker-k\u00e9p c\u00edmk\u00e9je megv\u00e1ltozik.<\/li>\n<li> Lehetett l\u00e9trehozni olyan commitot, amely a Git-ben olyan f\u00e1jlokat v\u00e1ltoztat meg, amelyek nem ker\u00fclnek be a k\u00e9pbe, \u00edgy a Docker-k\u00e9p c\u00edmk\u00e9je ism\u00e9t megv\u00e1ltozik.<\/li>\n<\/ul>\n<p><\/p>\n<h2>A Git-\u00e1g neve szerinti c\u00edmk\u00e9z\u00e9s nem t\u00fckr\u00f6zi a k\u00e9p verzi\u00f3j\u00e1t<\/h2>\n<p>\nVan egy m\u00e1sik probl\u00e9ma is, amely a Git-\u00e1gak szerinti c\u00edmk\u00e9z\u00e9si strat\u00e9gi\u00e1hoz kapcsol\u00f3dik.<\/p>\n<p>A branch nev\u00e9nek szerinti c\u00edmk\u00e9z\u00e9s addig m\u0171k\u00f6dik, am\u00edg a branch commitjei id\u0151rendi sorrendben \u00f6sszegy\u0171jt\u00e9sre ker\u00fclnek.<\/p>\n<p>Ha a felhaszn\u00e1l\u00f3 az aktu\u00e1lis s\u00e9ma alapj\u00e1n \u00fajra\u00e9p\u00edti egy r\u00e9gi commitot, amely egy bizonyos \u00e1ghoz kapcsol\u00f3dik, akkor a werf fel\u00fcl\u00edrja a Docker c\u00edmke alatt tal\u00e1lhat\u00f3 k\u00e9pet a r\u00e9gi commit \u00fajonnan \u00e9p\u00edtett verzi\u00f3j\u00e1val. Az ezen c\u00edmk\u00e9t haszn\u00e1l\u00f3 telep\u00edt\u00e9sek a j\u00f6v\u0151ben megszak\u00edthatj\u00e1k a kapcsolatot a CI rendszerrel, \u00e9s szinkroniz\u00e1latlann\u00e1 v\u00e1lhatnak, amikor \u00fajraind\u00edtj\u00e1k a podokat, \u00edgy az alkalmaz\u00e1sunk elvesz\u00edti a kapcsolatot a CI rendszerrel.<\/p>\n<p>Ezenk\u00edv\u00fcl, ha egym\u00e1s ut\u00e1n sok push-t hajtanak v\u00e9gre egy \u00e1gon kis id\u0151k\u00f6z\u00f6nk\u00e9nt, a r\u00e9gi commit k\u00e9s\u0151bb is ker\u00fclhet a feldolgoz\u00e1sra, mint az \u00fajabb: a r\u00e9gi image verzi\u00f3 fel\u00fcl\u00edrhatja az \u00fajat a Git \u00e1g c\u00edmk\u00e9j\u00e9n. Ezeket a probl\u00e9m\u00e1kat egy CI\/CD rendszer (p\u00e9ld\u00e1ul a GitLab CI az utols\u00f3 commitok sorozat\u00e1n\u00e1l egy pipeline-t ind\u00edt) k\u00e9pes kezelni. Azonban ezt nem minden rendszer t\u00e1mogatja, \u00edgy megb\u00edzhat\u00f3bb m\u00f3dot kell tal\u00e1lni e radik\u00e1lis probl\u00e9ma megel\u0151z\u00e9s\u00e9re.<\/p>\n<h2>Mi az a tartalom-alap\u00fa c\u00edmk\u00e9z\u00e9s?<\/h2>\n<p>\nTeh\u00e1t mi is az a tartalom-alap\u00fa c\u00edmk\u00e9z\u00e9s \u2014 a k\u00e9pek c\u00edmk\u00e9z\u00e9se a tartalom alapj\u00e1n.<\/p>\n<p>A Docker c\u00edmk\u00e9k l\u00e9trehoz\u00e1s\u00e1hoz nem a Git primit\u00edveit (Git \u00e1gat, Git c\u00edmk\u00e9t...) haszn\u00e1ljuk, hanem egy ellen\u0151rz\u0151 \u00f6sszeget, amely kapcsol\u00f3dik a k\u00f6vetkez\u0151kh\u00f6z:<\/p>\n<ul>\n<li> <i>a k\u00e9p tartalm\u00e1val<\/i>. A c\u00edmke azonos\u00edt\u00f3ja t\u00fckr\u00f6zi a tartalmat. Az \u00faj verzi\u00f3 \u00f6ssze\u00e1ll\u00edt\u00e1sakor ez az azonos\u00edt\u00f3 nem v\u00e1ltozik, ha a k\u00e9pen l\u00e9v\u0151 f\u00e1jlok nem m\u00f3dosultak;<\/li>\n<li> <i>a k\u00e9p l\u00e9trehoz\u00e1s\u00e1nak t\u00f6rt\u00e9net\u00e9vel a Git-ben<\/i>. A k\u00fcl\u00f6nb\u00f6z\u0151 Git \u00e1gakhoz \u00e9s a werf \u00e1ltal k\u00fcl\u00f6nb\u00f6z\u0151 \u00e9p\u00edt\u00e9si t\u00f6rt\u00e9netekhez tartoz\u00f3 k\u00e9pek k\u00fcl\u00f6nb\u00f6z\u0151 c\u00edmke-azonos\u00edt\u00f3kat fog kapni.<\/li>\n<\/ul>\n<p>\nEgy ilyen c\u00edmke-azonos\u00edt\u00f3k\u00e9nt funkcion\u00e1l a \u00fagynevezett <b>st\u00e1diumok al\u00e1\u00edr\u00e1sa<\/b>.<\/p>\n<p>Minden k\u00e9p egy sorozatb\u00f3l \u00e1ll: <code>a<\/code>, <code>before-install<\/code>, <code>git-archive<\/code>, <code>install<\/code>, <code>imports-after-install<\/code>, <code>before-setup<\/code>,\u2026 <code>git-latest-patch<\/code> stb. Minden st\u00e1diumhoz van egy azonos\u00edt\u00f3, ami a tartalm\u00e1t t\u00fckr\u00f6zi, \u2014 <b>st\u00e1dium al\u00e1\u00edr\u00e1s<\/b> <i>(stage signature)<\/i>.<\/p>\n<p>Az v\u00e9gleges k\u00e9p, amely ezekb\u0151l a st\u00e1diumokb\u00f3l \u00e1ll, a st\u00e1diumok sorozat\u00e1nak al\u00e1\u00edr\u00e1s\u00e1val van c\u00edmk\u00e9zve \u2014 <b>stages signature<\/b>, \u2014 amely \u00e1ltal\u00e1nos\u00edtja az \u00f6sszes st\u00e1dium tartalm\u00e1t.<\/p>\n<p>Minden k\u00e9pn\u00e9l az konfigur\u00e1ci\u00f3ban <code>werf.yaml<\/code> \u00e1ltal\u00e1nosan van egy ilyen al\u00e1\u00edr\u00e1sa, \u00e9s ennek megfelel\u0151en Docker c\u00edmk\u00e9je is.<\/p>\n<p>A st\u00e1diumok al\u00e1\u00edr\u00e1sa megoldja az \u00f6sszes eml\u00edtett probl\u00e9m\u00e1t:<\/p>\n<ul>\n<li> Ellen\u00e1ll az \u00fcres Git commitoknak.<\/li>\n<li> Ellen\u00e1ll azoknak a Git commitoknak, amelyek f\u00e1jlokat m\u00f3dos\u00edtanak, amelyek nem relev\u00e1nsak a k\u00e9p szempontj\u00e1b\u00f3l.<\/li>\n<li> Nem okoz probl\u00e9m\u00e1t a legfrissebb k\u00e9p fel\u00fcl\u00edr\u00e1sakor, amikor a r\u00e9gi Git commitokhoz \u00fajra\u00e9p\u00edt\u00e9seket ind\u00edtanak.<\/li>\n<\/ul>\n<p>\nMost ez az aj\u00e1nlott c\u00edmk\u00e9z\u00e9si strat\u00e9gia, amely alap\u00e9rtelmez\u00e9s szerint a werf-ben haszn\u00e1latos minden CI-rendszerhez.<\/p>\n<h2>Hogyan lehet ezt aktiv\u00e1lni \u00e9s haszn\u00e1lni a werf-ben<\/h2>\n<p>\nA kapcsol\u00f3d\u00f3 opci\u00f3 el\u00e9rhet\u0151 a parancsban <code>werf publish<\/code>: <code>--tag-by-stages-signature=true|false<\/code><\/p>\n<p>A CI rendszerben a c\u00edmk\u00e9z\u00e9si strat\u00e9gi\u00e1t a parancs hat\u00e1rozza meg <code>werf ci-env<\/code>. Kor\u00e1bban ehhez a param\u00e9tert a k\u00f6vetkez\u0151k\u00e9ppen hat\u00e1rozt\u00e1k meg <code>werf ci-env --tagging-strategy=tag-or-branch<\/code>. Most, ha megadjuk <code>werf ci-env --tagging-strategy=stages-signature<\/code> vagy ne is adjuk meg ezt az opci\u00f3t, a werf alap\u00e9rtelmez\u00e9s szerint a c\u00edmk\u00e9z\u00e9si strat\u00e9gi\u00e1t fogja haszn\u00e1lni <code>stages-signature<\/code>. A parancs <code>werf ci-env<\/code> automatikusan be\u00e1ll\u00edtja a sz\u00fcks\u00e9ges z\u00e1szl\u00f3kat a parancs sz\u00e1m\u00e1ra <code>werf build-and-publish<\/code> SysWOW64 <code>werf publish<\/code>), teh\u00e1t nincs sz\u00fcks\u00e9g tov\u00e1bbi opci\u00f3k megad\u00e1s\u00e1ra ezekhez a parancsokhoz.<\/p>\n<p>P\u00e9ld\u00e1ul a parancs:<\/p>\n<pre><code class=\"plaintext\">werf publish --stages-storage :local --images-repo registry.hello.com\/web\/core\/system --tag-by-stages-signature<\/code><\/pre>\n<p>\n\u2026a k\u00f6vetkez\u0151 k\u00e9peket l\u00e9trehozhatja:<\/p>\n<ul>\n<li> <code>registry.hello.com\/web\/core\/system\/backend:4ef339f84ca22247f01fb335bb19f46c4434014d8daa3d5d6f0e386d<\/code><\/li>\n<li> <code>registry.hello.com\/web\/core\/system\/frontend:f44206457e0a4c8a54655543f749799d10a9fe945896dab1c16996c6<\/code><\/li>\n<\/ul>\n<p>\nItt <code>4ef339f84ca22247f01fb335bb19f46c4434014d8daa3d5d6f0e386d<\/code> \u2014 ez a k\u00e9p f\u00e1zis\u00e1nak al\u00e1\u00edr\u00e1sa <code>backend<\/code>, \u00e9s <code>f44206457e0a4c8a54655543f749799d10a9fe945896dab1c16996c6<\/code> \u2014 a k\u00e9p f\u00e1zis\u00e1nak al\u00e1\u00edr\u00e1sa <code>frontend<\/code>.<\/p>\n<p>Speci\u00e1lis funkci\u00f3k haszn\u00e1lata eset\u00e9n <code>werf_container_image<\/code> \u00e9s <code>werf_container_env<\/code> a Helm sablonokban semmit nem kell m\u00f3dos\u00edtani: ezek a funkci\u00f3k automatikusan megfelel\u0151 k\u00e9pneveket gener\u00e1lnak.<\/p>\n<p>P\u00e9lda CI-rendszer konfigur\u00e1ci\u00f3j\u00e1ra:<\/p>\n<pre><code class=\"plaintext\">type multiwerf &amp;&amp; source &lt;(multiwerf use 1.1 beta)\ntype werf &amp;&amp; source &lt;(werf ci-env gitlab)\nwerf build-and-publish|deploy<\/code><\/pre>\n<p>\nTov\u00e1bbi inform\u00e1ci\u00f3 a be\u00e1ll\u00edt\u00e1sokr\u00f3l a dokument\u00e1ci\u00f3ban tal\u00e1lhat\u00f3:<\/p>\n<ul>\n<li> <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.werf.io\/v1.1\/documentation\/reference\/publish_process.html#%D1%82%D0%B5%D0%B3%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5-%D0%BE%D0%B1%D1%80%D0%B0%D0%B7%D0%BE%D0%B2-%D0%BF%D0%BE-%D1%81%D0%BE%D0%B4%D0%B5%D1%80%D0%B6%D0%B8%D0%BC%D0%BE%D0%BC%D1%83\">\u00datmutat\u00f3 \u2192 Kiad\u00e1s (publish)<\/a><\/noindex>;<\/li>\n<li> <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.werf.io\/v1.1\/documentation\/reference\/plugging_into_cicd\/overview.html#stages-signature\">CI\/CD haszn\u00e1lata \u2192 \u00c1ttekint\u00e9s \u2192 stages-signature<\/a><\/noindex>;<\/li>\n<li> <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.werf.io\/v1.1\/documentation\/guides\/gitlab_ci_cd_integration.html#gitlab-ciyml\">Integr\u00e1ci\u00f3 a GitLab CI\/CD-vel \u2192 .gitlab-ci.yml<\/a><\/noindex>.<\/li>\n<\/ul>\n<p><\/p>\n<h2>\u00d6sszesen<\/h2>\n<p><\/p>\n<ul>\n<li> Az \u00faj opci\u00f3 <code>werf publish --tag-by-stages-signature=true|false<\/code>.<\/li>\n<li> Az opci\u00f3 \u00faj \u00e9rt\u00e9ke <code>werf ci-env --tagging-strategy=stages-signature|tag-or-branch<\/code> (ha nem adja meg, alap\u00e9rtelmez\u00e9s szerint <code>stages-signature<\/code>).<\/li>\n<li> Ha kor\u00e1bban Git-commit alap\u00fa c\u00edmk\u00e9z\u00e9si opci\u00f3kat haszn\u00e1ltak (<code>WERF_TAG_GIT_COMMIT<\/code> vagy az opci\u00f3 <code>werf publish --tag-git-commit COMMIT<\/code>), akkor k\u00f6telez\u0151 v\u00e1ltani a c\u00edmk\u00e9z\u00e9si strat\u00e9gi\u00e1ra <i>stages-signature<\/i>.<\/li>\n<li> Az \u00faj projekteket a lehet\u0151 leghamarabb \u00e9rdemes az \u00faj c\u00edmk\u00e9z\u00e9si rendszerre v\u00e1ltani.<\/li>\n<li> \u00d6reg projektekn\u00e9l a werf 1.1-re val\u00f3 \u00e1tt\u00e9r\u00e9skor c\u00e9lszer\u0171 az \u00faj c\u00edmk\u00e9z\u00e9si rendszerre v\u00e1ltani, azonban a r\u00e9gi <i>tag-or-branch<\/i> tov\u00e1bbra is t\u00e1mogatott.<\/li>\n<\/ul>\n<p>\nA tartalom-alap\u00fa c\u00edmk\u00e9z\u00e9s megoldja a cikkben felsorolt probl\u00e9m\u00e1kat:<\/p>\n<ul>\n<li> A Docker-c\u00edmke nev\u00e9nek ellen\u00e1ll\u00e1sa a \u00fcres Git-commitokkal szemben.<\/li>\n<li> A Docker-c\u00edmke nev\u00e9nek ellen\u00e1ll\u00e1sa a Git-commitokkal szemben, amelyek irrelev\u00e1ns f\u00e1jlokat m\u00f3dos\u00edtanak a k\u00e9ppel kapcsolatban.<\/li>\n<li> Nem okoz probl\u00e9m\u00e1t a legfrissebb k\u00e9p fel\u00fcl\u00edr\u00e1sa a r\u00e9gi Git-commitok \u00fajra\u00e9p\u00edt\u00e9se sor\u00e1n a Git-\u00e1gakhoz.<\/li>\n<\/ul>\n<p>\nHaszn\u00e1lja! \u00c9s ne felejtsen el ben\u00e9zni hozz\u00e1nk a <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/flant\/werf\">GitHub<\/a><\/noindex>, hogy l\u00e9trehozzon egy issue-t, vagy megtal\u00e1lja a m\u00e1r megl\u00e9v\u0151t, l\u00e1jkolja, hozzon l\u00e9tre PR-t, vagy csak figyelje a projekt fejl\u0151d\u00e9s\u00e9t.<\/p>\n<h2>P.S.<\/h2>\n<p>\nOlvasson tov\u00e1bbi inform\u00e1ci\u00f3kat a blogunkban:<\/p>\n<ul>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/493170\/\">A werf 1.1-es verzi\u00f3ja: fejleszt\u00e9sek a build rendszerben ma \u00e9s j\u00f6v\u0151beni tervek<\/a><\/noindex>\u00bb<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/481306\/\">Bemutatjuk a werf 1.0 stabil verzi\u00f3j\u00e1t: mi k\u00f6ze van a GitOps-hoz, a st\u00e1tuszhoz \u00e9s a terveinkhez<\/a><\/noindex>\u00bb<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/460351\/\">werf \u2014 az eszk\u00f6z\u00fcnk CI\/CD-hez Kubernetes-ben (\u00e1ttekint\u00e9s \u00e9s a besz\u00e1mol\u00f3 vide\u00f3ja)<\/a><\/noindex>\u00bb;<\/li>\n<li> A werf \u00fajdons\u00e1gair\u00f3l sz\u00f3l\u00f3 jegyzetek ciklusa:\n<ul>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/476646\/\">3-way merge a werf-ben: telep\u00edt\u00e9s Kubernetesre Helm \u201eszteroidokkal\u201d<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/468049\/\">A werf haszn\u00e1lata komplex Helm diagramok kiad\u00e1sa sor\u00e1n<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/465131\/\">Monorepo \u00e9s multirepo t\u00e1mogat\u00e1s a werf-ben, \u00e9s mi k\u00f6ze a Docker Registryhez<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/463613\/\">Most Docker images in werf can now be built using a regular Dockerfile<\/a><\/noindex>\u00bb.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>Forr\u00e1s: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/495112\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>werf \u2014 \u043d\u0430\u0448\u0430 GitOps CLI-\u0443\u0442\u0438\u043b\u0438\u0442\u0430 \u0441 \u043e\u0442\u043a\u0440\u044b\u0442\u044b\u043c \u043a\u043e\u0434\u043e\u043c \u0434\u043b\u044f \u0441\u0431\u043e\u0440\u043a\u0438 \u0438 \u0434\u043e\u0441\u0442\u0430\u0432\u043a\u0438 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0439 \u0432 Kubernetes. \u0412 \u0440\u0435\u043b\u0438\u0437\u0435 v1.1 \u0431\u044b\u043b\u0430 \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u0435\u043d\u0430 \u043d\u043e\u0432\u0430\u044f \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u044c \u0432 \u0441\u0431\u043e\u0440\u0449\u0438\u043a\u0435 \u043e\u0431\u0440\u0430\u0437\u043e\u0432: \u0442\u0435\u0433\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435 \u043e\u0431\u0440\u0430\u0437\u043e\u0432 \u043f\u043e \u0441\u043e\u0434\u0435\u0440\u0436\u0438\u043c\u043e\u043c\u0443 \u0438\u043b\u0438 content-based tagging. \u0414\u043e \u0441\u0438\u0445 \u043f\u043e\u0440 \u0442\u0438\u043f\u0438\u0447\u043d\u0430\u044f \u0441\u0445\u0435\u043c\u0430 \u0442\u0435\u0433\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f \u0432 werf \u043f\u0440\u0435\u0434\u043f\u043e\u043b\u0430\u0433\u0430\u043b\u0430 \u0442\u0435\u0433\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435 Docker-\u043e\u0431\u0440\u0430\u0437\u043e\u0432 \u043f\u043e Git-\u0442\u0435\u0433\u0443, Git-\u0432\u0435\u0442\u043a\u0435 \u0438\u043b\u0438 Git-\u043a\u043e\u043c\u043c\u0438\u0442\u0443. \u041d\u043e \u0443 \u0432\u0441\u0435\u0445 \u044d\u0442\u0438\u0445 \u0441\u0445\u0435\u043c \u0435\u0441\u0442\u044c \u043d\u0435\u0434\u043e\u0441\u0442\u0430\u0442\u043a\u0438, [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":76770,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-76769","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.3 - aioseo.com -->\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\/hu\/blog\/administrirovanie\/content-based-tagging-v-sborshhike-werf-zachem-i-kak-eto-rabotaet\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.3\" \/>\n\t\t<meta property=\"og:locale\" content=\"hu_HU\" \/>\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\udd47Content-based tagging \u0432 \u0441\u0431\u043e\u0440\u0449\u0438\u043a\u0435 werf: \u0437\u0430\u0447\u0435\u043c \u0438 \u043a\u0430\u043a \u044d\u0442\u043e \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442? | ProHoster\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/hu\/blog\/administrirovanie\/content-based-tagging-v-sborshhike-werf-zachem-i-kak-eto-rabotaet\" \/>\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=\"2020-04-04T11:42:27+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-04-04T11:42:27+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\udd47Tartalom-alap\u00fa c\u00edmk\u00e9z\u00e9s a werf gy\u0171jt\u0151ben: mi\u00e9rt \u00e9s hogyan m\u0171k\u00f6dik? | ProHoster","description":"","canonical_url":"https:\/\/prohoster.info\/hu\/blog\/administrirovanie\/content-based-tagging-v-sborshhike-werf-zachem-i-kak-eto-rabotaet","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"hu_HU","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\udd47Content-based tagging \u0432 \u0441\u0431\u043e\u0440\u0449\u0438\u043a\u0435 werf: \u0437\u0430\u0447\u0435\u043c \u0438 \u043a\u0430\u043a \u044d\u0442\u043e \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442? | ProHoster","og:url":"https:\/\/prohoster.info\/hu\/blog\/administrirovanie\/content-based-tagging-v-sborshhike-werf-zachem-i-kak-eto-rabotaet","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-04-04T11:42:27+00:00","article:modified_time":"2020-04-04T11:42:27+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"76769","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 17:30:22","updated":"2022-09-28 05:59:33","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/posts\/76769","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/comments?post=76769"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/posts\/76769\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/media\/76770"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/media?parent=76769"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/categories?post=76769"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/hu\/wp-json\/wp\/v2\/tags?post=76769"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}