{"id":92048,"date":"2020-08-22T07:42:57","date_gmt":"2020-08-22T05:42:57","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/sovremennye-prilozheniya-na-openshift-chast-3-openshift-kak-sreda-razrabotki-i-konvejery-openshift-pipelines"},"modified":"2020-08-22T07:42:57","modified_gmt":"2020-08-22T05:42:57","slug":"sovremennye-prilozheniya-na-openshift-chast-3-openshift-kak-sreda-razrabotki-i-konvejery-openshift-pipelines","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/sovremennye-prilozheniya-na-openshift-chast-3-openshift-kak-sreda-razrabotki-i-konvejery-openshift-pipelines","title":{"rendered":"Aplikacione moderne n\u00eb OpenShift, pjesa 3: OpenShift si nj\u00eb ambient zhvillimi dhe konvergjencat OpenShift Pipelines","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

P\u00ebrsh\u00ebndetje t\u00eb gjith\u00ebve n\u00eb k\u00ebt\u00eb blog! Ky \u00ebsht\u00eb postimi i tret\u00eb n\u00eb seri, ku tregojm\u00eb se si t\u00eb implementoni aplikacione web moderne n\u00eb Red Hat OpenShift.<\/p>\n

\"Aplikacione
\n
\nN\u00eb dy postimet e m\u00ebparshme, ne treguam se si t\u00eb implementoni aplikacione web moderne n\u00eb vet\u00ebm disa hapa dhe si t\u00eb p\u00ebrdorni imazhin e ri S2I me nj\u00eb imazh t\u00eb gatsh\u00ebm t\u00eb serverit HTTP, si NGINX me ndihm\u00ebn e nd\u00ebrlidhjeve t\u00eb nd\u00ebrlidhura p\u00ebr t\u00eb organizuar implementimin n\u00eb prodhim.<\/p>\n

Sot do t\u00eb tregojm\u00eb se si t\u00eb lanconi nj\u00eb server zhvillimi p\u00ebr aplikacionin tuaj n\u00eb platform\u00ebn OpenShift dhe si ta sinkronizoni at\u00eb me sistemin tuaj lokal t\u00eb skedar\u00ebve, si dhe do t\u00eb flasim p\u00ebr \u00e7far\u00eb \u00ebsht\u00eb OpenShift Pipelines dhe si mund t\u00eb p\u00ebrdoret si nj\u00eb alternativ\u00eb ndaj nd\u00ebrlidhjeve t\u00eb nd\u00ebrlidhura.
\n<\/a><\/noindex><\/p>\n

OpenShift si nj\u00eb ambient zhvillimi<\/h3>\n

<\/p>\n

Procesi i pun\u00ebs n\u00eb zhvillim<\/h4>\n

\nSi\u00e7 u tha n\u00eb postimin e par\u00eb<\/a><\/noindex>, procesi standard i zhvillimit p\u00ebr aplikacionet moderne web \u00ebsht\u00eb thjesht nj\u00eb \"server zhvillimi\" q\u00eb ndjek ndryshimet n\u00eb skedar\u00ebt lokal\u00eb. Kur ndodhin k\u00ebto ndryshime, ndodh nd\u00ebrtimi i aplikacionit dhe pastaj ato p\u00ebrdit\u00ebsohen n\u00eb shfletues.<\/p>\n

N\u00eb shumic\u00ebn e frameworkeve moderne, nj\u00eb \"server zhvillimi\" \u00ebsht\u00eb i p\u00ebrfshir\u00eb n\u00eb veglat p\u00ebrkat\u00ebse t\u00eb komand\u00ebs.<\/p>\n

Shembulli lokal<\/h4>\n

\nFillimisht, le t\u00eb shohim se si funksionon n\u00eb rastin e ekzekutimit lokal t\u00eb aplikacioneve. Si shembull, t\u00eb marrim aplikacionin React<\/a><\/noindex> nga artikujt paraardh\u00ebs, edhe pse pothuajse t\u00eb nj\u00ebjtat koncepte t\u00eb procesit t\u00eb pun\u00ebs zbatohen n\u00eb t\u00eb gjitha frameworket moderne.
\nPra, p\u00ebr t\u00eb nisur \"serverin e zhvillimit\" n\u00eb shembullin ton\u00eb me React, do t\u00eb shkruajm\u00eb komand\u00ebn e m\u00ebposhtme:<\/p>\n

$ npm run start\n<\/code><\/pre>\n
\nN\u00eb at\u00eb moment, n\u00eb dritaren e terminalit do t\u00eb kemi di\u00e7ka t\u00eb ngjashme:<\/p>\n
\"Aplikacione<\/p>\n
Dhe aplikacioni yn\u00eb do t\u00eb hapet n\u00eb shfletuesin p\u00ebrkat\u00ebs:<\/p>\n
\"Aplikacione<\/p>\n
Tani, n\u00ebse b\u00ebjm\u00eb nj\u00eb ndryshim n\u00eb skedarin, aplikacioni duhet t\u00eb p\u00ebrdit\u00ebsohet n\u00eb shfletues.<\/p>\n
Mir\u00eb, p\u00ebr zhvillimin n\u00eb modalitetin lokal \u00ebsht\u00eb e qart\u00eb, por si ta arrijm\u00eb t\u00eb nj\u00ebjt\u00ebn gj\u00eb n\u00eb OpenShift?<\/p>\n
Serveri i zhvillimit n\u00eb OpenShift<\/h4>\n
\nN\u00ebse e mbani mend, n\u00eb postimin e m\u00ebparsh\u00ebm<\/a><\/noindex>, ne kemi diskutuar faz\u00ebn e njohur si faza e nisjes (run phase) t\u00eb imazhit S2I dhe kemi par\u00eb se n\u00eb m\u00ebnyr\u00eb t\u00eb paracaktuar, mbajtja e aplikacionit ton\u00eb web kryhet nga moduli serve.<\/p>\n
Megjithat\u00eb, n\u00ebse e shikoni m\u00eb me kujdes run script<\/a><\/noindex> nga ai shembull, ka nj\u00eb variab\u00ebl ambienti $NPM_RUN, e cila lejon t\u00eb ekzekutohet edhe komanda juaj.<\/p>\n
P\u00ebr shembull, mund t\u00eb p\u00ebrdorim modulin nodeshift p\u00ebr t\u00eb vendosur aplikacionin ton\u00eb:<\/p>\n
$ npx nodeshift --deploy.env NPM_RUN=\"yarn start\" --dockerImage=nodeshift\/ubi8-s2i-web-app\n<\/code><\/pre>\n
\nV\u00ebrejtje: shembulli m\u00eb sip\u00ebr jepet n\u00eb nj\u00eb form\u00eb t\u00eb shkurtuar p\u00ebr t\u00eb ilustruar iden\u00eb e p\u00ebrgjithshme.<\/i><\/p>\n
K\u00ebtu ne kemi shtuar n\u00eb vendosjen ton\u00eb nj\u00eb variab\u00ebl ambienti NPM_RUN, e cila i thot\u00eb faz\u00ebs s\u00eb ekzekutimit se duhet t\u00eb nis\u00eb komand\u00ebn yarn start, e cila nis serverin e zhvillimit React brenda pod-it ton\u00eb OpenShift.<\/p>\n
N\u00ebse shikoni log-un e pod-it q\u00eb po punon, do t\u00eb jet\u00eb di\u00e7ka e till\u00eb:<\/p>\n
\"Aplikacione<\/p>\n
Sigurisht, gjith\u00e7ka do t\u00eb jet\u00eb e pavler\u00eb deri sa t\u00eb mund t\u00eb sinkronizojm\u00eb kodin lokal me kodin, i cili gjithashtu kontrollohet p\u00ebr ndryshime, por jeton n\u00eb nj\u00eb server t\u00eb larg\u00ebt.<\/p>\n
Sinkronizimi i kodit t\u00eb larg\u00ebt dhe lokal<\/h4>\n
\nFatkeq\u00ebsisht, nodeshift ofron ndihm\u00eb t\u00eb leht\u00eb me sinkronizimin, dhe p\u00ebr t\u00eb p\u00ebrcjell\u00eb ndryshimet, mund t\u00eb p\u00ebrdorni komand\u00ebn watch.<\/p>\n
Prandaj, pas ekzekutimit t\u00eb komand\u00ebs p\u00ebr t\u00eb dislokuar serverin e zhvillimit p\u00ebr aplikacionin ton\u00eb, mund ta p\u00ebrdorim me besim k\u00ebt\u00eb komand\u00eb:<\/p>\n
$ npx nodeshift watch\n<\/code><\/pre>\n
\nSi rezultat, do t\u00eb lidhet me pod-in q\u00eb krijuam pak m\u00eb her\u00ebt, aktivizohet sinkronizimi i skedar\u00ebve tan\u00eb lokal\u00eb me klasterin e larg\u00ebt, dhe skedar\u00ebt n\u00eb sistemin ton\u00eb lokal do t\u00eb fillojn\u00eb t\u00eb monitorohen p\u00ebr ndryshime.<\/p>\n
Prandaj, n\u00ebse tani p\u00ebrdit\u00ebsojm\u00eb skedarin src\/App.js, sistemi do t\u00eb reagoj\u00eb ndaj k\u00ebtyre ndryshimeve, do t'i kopjoj\u00eb ato n\u00eb klasterin e larg\u00ebt dhe do t\u00eb niste serverin e zhvillimit, i cili do t\u00eb p\u00ebrdit\u00ebsoj\u00eb aplikacionin ton\u00eb n\u00eb shfletues.<\/p>\n
P\u00ebr t\u00eb pasur nj\u00eb pamje t\u00eb plot\u00eb, do t\u00eb tregojm\u00eb si duken k\u00ebto komanda n\u00eb t\u00ebr\u00ebsi:<\/p>\n
$ npx nodeshift --strictSSL=false --dockerImage=nodeshift\/ubi8-s2i-web-app --build.env YARN_ENABLED=true --expose --deploy.env NPM_RUN=\"yarn start\" --deploy.port 3000\n\n$ npx nodeshift watch --strictSSL=false\n<\/code><\/pre>\n
\nKomanda watch \u00ebsht\u00eb nj\u00eb abstraksion mbi komand\u00ebn oc rsync, p\u00ebr t'u informuar m\u00eb shum\u00eb se si funksionon, mund t\u00eb m\u00ebsoni. k\u00ebtu<\/a><\/noindex>.<\/p>\n
Ky ishte nj\u00eb shembull p\u00ebr React, por nj\u00eb metod\u00eb e till\u00eb mund t\u00eb p\u00ebrdoret po ashtu me frameworke t\u00eb tjera, thjesht shkrini variabl\u00ebn e mjedisit NPM_RUN sipas nevoj\u00ebs.
\n\u2003<\/p>\n
Pipelinat Openshift Pipelines<\/h3>\n
\"Aplikacione<\/p>\n
M\u00eb pas do t\u00eb flasim p\u00ebr nj\u00eb mjet t\u00eb till\u00eb si OpenShift Pipelines, dhe se si mund t\u00eb p\u00ebrdoret si nj\u00eb alternativ\u00eb p\u00ebr nd\u00ebrlidhjet e nd\u00ebrtimit chain build.<\/p>\n
\u00c7far\u00eb \u00ebsht\u00eb OpenShift Pipelines<\/h4>\n
\nOpenShift Pipelines \u00ebsht\u00eb nj\u00eb sistem CI\/CD i orientuar drejt cloud-it p\u00ebr integrim dhe shp\u00ebrndarje t\u00eb vazhdueshme, i dedikuar p\u00ebr organizimin e pipelinave duke p\u00ebrdorur Tekton. Tekton \u00ebsht\u00eb nj\u00eb framework CI\/CD me kod t\u00eb hapur, i natyrsh\u00ebm p\u00ebr Kubernetes, q\u00eb lejon automatizimin e publikimeve n\u00eb platforma t\u00eb ndryshme (Kubernetes, serverless, makina virtuale, etj.) duke e abstraktuar at\u00eb nga niveli i posht\u00ebm.<\/p>\n
P\u00ebr t\u00eb kuptuar k\u00ebt\u00eb artikull jan\u00eb t\u00eb nevojshme disa njohuri mbi Pipelines, prandaj ju inkurajojm\u00eb q\u00eb fillimisht t\u00eb njiheni me manualin zyrtar<\/a><\/noindex>.<\/p>\n
Konfigurimi i ambientit t\u00eb pun\u00ebs<\/h4>\n
\nP\u00ebr t'u luajtur me shembujt nga ky artikull, s\u00eb pari duhet t\u00eb p\u00ebrgatitni ambientin e pun\u00ebs:<\/p>\n
    \n
  1. Instaloni dhe konfiguroni nj\u00eb kluster OpenShift 4. N\u00eb shembujt tan\u00eb do t\u00eb p\u00ebrdorim CodeReady Containers (CRD), p\u00ebr informacionin n\u00eb lidhje me instalimin e t\u00eb cilit mund t\u00eb gjeni k\u00ebtu<\/a><\/noindex>.<\/li>\n
  2. Pasi klustri t\u00eb jet\u00eb gati, duhet t\u00eb instaloni Operatorin e Pipeline. Mos e keni frik\u00eb, \u00ebsht\u00eb e leht\u00eb, p\u00ebr udh\u00ebzimet e instalimit k\u00ebtu<\/a><\/noindex>.<\/li>\n
  3. Shkarko Tekton CLI<\/a><\/noindex> (tkn) k\u00ebtu<\/a><\/noindex>.<\/li>\n
  4. Startoni mjetin e komand\u00ebs create-react-app p\u00ebr t\u00eb krijuar nj\u00eb aplikacion, i cili m\u00eb von\u00eb do t\u00eb implementohet (ky \u00ebsht\u00eb nj\u00eb aplikacion i thjesht\u00eb React<\/a><\/noindex>).<\/li>\n
  5. (Opcionale) Kloni repozitorin p\u00ebr t\u00eb ekzekutuar lokalisht shembullin e aplikacionit me komand\u00ebn npm install dhe pastaj npm start.<\/li>\n<\/ol>\n
    \nN\u00eb repozitorin e aplikacionit gjithashtu do t\u00eb ket\u00eb nj\u00eb folder k8s, ku do t\u00eb gjenden YAML-t\u00eb p\u00ebr Kubernetes\/OpenShift, t\u00eb p\u00ebrdorura p\u00ebr implementimin e aplikacionit. Aty do t\u00eb jen\u00eb Tasks, ClusterTasks, Resources dhe Pipelines, t\u00eb cilat do t\u2019i krijojm\u00eb n\u00eb k\u00ebt\u00eb repozitorit<\/a><\/noindex>.<\/p>\n
    Le t\u00eb fillojm\u00eb<\/h4>\n
    \nM\u00eb par\u00eb, p\u00ebr shembullin ton\u00eb, duhet t\u00eb krijojm\u00eb nj\u00eb projekt t\u00eb ri n\u00eb klusterin OpenShift. Ta quajm\u00eb k\u00ebt\u00eb projekt webapp-pipeline dhe ta krijojm\u00eb me komand\u00ebn e m\u00ebposhtme:<\/p>\n
    $ oc new-project webapp-pipeline\n<\/code><\/pre>\n
    \nM\u00eb von\u00eb, ky em\u00ebr projekti do t\u00eb shfaqet n\u00eb kod, prandaj n\u00ebse vendosni ta em\u00ebrtoni ndryshe, mos harroni t\u00eb ndryshoni p\u00ebrkat\u00ebsisht kodin n\u00eb shembuj. Duke filluar nga kjo pik\u00eb, do t\u00eb shkojm\u00eb jo nga lart-posht\u00eb, por nga posht\u00eb-lart: dometh\u00ebn\u00eb, m\u00eb par\u00eb do t\u00eb krijojm\u00eb t\u00eb gjitha p\u00ebrb\u00ebr\u00ebsit e tubacionit, dhe pastaj vet\u00eb tubacionin.<\/p>\n
    Pra, hapi i par\u00eb\u2026<\/p>\n
    Detyrat Tasks<\/h4>\n
    \nDo t\u00eb krijojm\u00eb disa detyra (tasks), t\u00eb cilat m\u00eb von\u00eb do t\u00eb ndihmojn\u00eb p\u00ebr t\u00eb shp\u00ebrndar\u00eb aplikacionin n\u00eb kuad\u00ebr t\u00eb tubacionit ton\u00eb pipeline. Detyra e par\u00eb \u2013 apply_manifests_task \u2013 \u00ebsht\u00eb p\u00ebrgjegj\u00ebse p\u00ebr aplikimin e YAML t\u00eb burimeve Kubernetes (sh\u00ebrbimi, shp\u00ebrndarja dhe rruga), t\u00eb cilat ndodhen n\u00eb dosjen k8s t\u00eb aplikacionit ton\u00eb. Detyra e dyt\u00eb \u2013 update_deployment_task \u2013 \u00ebsht\u00eb p\u00ebrgjegj\u00ebse p\u00ebr p\u00ebrdit\u00ebsimin e imazhit t\u00eb shp\u00ebrndar\u00eb tashm\u00eb n\u00eb at\u00eb q\u00eb krijohet nga tubacioni yn\u00eb.<\/p>\n
    Mos u shqet\u00ebsoni n\u00ebse ende nuk \u00ebsht\u00eb shum\u00eb e qart\u00eb. N\u00eb t\u00eb v\u00ebrtet\u00eb, k\u00ebto detyra jan\u00eb si nj\u00eb lloj utiliteti, dhe ne do t\u2019i shqyrtojm\u00eb ato m\u00eb n\u00eb detaje pak m\u00eb von\u00eb. Tani, le t\u00eb krijojm\u00eb ato:<\/p>\n
    $ oc create -f https:\/\/raw.githubusercontent.com\/nodeshift\/webapp-pipeline-tutorial\/master\/tasks\/update_deployment_task.yaml\n$ oc create -f https:\/\/raw.githubusercontent.com\/nodeshift\/webapp-pipeline-tutorial\/master\/tasks\/apply_manifests_task.yaml\n<\/code><\/pre>\n
    \nPastaj, me ndihm\u00ebn e komand\u00ebs tkn CLI, do t\u00eb kontrollojm\u00eb q\u00eb detyrat u krijuan:<\/p>\n
    $ tkn task ls\n\nEMRI                MOSHA\napply-manifests     1 minut\u00eb m\u00eb par\u00eb\nupdate-deployment   1 minut\u00eb m\u00eb par\u00eb\n<\/code><\/pre>\n
    \nSh\u00ebnim: k\u00ebto jan\u00eb detyrat lokale t\u00eb projektit tuaj aktual.<\/i><\/p>\n
    Detyrat e klasterit<\/h4>\n
    \nDetyrat e klasterit jan\u00eb n\u00eb thelb t\u00eb nj\u00ebjtat si detyrat e zakonshme. Kjo do t\u00eb thot\u00eb se ato jan\u00eb nj\u00eb koleksion i rip\u00ebrdorsh\u00ebm i hapave, t\u00eb cilat kombinohen n\u00eb nj\u00eb m\u00ebnyr\u00eb ose n\u00eb nj\u00eb tjet\u00ebr kur ekzekutohet nj\u00eb detyr\u00eb specifike. Dallimi \u00ebsht\u00eb se detyra e klasterit \u00ebsht\u00eb e disponueshme kudo brenda klasterit. P\u00ebr t\u00eb par\u00eb list\u00ebn e detyrave t\u00eb klasterit, t\u00eb cilat krijohen automatikisht duke shtuar Operatorin e Pipeline, do t\u00eb p\u00ebrdorim p\u00ebrs\u00ebri komand\u00ebn tkn CLI:<\/p>\n
    $ tkn clustertask ls\n\nEMRI                       MOSHA\nbuildah                    1 dit\u00eb m\u00eb par\u00eb\nbuildah-v0-10-0            1 dit\u00eb m\u00eb par\u00eb\njib-maven                  1 dit\u00eb m\u00eb par\u00eb\nkn                         1 dit\u00eb m\u00eb par\u00eb\nmaven                      1 dit\u00eb m\u00eb par\u00eb\nopenshift-client           1 dit\u00eb m\u00eb par\u00eb\nopenshift-client-v0-10-0   1 dit\u00eb m\u00eb par\u00eb\ns2i                        1 dit\u00eb m\u00eb par\u00eb\ns2i-go                     1 dit\u00eb m\u00eb par\u00eb\ns2i-go-v0-10-0             1 dit\u00eb m\u00eb par\u00eb\ns2i-java-11                1 dit\u00eb m\u00eb par\u00eb\ns2i-java-11-v0-10-0        1 dit\u00eb m\u00eb par\u00eb\ns2i-java-8                 1 dit\u00eb m\u00eb par\u00eb\ns2i-java-8-v0-10-0         1 dit\u00eb m\u00eb par\u00eb\ns2i-nodejs                 1 dit\u00eb m\u00eb par\u00eb\ns2i-nodejs-v0-10-0         1 dit\u00eb m\u00eb par\u00eb\ns2i-perl                   1 dit\u00eb m\u00eb par\u00eb\ns2i-perl-v0-10-0           1 dit\u00eb m\u00eb par\u00eb\ns2i-php                    1 dit\u00eb m\u00eb par\u00eb\ns2i-php-v0-10-0            1 dit\u00eb m\u00eb par\u00eb\ns2i-python-3               1 dit\u00eb m\u00eb par\u00eb\ns2i-python-3-v0-10-0       1 dit\u00eb m\u00eb par\u00eb\ns2i-ruby                   1 dit\u00eb m\u00eb par\u00eb\ns2i-ruby-v0-10-0           1 dit\u00eb m\u00eb par\u00eb\ns2i-v0-10-0                1 dit\u00eb m\u00eb par\u00eb\n<\/code><\/pre>\n
    \nTani le t\u00eb krijojm\u00eb dy detyra klasterike. E para do t\u00eb krijoj\u00eb nj\u00eb imazh S2I dhe do ta d\u00ebrgoj\u00eb n\u00eb regjistrin e brendsh\u00ebm OpenShift; e dyta do t\u00eb ekzekutoj\u00eb nd\u00ebrtimin e imazhit ton\u00eb mbi baz\u00ebn e NGINX, duke p\u00ebrdorur si p\u00ebrmbajtje aplikacionin q\u00eb e kemi nd\u00ebrtuar m\u00eb par\u00eb.<\/p>\n
    Krijojm\u00eb dhe d\u00ebrgojm\u00eb imazh<\/h4>\n
    \nKur krijojm\u00eb detyr\u00ebn e par\u00eb, do t\u00eb p\u00ebrs\u00ebrisim at\u00eb q\u00eb b\u00ebm\u00eb n\u00eb artikullin e m\u00ebparsh\u00ebm mbi nd\u00ebrlidhjet e nd\u00ebrtimit. T\u00eb kujtojm\u00eb se ne p\u00ebrdor\u00ebm imazhin S2I (ubi8-s2i-web-app) p\u00ebr t\u00eb \"nd\u00ebrtuar\" aplikacionin ton\u00eb, dhe n\u00eb fund mor\u00ebm nj\u00eb imazh, i cili ruhej n\u00eb regjistrin e brendsh\u00ebm OpenShift. Tani do t\u00eb p\u00ebrdorim k\u00ebt\u00eb imazh S2I t\u00eb aplikacionit web p\u00ebr t\u00eb krijuar nj\u00eb DockerFile p\u00ebr aplikacionin ton\u00eb, dhe m\u00eb pas do t\u00eb angazhojm\u00eb Buildah p\u00ebr t\u00eb kryer nd\u00ebrtimin real dhe p\u00ebr t\u00eb d\u00ebrguar imazhin e marr\u00eb n\u00eb regjistrin e brendsh\u00ebm OpenShift, pasi kjo \u00ebsht\u00eb sakt\u00ebsisht ajo q\u00eb b\u00ebn OpenShift kur ju vendosni aplikacionet tuaja duke p\u00ebrdorur NodeShift.<\/p>\n
    Po pyesni, nga e dim\u00eb t\u00eb gjitha k\u00ebto? Nga \u043e\u0444\u0438\u0446\u0438\u0430\u043b\u044c\u043d\u043e\u0439 \u0432\u0435\u0440\u0441\u0438\u0438 official Node.js<\/a><\/noindex>, ne thjesht e kopjuam at\u00eb dhe e p\u00ebrshtat\u00ebm p\u00ebr vete.<\/p>\n
    K\u00ebshtu, tani krijojm\u00eb detyr\u00ebn klasterike s2i-web-app:<\/p>\n
    $ oc create -f https:\/\/raw.githubusercontent.com\/nodeshift\/webapp-pipeline-tutorial\/master\/clustertasks\/s2i-web-app-task.yaml\n<\/code><\/pre>\n
    \nNuk do t\u00eb merremi me detaje t\u00eb shumta rreth k\u00ebsaj, por do t\u00eb ndalemi vet\u00ebm te parametri OUTPUT_DIR:<\/p>\n
    params:\n      - name: OUTPUT_DIR\n        description: Vendi i drejtoris\u00eb s\u00eb daljes s\u00eb nd\u00ebrtimit\n        default: build\n<\/code><\/pre>\n
    \nNga e drejta, ky parametr \u00ebsht\u00eb i barabart\u00eb me build, dhe aty React ruan p\u00ebrmbajtjen e nd\u00ebrtuar. N\u00eb kuad\u00ebr t\u00eb framework-\u00ebve t\u00eb tjer\u00eb p\u00ebrdoren rrug\u00eb t\u00eb tjera, p\u00ebr shembull, n\u00eb Ember kjo \u00ebsht\u00eb dist. T\u00eb dh\u00ebnat e detyr\u00ebs son\u00eb t\u00eb par\u00eb klaster do t\u00eb p\u00ebrb\u00ebhen nga nj\u00eb imazh, q\u00eb p\u00ebrmban HTML-n\u00eb, JavaScript dhe CSS-n\u00eb q\u00eb kemi mbledhur.<\/p>\n
    Krijojm\u00eb nj\u00eb imazh n\u00eb baz\u00eb t\u00eb NGINX<\/h4>\n
    \nSa i p\u00ebrket detyr\u00ebs son\u00eb t\u00eb dyt\u00eb klaster, ajo duhet t\u00eb krijoj\u00eb nj\u00eb imazh mbi baz\u00ebn e NGINX, duke p\u00ebrdorur p\u00ebrmbajtjen e aplikacionit q\u00eb kemi nd\u00ebrtuar m\u00eb par\u00eb. N\u00eb thelb, kjo \u00ebsht\u00eb pjesa e atij kapitulli t\u00eb m\u00ebparsh\u00ebm, ku shqyrtuam nd\u00ebrlidhjet e nd\u00ebrtimit.<\/p>\n
    P\u00ebr k\u00ebt\u00eb, ne - pik\u00ebrisht si m\u00eb lart - do t\u00eb krijojm\u00eb detyr\u00ebn klaster webapp-build-runtime:<\/p>\n
    $ oc create -f https:\/\/raw.githubusercontent.com\/nodeshift\/webapp-pipeline-tutorial\/master\/clustertasks\/webapp-build-runtime-task.yaml\n<\/code><\/pre>\n
    \nN\u00ebse shikoni kodin e k\u00ebtyre detyrave t\u00eb grumbullit, do t\u00eb vini re se nuk specifikohet depoja Git me t\u00eb cil\u00ebn punojm\u00eb, apo emrat e imazheve q\u00eb krijojm\u00eb. Ne vet\u00ebm p\u00ebrcaktojm\u00eb se \u00e7far\u00eb sakt\u00ebsisht po transferojm\u00eb n\u00eb Git, ose ndonj\u00eb imazh, ku duhet t\u00eb ruhet imazhi p\u00ebrfundimtar. Prandaj, k\u00ebto detyra t\u00eb grumbullit mund t\u00eb rip\u00ebrdoren edhe gjat\u00eb pun\u00ebs me aplikacione t\u00eb tjera.<\/p>\n
    Dhe k\u00ebtu kalojm\u00eb me eleganc\u00eb n\u00eb pik\u00ebn tjet\u00ebr...<\/p>\n
    Burimet<\/h4>\n
    \nPra, duke qen\u00eb se, si\u00e7 sapo tham\u00eb, detyrat e grumbullit duhet t\u00eb jen\u00eb sa m\u00eb t\u00eb p\u00ebrgjithshme, na nevojitet t\u00eb krijojm\u00eb burime q\u00eb do t\u00eb p\u00ebrdoren n\u00eb hyrje (depoja Git) dhe n\u00eb dalje (imazhet p\u00ebrfundimtare). Burimi i par\u00eb q\u00eb na nevojitet \u00ebsht\u00eb Git, ku ndodhet aplikacioni yn\u00eb, di\u00e7ka si kjo:<\/p>\n
    # This resource is the location of the git repo with the web application source\napiVersion: tekton.dev\/v1alpha1\nkind: PipelineResource\nmetadata:\n  name: web-application-repo\nspec:\n  type: git\n  params:\n    - name: url\n      value: https:\/\/github.com\/nodeshift-starters\/react-pipeline-example\n    - name: revision\n      value: master\n<\/code><\/pre>\n
    \nK\u00ebtu, PipelineResource ka llojin git. \u00c7el\u00ebsi url n\u00eb seksionin params tregon depozitat specifike dhe caktimin e deg\u00ebs master (kjo \u00ebsht\u00eb opsionale, por e shkruajm\u00eb p\u00ebr kompletim).<\/p>\n
    Tani na nevojitet t\u00eb krijojm\u00eb nj\u00eb burim p\u00ebr imazhin, ku do t\u00eb ruhen rezultatet e ekzekutimit t\u00eb detyr\u00ebs s2i-web-app; kjo b\u00ebhet k\u00ebshtu:<\/p>\n
    # This resource is the result of running "npm run build",  the resulting built files will be located in \/opt\/app-root\/output\napiVersion: tekton.dev\/v1alpha1\nkind: PipelineResource\nmetadata:\n  name: built-web-application-image\nspec:\n  type: image\n  params:\n    - name: url\n      value: image-registry.openshift-image-registry.svc:5000\/webapp-pipeline\/built-web-application:latest\n<\/code><\/pre>\n
    \nK\u00ebtu, PipelineResource ka tipin image, dhe vlera e parametrave url tregon regjistrin e brendsh\u00ebm t\u00eb imazheve OpenShift, konkretisht at\u00eb q\u00eb ndodhet n\u00eb hap\u00ebsir\u00ebn e emrave webapp-pipeline. Mos harroni ta ndryshoni k\u00ebt\u00eb parametrin n\u00ebse po p\u00ebrdorni nj\u00eb hap\u00ebsir\u00eb tjet\u00ebr emri.<\/p>\n
    Dhe, p\u00ebrfundimisht, burimi i fundit q\u00eb do na nevojitet, gjithashtu do t\u00eb ket\u00eb tipin image dhe ky do t\u00eb jet\u00eb imazhi p\u00ebrfundimtar NGINX, i cili m\u00eb pas do t\u00eb p\u00ebrdoret gjat\u00eb implementimit:<\/p>\n
    # This resource is the image that will be just the static html, css, js files being run with nginx\napiVersion: tekton.dev\/v1alpha1\nkind: PipelineResource\nmetadata:\n  name: runtime-web-application-image\nspec:\n  type: image\n  params:\n    - name: url\n      value: image-registry.openshift-image-registry.svc:5000\/webapp-pipeline\/runtime-web-application:latest\n<\/code><\/pre>\n
    \nDhe p\u00ebrs\u00ebri, vini re se ky burim ruan imazhin n\u00eb regjistrin e brendsh\u00ebm OpenShift n\u00eb hap\u00ebsir\u00ebn e emrave webapp-pipeline.<\/p>\n
    P\u00ebr t\u00eb krijuar t\u00eb gjitha k\u00ebto burime nj\u00ebkoh\u00ebsisht, do t\u00eb p\u00ebrdorim komand\u00ebn create:<\/p>\n
    $ oc create -f https:\/\/raw.githubusercontent.com\/nodeshift\/webapp-pipeline-tutorial\/master\/resources\/resource.yaml\n<\/code><\/pre>\n
    \nMund t\u00eb verifikoni q\u00eb burimet jan\u00eb krijuar k\u00ebshtu:<\/p>\n
    $ tkn resource ls\n<\/code><\/pre>\n
    <\/p>\n
    Pipeline i konvejerit<\/h4>\n
    \nTani q\u00eb kemi t\u00eb gjitha p\u00ebrb\u00ebr\u00ebsit e nevojsh\u00ebm, do ta nd\u00ebrtrojm\u00eb konvejerin, duke e krijuar at\u00eb me komand\u00ebn e m\u00ebposhtme:<\/p>\n
    $ oc create -f https:\/\/raw.githubusercontent.com\/nodeshift\/webapp-pipeline-tutorial\/master\/pipelines\/build-and-deploy-react.yaml\n<\/code><\/pre>\n
    \nPor, para se ta ekzekutojm\u00eb k\u00ebt\u00eb komand\u00eb, le t\u00eb analizojm\u00eb k\u00ebta p\u00ebrb\u00ebr\u00ebs. I pari \u2013 \u00ebsht\u00eb emri:<\/p>\n
    apiVersion: tekton.dev\/v1alpha1\nkind: Pipeline\nmetadata:\n  name: build-and-deploy-react\n<\/code><\/pre>\n
    \nM\u00eb pas, n\u00eb seksionin spec shohim p\u00ebrcaktimin e burimeve q\u00eb krijuam m\u00eb par\u00eb:<\/p>\n
    spec:\n  burimet:\n    - emri: web-application-repo\n      lloji: git\n    - emri: built-web-application-image\n      lloji: image\n    - emri: runtime-web-application-image\n      lloji: image\n<\/code><\/pre>\n
    \nM\u00eb pas krijojm\u00eb detyrat q\u00eb do t\u00eb ekzekutoj\u00eb konvjeri yn\u00eb. E para q\u00eb duhet t\u00eb kryej\u00eb \u00ebsht\u00eb detyra q\u00eb e krijuam m\u00eb par\u00eb, s2i-web-app:<\/p>\n
    detyrat:\n    - emri: build-web-application\n      taskRef:\n        emri: s2i-web-app\n        lloji: ClusterTask\n<\/code><\/pre>\n
    \nKjo detyr\u00eb merr parametrat hyr\u00ebs (gir-burimi) dhe dal\u00ebs (burimi built-web-application-image). Ne gjithashtu ia japim nj\u00eb paramet\u00ebr t\u00eb ve\u00e7ant\u00eb q\u00eb t\u00eb mos verifikoj\u00eb TLS, pasi po p\u00ebrdorim certifikata t\u00eb vet\u00eb-nderuar:<\/p>\n
    resources:\n        inputs:\n          - name: source\n            resource: web-application-repo\n        outputs:\n          - name: image\n            resource: built-web-application-image\n      params:\n        - name: TLSVERIFY\n          value: \"false\"\n<\/code><\/pre>\n
    \nDetyra tjet\u00ebr \u00ebsht\u00eb pothuajse e nj\u00ebjt\u00eb, vet\u00ebm se k\u00ebtu thirret detyra tona klaster me em\u00ebr webapp-build-runtime:<\/p>\n
    emri: build-runtime-image\n    taskRef:\n      emri: webapp-build-runtime\n      lloji: ClusterTask\n<\/code><\/pre>\n
    \nAshtu si me detyr\u00ebn e m\u00ebparshme, ne transferojm\u00eb burimin, por tani kjo \u00ebsht\u00eb built-web-application-image (dalja nga detyra jon\u00eb e m\u00ebparshme). Dhe si dalje, p\u00ebrs\u00ebri specifikojm\u00eb imazhin. Duke qen\u00eb se kjo detyr\u00eb duhet t\u00eb ekzekutohet pas asaj paraprake, shtojm\u00eb fush\u00ebn runAfter:<\/p>\n
    resources:\n        inputs:\n          - name: image\n            resource: built-web-application-image\n        outputs:\n          - name: image\n            resource: runtime-web-application-image\n        params:\n        - name: TLSVERIFY\n          value: \"false\"\n      runAfter:\n        - build-web-application\n<\/code><\/pre>\n
    \nDy detyrat e ardhshme jan\u00eb p\u00ebrgjegj\u00ebse p\u00ebr aplikimin e skedar\u00ebve YAML p\u00ebr sh\u00ebrbimin, rrug\u00ebn dhe implementimin, t\u00eb cil\u00ebt jetojn\u00eb n\u00eb dosjen k8s t\u00eb aplikacionit ton\u00eb web, si dhe p\u00ebr t\u00eb p\u00ebrdit\u00ebsuar k\u00ebt\u00eb implementim kur krijohen imazhe t\u00eb reja. K\u00ebto dy detyra klasteri i kemi p\u00ebrcaktuar q\u00eb n\u00eb fillim t\u00eb artikullit.<\/p>\n
    Ekzekutimi i konvejerit<\/h4>\n
    \nPra, t\u00eb gjitha pjes\u00ebt e konveyor\u00ebve tan\u00eb jan\u00eb krijuar, dhe ne do ta ekzekutojm\u00eb at\u00eb me komand\u00ebn e m\u00ebposhtme:<\/p>\n
    $ tkn pipeline start build-and-deploy-react\n<\/code><\/pre>\n
    \nN\u00eb k\u00ebt\u00eb faz\u00eb, linja e komandave p\u00ebrdoret n\u00eb mod t\u00eb nd\u00ebrveprimit dhe duhet t\u00eb zgjidhni burimet p\u00ebrkat\u00ebse n\u00eb p\u00ebrgjigje t\u00eb \u00e7do k\u00ebrkese t\u00eb saj: p\u00ebr burimin git zgjidhni web-application-repo, pastaj p\u00ebr burimin e par\u00eb t\u00eb imazhit - built-web-application-image, dhe, n\u00eb fund, p\u00ebr burimin e dyt\u00eb t\u00eb imazhit - runtime-web-application-image:<\/p>\n
    ? Choose the git resource to use for web-application-repo: web-application-repo (https:\/\/github.com\/nodeshift-starters\/react-pipeline-example)\n? Choose the image resource to use for built-web-application-image: built-web-application-image (image-registry.openshift-image-registry.svc:5000\/webapp-pipeline\/built-web-\napplication:latest)\n? Choose the image resource to use for runtime-web-application-image: runtime-web-application-image (image-registry.openshift-image-registry.svc:5000\/webapp-pipeline\/runtim\ne-web-application:latest)\nPipelinerun started: build-and-deploy-react-run-4xwsr\n<\/code><\/pre>\n
    \nTani do t\u00eb kontrollojm\u00eb statusin e pipeline-it duke p\u00ebrdorur komand\u00ebn e m\u00ebposhtme:<\/p>\n
    $ tkn pipeline logs -f\n<\/code><\/pre>\n
    \nPasi t\u00eb nis\u00eb pipeline-i dhe aplikacioni t\u00eb jet\u00eb i instaluar, do ta k\u00ebrkojm\u00eb rrug\u00ebn e publikuar me komand\u00ebn e m\u00ebposhtme:<\/p>\n
    $ oc get route react-pipeline-example --template='http:\/\/{{.spec.host}}'\n<\/code><\/pre>\n
    \nP\u00ebr m\u00eb shum\u00eb vizibilitet, mund ta shikoni pipeline-n ton\u00eb n\u00eb modalitetin Developer t\u00eb konsol\u00ebs s\u00eb webit n\u00eb seksionin Pipelines<\/b>, ashtu si\u00e7 tregohet n\u00eb Fig. 1.<\/p>\n
    \"Aplikacione<\/p>\n
    Fig. 1. Pasqyra e pipeline-ve t\u00eb nisura.<\/i><\/p>\n
    Klikimi mbi pipeline-in e nisur tregon informacion shtes\u00eb, si\u00e7 tregohet n\u00eb Fig. 2.<\/p>\n
    \"Aplikacione<\/p>\n
    Fig. 2. Informacion shtes\u00eb rreth pipeline-it.<\/i><\/p>\n
    Pas informacionit shtes\u00eb, mund t\u00eb shikoni aplikacionet e nisura n\u00eb pamjen Topology<\/b>, si\u00e7 tregohet n\u00eb Fig. 3.<\/p>\n
    \"Aplikacione<\/p>\n
    Fig. 3. Pod-i i nisur.<\/i><\/p>\n
    Klikimi mbi rrethin n\u00eb k\u00ebndin e sip\u00ebrm t\u00eb djatht\u00eb t\u00eb ikon\u00ebs hap aplikacionin ton\u00eb, si\u00e7 tregohet n\u00eb Fig. 4.<\/p>\n
    \"Aplikacione<\/p>\n
    Fig. 4. Aplikacioni React i nisur.<\/i><\/p>\n
    P\u00ebrfundimi<\/h3>\n
    \nPra, ne treguam se si t\u00eb nisni n\u00eb OpenShift nj\u00eb server zhvillimi p\u00ebr aplikacionin tuaj dhe ta sinkronizoni at\u00eb me sistemin lokal t\u00eb skedave. Po ashtu, shqyrtuam se si t\u00eb imitojm\u00eb template-n e chained-build me ndihm\u00ebn e OpenShift Pipelines. T\u00eb gjitha kodet e shembujve nga ky artikull mund t\u00eb gjenden n\u00eb k\u00ebtu<\/a><\/noindex>.<\/p>\n
    Burime t\u00eb tjera (EN)<\/h3>\n
    <\/p>\n