{"id":87467,"date":"2020-07-08T13:42:11","date_gmt":"2020-07-08T11:42:11","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/rukovodstvo-dlya-nachinayushhih-sozdaem-devops-pajplajn"},"modified":"2020-07-08T13:42:11","modified_gmt":"2020-07-08T11:42:11","slug":"rukovodstvo-dlya-nachinayushhih-sozdaem-devops-pajplajn","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/rukovodstvo-dlya-nachinayushhih-sozdaem-devops-pajplajn","title":{"rendered":"Udh\u00ebzues p\u00ebr fillestar\u00ebt: krijimi i nj\u00eb pipeline DevOps","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

N\u00ebse jeni nj\u00eb fillestar n\u00eb DevOps, shikoni k\u00ebt\u00eb udh\u00ebzues p\u00ebr krijimin e tubacionit tuaj t\u00eb par\u00eb n\u00eb pes\u00eb hapa.<\/i><\/p>\n

\"Udh\u00ebzues<\/p>\n

DevOps \u00ebsht\u00eb b\u00ebr\u00eb zgjidhja standarde p\u00ebr t\u00eb rregulluar proceset e ngadalta, t\u00eb ndara ose t\u00eb pap\u00ebrshtatshme t\u00eb zhvillimit t\u00eb softuerit. Problemi \u00ebsht\u00eb se, n\u00ebse jeni nj\u00eb fillestar n\u00eb DevOps dhe nuk dini nga t\u00eb filloni, mund t'ju mungoj\u00eb kuptimi i k\u00ebtyre metodave. N\u00eb k\u00ebt\u00eb artikull do t\u00eb flasim p\u00ebr p\u00ebrcaktimin e tubacionit DevOps dhe do t\u00eb ofrojm\u00eb nj\u00eb udh\u00ebzim p\u00ebr krijimin e tij n\u00eb pes\u00eb hapa. Edhe pse ky udh\u00ebzues nuk \u00ebsht\u00eb p\u00ebrmbledh\u00ebs, duhet t\u00eb ju jap\u00eb nj\u00eb baz\u00eb p\u00ebr t\u00eb filluar rrug\u00ebtimin tuaj dhe p\u00ebr t\u00eb zgjeruar njohurit\u00eb tuaja n\u00eb t\u00eb ardhmen. Por le t\u00eb fillojm\u00eb me historin\u00eb.<\/p>\n

Udh\u00ebtimi im n\u00eb DevOps<\/h3>\n

\nN\u00eb t\u00eb kaluar\u00ebn punoja n\u00eb ekipin e cloud-it t\u00eb Citi Group, duke zhvilluar nj\u00eb aplikacion web Infrastructure-as-a-Service (IaaS) p\u00ebr menaxhimin e infrastruktur\u00ebs cloud t\u00eb Citi, por gjithmon\u00eb kam qen\u00eb i interesuar se si ta b\u00ebja procesin e zhvillimit m\u00eb efikas dhe t\u00eb sjell ndryshime kulturore pozitive n\u00eb ekipin e zhvilluesve. P\u00ebrgjigjen e gjeta n\u00eb nj\u00eb lib\u00ebr t\u00eb rekomanduar nga Greg Lavender, CTO i Citi p\u00ebr arkitektur\u00ebn dhe infrastruktur\u00ebn n\u00eb cloud. Libri quhej \"Projekti Feniks\"Projekti Feniks<\/a><\/noindex>\", dhe aty shpjegohen parimet e DevOps-it, duke u lexuar si nj\u00eb roman.<\/p>\n

N\u00eb tabel\u00ebn n\u00eb an\u00ebn e pasme t\u00eb librit tregohet se sa shpesh kompanit\u00eb e ndryshme dislokojn\u00eb sistemet e tyre n\u00eb nj\u00eb mjedis p\u00ebr l\u00ebshimin e versioneve:<\/p>\n

Amazon: 23,000 n\u00eb dit\u00eb
\nGoogle: 5,500 n\u00eb dit\u00eb
\nNetflix: 500 n\u00eb dit\u00eb
\nFacebook: Nj\u00eb her\u00eb n\u00eb dit\u00eb
\nTwitter: 3 her\u00eb n\u00eb jav\u00eb
\nKompanit\u00eb tipike: Nj\u00eb her\u00eb n\u00eb 9 muaj<\/p>\n

Si \u00ebsht\u00eb e mundur q\u00eb Amazon, Google dhe Netflix t\u00eb ken\u00eb k\u00ebto frekuenca? E gjitha sepse k\u00ebto kompani kan\u00eb menduar se si t\u00eb krijojn\u00eb nj\u00eb pipeline pothuajse t\u00eb p\u00ebrsosur DevOps.
\n<\/a><\/noindex>
\nIshimim \u00e7far\u00eb ka ndodhur me ne derisa nuk b\u00ebm\u00eb implementimin e DevOps n\u00eb Citi. At\u00ebher\u00eb, ekipi im kishte mjedise t\u00eb ndryshme, por vendosja n\u00eb serverin e zhvillimit ishte plot\u00ebsisht manuale. T\u00eb gjith\u00eb zhvilluesit kishin akses vet\u00ebm n\u00eb nj\u00eb server zhvillimi q\u00eb bazohej n\u00eb IBM WebSphere Application Server Community Edition. Problemi ishte se serveri fikej \u00e7do her\u00eb q\u00eb disa p\u00ebrdorues p\u00ebrpiqeshin t\u00eb b\u00ebnin vendosje n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, prandaj zhvilluesit duhet t\u00eb shpallin nj\u00ebri-tjetrit q\u00ebllimet e tyre, gj\u00eb q\u00eb ishte mjaft e dhimbshme. P\u00ebr m\u00eb tep\u00ebr, kishte probleme me mbulimin e ul\u00ebt t\u00eb testeve t\u00eb kodit, procese t\u00eb ngarkuara manuale dhe munges\u00ebn e mund\u00ebsis\u00eb p\u00ebr t\u00eb ndjekur vendosjen e kodit t\u00eb lidhur me nj\u00eb detyr\u00eb ose histori p\u00ebrdoruesi t\u00eb caktuar.<\/p>\n

E kuptova q\u00eb duhej t\u00eb b\u00ebja di\u00e7ka dhe gjeta nj\u00eb koleg me t\u00eb nj\u00ebjtin mendim. Ne vendos\u00ebm t\u00eb bashk\u00ebpunojm\u00eb p\u00ebr t\u00eb krijuar nj\u00eb konvjer\u00eb DevOps fillestar - ai vendosi nj\u00eb makin\u00eb virtuale dhe nj\u00eb server aplikacionesh Tomcat, nd\u00ebrsa un\u00eb punoja mbi Jenkins, integrova Atlassian Jira dhe BitBucket, si dhe punova mbi mbulimin e testeve t\u00eb kodit. Ky projekt an\u00ebsor ishte shum\u00eb i suksessh\u00ebm: ne automatizuam pothuajse plot\u00ebsisht shum\u00eb procese, arrit\u00ebm praktikisht 100% funksionalitet t\u00eb serverit tan\u00eb t\u00eb zhvillimit, siguruam monitorimin dhe p\u00ebrmir\u00ebsuam mbulimin e testeve t\u00eb kodit, si dhe shtuam mund\u00ebsin\u00eb p\u00ebr t\u00eb lidhur deg\u00ebt n\u00eb Git me detyrat n\u00eb Jira ose me shp\u00ebrndarjen. Shumica e mjeteve q\u00eb p\u00ebrdor\u00ebm p\u00ebr t\u00eb nd\u00ebrtuar konvjerin ton\u00eb DevOps ishin me burim t\u00eb hapur.<\/p>\n

Tani kuptoj sa i thjesht\u00eb ishte konvjeri yn\u00eb DevOps: ne nuk p\u00ebrdor\u00ebm zgjerime si Jenkins files ose Ansible. Megjithat\u00eb, ky konvjer i thjesht\u00eb funksionoi mir\u00eb, ndoshta fal\u00eb parimit t\u00eb Pareto (i njohur gjithashtu si rregulli 80\/20).<\/p>\n

Nj\u00eb hyrje e shkurt\u00ebr n\u00eb DevOps dhe konvjerin CI\/CD<\/h3>\n

\nN\u00ebse pyesni disa njer\u00ebz: \"\u00c7far\u00eb \u00ebsht\u00eb DevOps?\", ka shum\u00eb mund\u00ebsi q\u00eb t\u00eb merrni disa p\u00ebrgjigje t\u00eb ndryshme. DevOps, ashtu si Agile, ka evoluar p\u00ebr t\u00eb p\u00ebrfshir\u00eb shum\u00eb disiplina t\u00eb ndryshme, por shumica e njer\u00ebzve do t\u00eb bien dakord p\u00ebr disa gj\u00ebra: DevOps \u00ebsht\u00eb nj\u00eb praktik\u00eb e zhvillimit t\u00eb softuerit ose nj\u00eb cik\u00ebl jet\u00ebsor i zhvillimit t\u00eb softuerit (SDLC), me parimin qendror t\u00eb ndryshimit t\u00eb kultur\u00ebs, n\u00eb t\u00eb cil\u00ebn zhvilluesit dhe ata q\u00eb nuk jan\u00eb zhvillues ekzistojn\u00eb n\u00eb nj\u00eb mjedis ku:<\/p>\n

Operacionet q\u00eb m\u00eb par\u00eb b\u00ebheshin manualisht jan\u00eb automatizuar;
\n\u00c7do kush b\u00ebn at\u00eb q\u00eb di m\u00eb mir\u00eb;
\nNumri i implementimeve n\u00eb nj\u00eb periudh\u00eb t\u00eb caktuar kohore rritet; Rritet kapaciteti;
\nRritet fleksibiliteti i zhvillimit.<\/p>\n

Megjith\u00ebse disponimi i mjeteve t\u00eb duhura softuerike nuk \u00ebsht\u00eb e vetmja gj\u00eb e nevojshme p\u00ebr t\u00eb krijuar nj\u00eb ambient DevOps, disa mjete jan\u00eb thelb\u00ebsore. Mjeti ky\u00e7 \u00ebsht\u00eb integrimi dhe shp\u00ebrndarja e vazhdueshme (CI\/CD). N\u00eb k\u00ebt\u00eb konvej, ambientet kan\u00eb faza t\u00eb ndryshme (p.sh. DEV, INT, TST, QA, UAT, STG, PROD), shum\u00eb operacione jan\u00eb t\u00eb automatizuara, dhe zhvilluesit mund t\u00eb shkruajn\u00eb kod t\u00eb lart\u00eb cil\u00ebsie, t\u00eb arrijn\u00eb fleksibilitet n\u00eb zhvillim dhe nj\u00eb frekuenc\u00eb t\u00eb lart\u00eb shp\u00ebrndarjesh.<\/p>\n

Ky artikull p\u00ebrshkruan nj\u00eb qasje me pes\u00eb hapa p\u00ebr t\u00eb nd\u00ebrtuar nj\u00eb konvej DevOps, si ai i ilustruar n\u00eb diagramin e m\u00ebposht\u00ebm, duke p\u00ebrdorur mjete me kod t\u00eb hapur.<\/p>\n

Hapi 1: Metodat CI\/CD<\/h3>\n

\nGj\u00ebja e par\u00eb q\u00eb ju nevojitet \u00ebsht\u00eb nj\u00eb mjet p\u00ebr CI\/CD. Jenkins, nj\u00eb mjet me kod t\u00eb hapur, i nd\u00ebrtuar n\u00eb Java dhe i shp\u00ebrndar\u00eb n\u00ebn licenc\u00ebn MIT, \u00ebsht\u00eb mjeti q\u00eb ka popullarizuar drejtimin DevOps dhe \u00ebsht\u00eb b\u00ebr\u00eb standardi de facto.<\/p>\n

Pra ndaj, \u00e7far\u00eb \u00ebsht\u00eb Jenkins? Mendoni p\u00ebr t\u00eb si nj\u00eb pult magjik universali q\u00eb mund t\u00eb flas\u00eb me sh\u00ebrbime dhe mjete t\u00eb ndryshme dhe t'i organizoj\u00eb ato. Nj\u00eb mjet CI\/CD si Jenkins \u00ebsht\u00eb i padobish\u00ebm vet\u00eb, por b\u00ebhet m\u00eb i fuqish\u00ebm nd\u00ebrsa lidhet me mjete dhe sh\u00ebrbime t\u00eb ndryshme.<\/p>\n

Jenkins \u00ebsht\u00eb vet\u00ebm nj\u00eb nga shum\u00eb mjetet me kod t\u00eb hapur p\u00ebr CI\/CD q\u00eb mund t\u00eb p\u00ebrdorni p\u00ebr t\u00eb nd\u00ebrtuar nj\u00eb pipeline DevOps.<\/p>\n

Jenkins: Creative Commons dhe MIT
\nTravis CI: MIT
\nCruiseControl: BSD
\nBuildbot: GPL
\nApache Gump: Apache 2.0
\nCabie: GNU<\/p>\n

Ja se si duken proceset DevOps me nj\u00eb mjet CI\/CD:<\/p>\n

\"Udh\u00ebzues<\/p>\n

Keni nj\u00eb mjet CI\/CD q\u00eb punon n\u00eb localhost tuaj, por p\u00ebr momentin nuk mund t\u00eb b\u00ebni shum\u00eb. Le t\u00eb kalojm\u00eb n\u00eb faz\u00ebn tjet\u00ebr t\u00eb udh\u00ebtimit n\u00eb bot\u00ebn DevOps.<\/p>\n

Hapi 2: Menaxhimi i sistemeve t\u00eb kontrollit t\u00eb burimeve<\/h3>\n

\nM\u00ebnyra m\u00eb e mir\u00eb (dhe ndoshta m\u00eb e thjesht\u00eb) p\u00ebr t\u00eb kontrolluar n\u00ebse mjeti juaj CI\/CD mund t\u00eb krijoj\u00eb magji \u2013 \u00ebsht\u00eb integrimi me mjetin e kontrollit t\u00eb kodit burimor (SCM). Pse keni nevoj\u00eb p\u00ebr kontroll mbi kodin burimor? Imagjinoni se po zhvilloni nj\u00eb aplikacion. Sa her\u00eb q\u00eb krijoni nj\u00eb aplikacion, ju programoni, dhe nuk ka r\u00ebnd\u00ebsi n\u00ebse po p\u00ebrdorni Java, Python, C++, Go, Ruby, JavaScript, apo ndonj\u00eb nga gjuh\u00ebt e shumta t\u00eb programimit. Kodi q\u00eb shkruani quhet kod burimor. N\u00eb fillim, ve\u00e7an\u00ebrisht kur punoni vet\u00ebm, ka shum\u00eb gjasa q\u00eb t\u00eb gjitha t\u2019i vendosni n\u00eb nj\u00eb direktore lokale. Por kur projekti b\u00ebhet m\u00eb i madh dhe ftoni njer\u00ebz t\u00eb tjer\u00eb p\u00ebr t\u00eb bashk\u00ebpunuar, ju nevojitet nj\u00eb m\u00ebnyr\u00eb p\u00ebr t\u00eb parandaluar konfliktet gjat\u00eb ndarjes efektive t\u00eb modifikimeve. Ju gjithashtu keni nevoj\u00eb p\u00ebr nj\u00eb m\u00ebnyr\u00eb p\u00ebr t\u00eb rikuperuar versionet e m\u00ebparshme, sepse krijimi i kopjeve rezerv\u00eb dhe kopjimi\/ngjitja n\u00eb to tashm\u00eb \u00ebsht\u00eb b\u00ebr\u00eb i tejkaluar. Ju (dhe shok\u00ebt tuaj n\u00eb ekip) ju nevojitet di\u00e7ka m\u00eb t\u00eb mir\u00eb.<\/p>\n

K\u00ebtu, mjetet p\u00ebr kontrollin e kodit burimor b\u00ebhen praktikisht t\u00eb domosdoshme. Ky mjet ruan kodin tuaj n\u00eb depo, mbahet ecuria e versioneve dhe koordinon pun\u00ebn e pjes\u00ebmarr\u00ebsve n\u00eb projekt.<\/p>\n

Megjith\u00ebse ekzistojn\u00eb shum\u00eb mjete p\u00ebr kontrollin e kodit burimor, Git \u00ebsht\u00eb standardi, dhe kjo \u00ebsht\u00eb e v\u00ebrtet\u00eb. Un\u00eb rekomandoj me ngulm p\u00ebrdorimin e Git, pavar\u00ebsisht se ka edhe mund\u00ebsi t\u00eb tjera me kod burimor t\u00eb hapur.<\/p>\n

Git: GPLv2 dhe LGPL v2.1
\nSubversion: Apache 2.0
\nSistemi i Versioneve t\u00eb P\u00ebrs\u00ebritura (CVS): GNU
\nVesta: LGPL
\nMercurial: GNU GPL v2+<\/p>\n

K\u00ebshtu duket nj\u00eb pipeline DevOps me p\u00ebrfshirjen e mjeteve p\u00ebr kontrollin e kodit burimor.<\/p>\n

\"Udh\u00ebzues<\/p>\n

Nj\u00eb mjet CI\/CD mund t\u00eb automatizoj\u00eb proceset e verifikimit, marrjes s\u00eb kodit burimor dhe bashk\u00ebpunimit mes an\u00ebtar\u00ebve. Jo keq? Por si ta kthejm\u00eb k\u00ebt\u00eb n\u00eb nj\u00eb aplikacion funksional q\u00eb miliarda njer\u00ebz mund ta p\u00ebrdorin dhe vler\u00ebsojn\u00eb?<\/p>\n

Hapi 3: Krijimi i nj\u00eb mjeti p\u00ebr automatizimin e nd\u00ebrtimit<\/h3>\n

\nSuper! Ju mund t\u00eb kontrolloni kodin dhe t\u00eb b\u00ebni ndryshime n\u00eb sistemin e kontrollit t\u00eb burimeve, si dhe t\u00eb ftoni miqt\u00eb tuaj t\u00eb bashk\u00ebpunojn\u00eb n\u00eb zhvillim. Por ende nuk keni krijuar nj\u00eb aplikacion. P\u00ebr t\u00eb b\u00ebr\u00eb nj\u00eb aplikacion web, duhet t\u00eb kompilohet dhe t\u00eb paketoj\u00eb n\u00eb nj\u00eb format t\u00eb shp\u00ebrndarjes ose t\u00eb startohet si nj\u00eb sked\u00eb ekzekutiv. (Kujtoni se nj\u00eb gjuh\u00eb programimi interpretuese si JavaScript ose PHP nuk ka nevoj\u00eb p\u00ebr kompilim).<\/p>\n

P\u00ebrdorni nj\u00eb mjet p\u00ebr automatizimin e nd\u00ebrtimit. Pavar\u00ebsisht se cili mjet p\u00ebr automatizimin e nd\u00ebrtimit vendosni t\u00eb p\u00ebrdorni, t\u00eb gjith\u00eb ndjekin nj\u00eb q\u00ebllim t\u00eb nj\u00ebjt\u00eb: t\u00eb mbledhin kodin burimor n\u00eb nj\u00eb format t\u00eb d\u00ebshiruar dhe t\u00eb automatizojn\u00eb detyr\u00ebn e pastrimit, kompilimit, testimit dhe shp\u00ebrndarjes n\u00eb nj\u00eb mjedis t\u00eb caktuar. Mjetet p\u00ebr nd\u00ebrtim do t\u00eb ndryshojn\u00eb n\u00eb var\u00ebsi t\u00eb gjuh\u00ebs suaj t\u00eb programimit, por k\u00ebtu jan\u00eb disa mund\u00ebsi t\u00eb zakonshme me burim t\u00eb hapur.<\/p>\n

Emri
\nLicenca
\nGjuha e programimit<\/p>\n

Maven
\nApache 2.0
\n Java<\/p>\n

Ant
\nApache 2.0
\nJava<\/p>\n

Gradle
\nApache 2.0
\nJava<\/p>\n

Bazel
\nApache 2.0
\nJava<\/p>\n

Make
\nGNU
\nN\/A<\/p>\n

Grunt
\nMIT
\nJavaScript<\/p>\n

Gulp
\nMIT
\nJavaScript<\/p>\n

Buildr
\nApache
\nRuby<\/p>\n

Rake
\nMIT
\nRuby<\/p>\n

A-A-P
\nGNU
\nPython<\/p>\n

SCons
\nMIT
\nPython<\/p>\n

BitBake
\nGPLv2
\nPython<\/p>\n

Cake
\nMIT
\nC#<\/p>\n

ASDF
\nExpat (MIT)
\nLISP<\/p>\n

Cabal
\nBSD
\nHaskell<\/p>\n

Shum\u00eb mir\u00eb! Ju mund t\u00eb vendosni skedar\u00ebt e konfigurimit t\u00eb instrumentit t\u00eb automatizimit t\u00eb nd\u00ebrtimit n\u00eb sistemin e menaxhimit t\u00eb burimeve dhe t'i lejoni mjetit tuaj CI\/CD t\u00eb bashkoj\u00eb gjith\u00e7ka.<\/p>\n

\"Udh\u00ebzues<\/p>\n

T\u00eb gjith\u00eb jan\u00eb mir\u00eb, apo jo? Por ku do ta vendosni aplikacionin tuaj?<\/p>\n

Hapi 4: Serveri p\u00ebr aplikacione web<\/h3>\n

\nP\u00ebr momentin, keni nj\u00eb skedh t\u00eb paketuar, i cili mund t\u00eb jet\u00eb ose ekzekutues ose instalues. P\u00ebr t\u00eb b\u00ebr\u00eb q\u00eb \u00e7do aplikacion t\u00eb jet\u00eb v\u00ebrtet i dobish\u00ebm, ai duhet t\u00eb ofroj\u00eb ndonj\u00eb sh\u00ebrbim ose nd\u00ebrfaqe, por ju nevojitet nj\u00eb kontejner p\u00ebr t\u00eb pritur aplikacionin tuaj.<\/p>\n

Serveri p\u00ebr aplikacione web \u00ebsht\u00eb pik\u00ebrisht nj\u00eb kontejner i till\u00eb. Serveri siguron nj\u00eb mjedis ku mund t\u00eb p\u00ebrcaktohet logjika e paket\u00ebs q\u00eb po zbatohet. Gjithashtu, serveri ofron nd\u00ebrfaqe dhe ofron sh\u00ebrbime web, duke hapur socket-e p\u00ebr bot\u00ebn e jashtme. Ju nevojitet nj\u00eb server HTTP, si dhe ndonj\u00eb mjedis (p\u00ebr shembull, nj\u00eb makin\u00eb virtuale) p\u00ebr ta instaluar at\u00eb. Nd\u00ebrkoh\u00eb, le t\u00eb supozojm\u00eb q\u00eb ju do t\u00eb m\u00ebsoni m\u00eb shum\u00eb p\u00ebr k\u00ebt\u00eb m\u00eb von\u00eb (pavar\u00ebsisht se un\u00eb do t\u00eb flas p\u00ebr kontejner\u00ebt m\u00eb posht\u00eb).<\/p>\n

Ekzistojn\u00eb disa server\u00eb p\u00ebr aplikacione web me kod t\u00eb hapur.<\/p>\n

Emri
\nLicenca
\nGjuha e programimit<\/p>\n

Tomcat
\nApache 2.0
\nJava<\/p>\n

Jetty
\nApache 2.0
\nJava<\/p>\n

WildFly
\nGNU Lesser Public
\nJava<\/p>\n

GlassFish
\nCDDL & GNU Less Public
\nJava<\/p>\n

Django
\nLicenca BSD me 3 Klauzola
\nPython<\/p>\n

Tornado
\nApache 2.0
\nPython<\/p>\n

Gunicorn
\nMIT
\nPython<\/p>\n

Python
\nMIT
\nPython<\/p>\n

Rails
\nMIT
\nRuby<\/p>\n

Node.js
\nMIT
\nJavascript<\/p>\n

DevOps pipeline-i juaj pothuajse \u00ebsht\u00eb gati p\u00ebr t'u p\u00ebrdorur. Pun\u00eb e mrekullueshme!<\/p>\n

\"Udh\u00ebzues<\/p>\n

Megjith\u00ebse mund t\u00eb ndaloni k\u00ebtu dhe t\u00eb angazhoheni n\u00eb integrim vet\u00eb, cil\u00ebsia e kodit \u00ebsht\u00eb nj\u00eb \u00e7\u00ebshtje e r\u00ebnd\u00ebsishme p\u00ebr zhvilluesit e aplikacioneve dhe duhet t\u2019i kushtohet v\u00ebmendje.<\/p>\n

Hapi 5: Mbulimi i testimit t\u00eb kodit<\/h3>\n

\nImplementimi i testeve mund t\u00eb jet\u00eb nj\u00eb k\u00ebrkes\u00eb tjet\u00ebr voluminoze, por zhvilluesit duhet t\u00eb kapin \u00e7far\u00ebdo gabimesh n\u00eb aplikacion n\u00eb nj\u00eb faz\u00eb t\u00eb hershme dhe t\u00eb p\u00ebrmir\u00ebsojn\u00eb cil\u00ebsin\u00eb e kodit p\u00ebr t\u00eb siguruar k\u00ebnaq\u00ebsin\u00eb e p\u00ebrdoruesve p\u00ebrfundimtar\u00eb. Me fat, ka shum\u00eb mjete me kod t\u00eb hapur p\u00ebr t\u00eb testuar kodin tuaj dhe p\u00ebr t\u00eb formuar rekomandime p\u00ebr p\u00ebrmir\u00ebsimin e cil\u00ebsis\u00eb s\u00eb tij. Akoma m\u00eb mir\u00eb \u00ebsht\u00eb se shumica e mjeteve CI\/CD mund t\u00eb lidhen me k\u00ebto mjete dhe t\u00eb automatizojn\u00eb procesin.<\/p>\n

Testimi i kodit p\u00ebrb\u00ebhet nga dy pjes\u00eb: kornizat p\u00ebr testimin e kodit, t\u00eb cilat ndihmojn\u00eb n\u00eb shk writing dhe ekzekutimin e testeve, si dhe mjetet p\u00ebr formimin e sugjerimeve, q\u00eb ndihmojn\u00eb n\u00eb p\u00ebrmir\u00ebsimin e cil\u00ebsis\u00eb s\u00eb kodit.<\/p>\n

Sistemet e testimit t\u00eb kodit<\/b><\/p>\n

Emri
\nLicenca
\nGjuha e programimit<\/p>\n

JUnit
\nLicenca Publike Eclipse
\nJava<\/p>\n

EasyMock
\nApache
\nJava<\/p>\n

Mockito
\nMIT
\nJava<\/p>\n

PowerMock
\nApache 2.0
\nJava<\/p>\n

Pytest
\n MIT
\nPython<\/p>\n

Hypothesis
\nMozilla
\nPython<\/p>\n

Tox
\nMIT
\nPython<\/p>\n

Sistemet e rekomandimeve p\u00ebr p\u00ebrmir\u00ebsimin e kodit<\/b><\/p>\n

Emri
\nLicenca
\nGjuha e programimit<\/p>\n

Cobertura
\nGNU
\nJava<\/p>\n

CodeCover
\nLicenca Publike Eclipse (EPL)
\nJava<\/p>\n

Coverage.py
\n Apache 2.0
\nPython<\/p>\n

Emma
\nLicenca e P\u00ebrbashk\u00ebt Publike
\nJava<\/p>\n

JaCoCo
\n Licenca Publike Eclipse
\nJava<\/p>\n

Hypothesis
\n Mozilla
\nPython<\/p>\n

Tox
\nMIT
\nPython<\/p>\n

Jasmine
\nMIT
\nJavaScript<\/p>\n

Karma
\nMIT
\nJavaScript<\/p>\n

Mocha
\n MIT
\nJavaScript<\/p>\n

Jest
\nMIT
\nJavaScript<\/p>\n

Kujdes: shumica e mjeteve dhe strukturave t\u00eb p\u00ebrmendura m\u00eb sip\u00ebr jan\u00eb shkruar p\u00ebr Java, Python dhe JavaScript, nd\u00ebrsa C++ dhe C# jan\u00eb gjuh\u00eb programimi t\u00eb pronarit (nd\u00ebrsa GCC ka kod burimor t\u00eb hapur).<\/p>\n

Tani q\u00eb keni implementuar mjetet e mbulimit t\u00eb kodit me teste, pipeline juaj DevOps duhet t\u00eb duket si diagrami q\u00eb u shfaq n\u00eb fillim t\u00eb k\u00ebtij udh\u00ebzuesi.<\/p>\n

Hapat shtes\u00eb<\/h3>\n

\nKontejner\u00ebt<\/b><\/p>\n

Si\u00e7 e thash\u00eb m\u00eb par\u00eb, mund t\u00eb hostoni serverin tuaj n\u00eb nj\u00eb makin\u00eb virtuale ose server, por kontejner\u00ebt jan\u00eb nj\u00eb zgjidhje popullore.<\/p>\n

\u00c7far\u00eb jan\u00eb kontejner\u00ebt? Shpjegimi i shkurt\u00ebr \u00ebsht\u00eb se nj\u00eb makin\u00eb virtuale k\u00ebrkon nj\u00eb sasi t\u00eb madhe memorie t\u00eb sistemit operativ, m\u00eb shum\u00eb se madh\u00ebsia e aplikacionit, nd\u00ebrsa nj\u00eb kontejner ka nevoj\u00eb vet\u00ebm p\u00ebr disa biblioteka dhe konfigurime p\u00ebr t\u00eb ekzekutuar aplikacionin. Natyrisht, nj\u00eb makin\u00eb virtuale ka ende fusha t\u00eb r\u00ebnd\u00ebsishme p\u00ebrdorimi, por kontejneri \u00ebsht\u00eb nj\u00eb zgjidhje e leht\u00eb p\u00ebr hostimin e aplikacionit, p\u00ebrfshir\u00eb serverin e aplikacioneve.<\/p>\n

Megjith\u00ebse ka dhe opsione t\u00eb tjera kontejner\u00ebsh, m\u00eb t\u00eb popullarizuarit jan\u00eb Docker dhe Kubernetes.<\/p>\n

Docker: Apache 2.0
\nKubernetes: Apache 2.0<\/p>\n

Mjetet e automatizimit nd\u00ebrmjet\u00ebs<\/b><\/p>\n

Pipeline yn\u00eb DevOps \u00ebsht\u00eb kryesisht e orientuar drejt krijimit dhe shp\u00ebrndarjes s\u00eb aplikacioneve, por ka shum\u00eb gj\u00ebra t\u00eb tjera q\u00eb mund t\u00eb b\u00ebhen me mjete DevOps. Nj\u00ebra prej tyre \u00ebsht\u00eb p\u00ebrdorimi i mjeteve Infrastructure as Code (IaC), t\u00eb njohura gjithashtu si mjete nd\u00ebrmjet\u00ebsimi t\u00eb automatizimit. K\u00ebto mjete ndihmojn\u00eb n\u00eb automatizimin e instalimit, menaxhimit dhe detyrave t\u00eb tjera p\u00ebr programin nd\u00ebrmjet\u00ebs. P\u00ebr shembull, nj\u00eb mjet automatizimi mund t\u00eb nxjerr\u00eb aplikacione si server\u00eb p\u00ebr aplikacione web, baza t\u00eb dh\u00ebnash dhe mjete monitorimi, me konfigurime t\u00eb sakta dhe t'i shp\u00ebrndaj\u00eb ato n\u00eb serverin e aplikacioneve.<\/p>\n

Ja disa mjete nd\u00ebrmjet\u00ebsimi t\u00eb automatizimit me burim t\u00eb hapur:<\/p>\n

Ansible: GNU Public
\nSaltStack: Apache 2.0
\nChef: Apache 2.0
\nPuppet: Apache ose GPL<\/p>\n

\"Udh\u00ebzues<\/p>\n

M\u00ebsoni m\u00eb shum\u00eb se si t\u00eb merrni nj\u00eb profesion t\u00eb k\u00ebrkuar nga zero ose Level Up n\u00eb aft\u00ebsi dhe pag\u00eb, duke ndjekur kurse online me pages\u00eb n\u00eb SkillFactory:<\/p>\n