Runner (Ko\u015fucu):<\/strong> \u0130\u015fleri fiziksel veya sanal makinelerde y\u00fcr\u00fcten arac\u0131d\u0131r. GitLab sunucusu, Runner’lara i\u015f atar ve Runner’lar da bu i\u015fleri kendi ortamlar\u0131nda \u00e7al\u0131\u015ft\u0131r\u0131r. Payla\u015f\u0131ml\u0131 Runner’lar veya kendi \u00f6zel Runner’lar\u0131n\u0131z\u0131 kullanabilirsiniz.<\/li>\n<\/ul>\nBu bile\u015fenlerin entegre ve esnek yap\u0131s\u0131 sayesinde, GitLab CI\/CD yaz\u0131l\u0131m geli\u015ftirme s\u00fcre\u00e7lerinizi daha verimli, \u015feffaf ve g\u00fcvenilir hale getirir. Hata bulma s\u00fcrelerini k\u0131salt\u0131r, \u00fcr\u00fcn kalitesini art\u0131r\u0131r ve yeni \u00f6zellikleri kullan\u0131c\u0131lara ula\u015ft\u0131rma h\u0131z\u0131n\u0131z\u0131 \u00f6nemli \u00f6l\u00e7\u00fcde art\u0131r\u0131r. K\u0131sacas\u0131, modern DevOps pratiklerini benimsemek isteyen her ekip i\u00e7in GitLab CI\/CD, vazge\u00e7ilmez bir ara\u00e7t\u0131r.<\/p>\n
\u0130lk GitLab CI\/CD Pipeline’\u0131n\u0131z\u0131 Nas\u0131l Olu\u015fturursunuz? (.gitlab-ci.yml Anatomisi)<\/h2>\n
GitLab CI\/CD’nin kalbi, projenizin k\u00f6k dizininde bulunan .gitlab-ci.yml<\/code> adl\u0131 yap\u0131land\u0131rma dosyas\u0131d\u0131r. Bu YAML dosyas\u0131, pipeline’\u0131n\u0131z\u0131n nas\u0131l \u00e7al\u0131\u015faca\u011f\u0131n\u0131, hangi a\u015famalardan ge\u00e7ece\u011fini ve her a\u015famada hangi i\u015flerin (job) y\u00fcr\u00fct\u00fclece\u011fini tan\u0131mlar. Bu dosya sayesinde, t\u00fcm CI\/CD s\u00fcrecinizi kod olarak ifade edebilir ve s\u00fcr\u00fcm kontrol\u00fc alt\u0131nda tutabilirsiniz. Bu b\u00f6l\u00fcm, temel bir .gitlab-ci.yml<\/code> dosyas\u0131n\u0131n anatomisini a\u00e7\u0131klayacak ve ilk pipeline’\u0131n\u0131z\u0131 olu\u015fturman\u0131z i\u00e7in ad\u0131m ad\u0131m bir rehber sunacakt\u0131r.<\/p>\nTemel Yap\u0131 Ta\u015flar\u0131: Stages, Jobs ve Script Komutlar\u0131<\/h3>\n
Bir .gitlab-ci.yml<\/code> dosyas\u0131 genellikle stages<\/code> anahtar kelimesiyle ba\u015flar. Bu, pipeline’\u0131n\u0131z\u0131n mant\u0131ksal a\u015famalar\u0131n\u0131 tan\u0131mlar. \u00d6rne\u011fin, tipik bir web uygulamas\u0131 i\u00e7in build<\/code>, test<\/code> ve deploy<\/code> gibi a\u015famalar\u0131n\u0131z olabilir. A\u015famalardaki her bir i\u015f (job), bu a\u015famalar\u0131n s\u0131ras\u0131na g\u00f6re y\u00fcr\u00fct\u00fcl\u00fcr. Ayn\u0131 a\u015fama i\u00e7indeki i\u015fler paralel olarak \u00e7al\u0131\u015ft\u0131r\u0131labilirken, farkl\u0131 a\u015famalar birbirini takip eder ve \u00f6nceki a\u015faman\u0131n ba\u015far\u0131l\u0131 bir \u015fekilde tamamlanmas\u0131n\u0131 bekler.<\/p>\nHer bir i\u015f, kendi ad\u0131 alt\u0131nda tan\u0131mlan\u0131r ve en az bir script<\/code> anahtar kelimesi i\u00e7ermelidir. script<\/code> anahtar kelimesi, bu i\u015fin GitLab Runner taraf\u0131ndan y\u00fcr\u00fct\u00fclecek komutlar\u0131n\u0131 listeler. Bu komutlar, genellikle ba\u011f\u0131ml\u0131l\u0131klar\u0131 y\u00fckleme, kodu derleme, testleri \u00e7al\u0131\u015ft\u0131rma veya uygulamay\u0131 bir sunucuya da\u011f\u0131tma gibi g\u00f6revleri i\u00e7erir. \u0130\u015fte basit bir .gitlab-ci.yml<\/code> dosyas\u0131n\u0131n g\u00f6r\u00fcn\u00fcm\u00fc:<\/p>\n\n# .gitlab-ci.yml dosyas\u0131n\u0131n ba\u015flang\u0131c\u0131\n\n# Pipeline'\u0131m\u0131z\u0131n a\u015famalar\u0131n\u0131 tan\u0131ml\u0131yoruz.\n# A\u015famalardaki i\u015fler paralel \u00e7al\u0131\u015f\u0131rken, a\u015famalar s\u0131rayla \u00e7al\u0131\u015f\u0131r.\nstages:\n - build\n - test\n - deploy\n\n# 'build_job' ad\u0131nda bir i\u015f tan\u0131ml\u0131yoruz.\n# Bu i\u015f 'build' a\u015famas\u0131nda \u00e7al\u0131\u015facak.\nbuild_job:\n stage: build\n # Bu i\u015f i\u00e7in bir Docker imaj\u0131 belirliyoruz. Runner bu imaj\u0131 kullanarak ortam\u0131 haz\u0131rlar.\n image: node:16-alpine\n script:\n - echo \"Uygulama olu\u015fturuluyor...\"\n - npm install\n - npm run build\n # Bu i\u015fin \u00e7\u0131kt\u0131s\u0131 olan 'build' klas\u00f6r\u00fcn\u00fc bir sonraki a\u015famalara aktar\u0131yoruz.\n artifacts:\n paths:\n - build\/\n expire_in: 1 day # \u00dcretilen dosyalar\u0131n ne kadar s\u00fcre saklanaca\u011f\u0131n\u0131 belirtir\n\n# 'test_job' ad\u0131nda bir i\u015f tan\u0131ml\u0131yoruz.\n# Bu i\u015f 'test' a\u015famas\u0131nda \u00e7al\u0131\u015facak.\ntest_job:\n stage: test\n image: node:16-alpine\n script:\n - echo \"Testler \u00e7al\u0131\u015ft\u0131r\u0131l\u0131yor...\"\n - npm install # \u00d6nceki a\u015famadan gelen ba\u011f\u0131ml\u0131l\u0131klar i\u00e7in gerekebilir veya cache kullan\u0131labilir.\n - npm test\n # 'build' a\u015famas\u0131ndan gelen artefaktlar\u0131 (build klas\u00f6r\u00fc) bu i\u015fe indiriyoruz.\n needs:\n - build_job\n\n# 'deploy_job' ad\u0131nda bir i\u015f tan\u0131ml\u0131yoruz.\n# Bu i\u015f 'deploy' a\u015famas\u0131nda \u00e7al\u0131\u015facak.\n# Bu i\u015fin sadece 'main' branch'ine yap\u0131lan push'larda \u00e7al\u0131\u015fmas\u0131n\u0131 sa\u011fl\u0131yoruz.\ndeploy_job:\n stage: deploy\n image: alpine\/git # Da\u011f\u0131t\u0131m i\u00e7in basit bir Alpine Linux ve Git i\u00e7eren imaj\n script:\n - echo \"Uygulama da\u011f\u0131t\u0131l\u0131yor...\"\n - cp -r build\/ \/var\/www\/html\/ # \u00d6rnek bir da\u011f\u0131t\u0131m komutu\n - echo \"Uygulama ba\u015far\u0131yla da\u011f\u0131t\u0131ld\u0131!\"\n # Sadece 'main' branch'inde de\u011fi\u015fiklik oldu\u011funda bu i\u015fi \u00e7al\u0131\u015ft\u0131r.\n rules:\n - if: $CI_COMMIT_BRANCH == \"main\"\n # \u00d6nceki a\u015famadan gelen artefaktlar\u0131 (build klas\u00f6r\u00fc) bu i\u015fe indiriyoruz.\n needs:\n - test_job\n <\/pre>\n<\/code><\/p>\n
Yukar\u0131daki \u00f6rnekte:<\/p>\n
\nstages<\/code>: build<\/code>, test<\/code> ve deploy<\/code> a\u015famalar\u0131n\u0131 tan\u0131mlar. Bunlar s\u0131ras\u0131yla \u00e7al\u0131\u015facakt\u0131r.<\/li>\nbuild_job<\/code>: build<\/code> a\u015famas\u0131nda \u00e7al\u0131\u015fan bir i\u015f. node:16-alpine<\/code> Docker imaj\u0131n\u0131 kullanarak ba\u011f\u0131ml\u0131l\u0131klar\u0131 kurar (npm install<\/code>) ve uygulamay\u0131 derler (npm run build<\/code>). artifacts<\/code> anahtar kelimesi ile derlenmi\u015f dosyalar\u0131n (build\/<\/code> klas\u00f6r\u00fc) saklanmas\u0131n\u0131 ve bir sonraki a\u015famalarda kullan\u0131labilmesini sa\u011flar.<\/li>\ntest_job<\/code>: test<\/code> a\u015famas\u0131nda \u00e7al\u0131\u015fan bir i\u015f. Yine node:16-alpine<\/code> imaj\u0131n\u0131 kullan\u0131r ve npm test<\/code> komutuyla testleri \u00e7al\u0131\u015ft\u0131r\u0131r. needs: ['build_job']<\/code> ifadesi, bu i\u015fin build_job<\/code>'\u0131n ba\u015far\u0131l\u0131 bir \u015fekilde tamamlanmas\u0131n\u0131 bekledi\u011fini ve onun artefaktlar\u0131na ihtiya\u00e7 duydu\u011funu belirtir.<\/li>\ndeploy_job<\/code>: deploy<\/code> a\u015famas\u0131nda \u00e7al\u0131\u015fan bir i\u015f. rules<\/code> anahtar kelimesi ile sadece main<\/code> branch'ine yap\u0131lan push'larda \u00e7al\u0131\u015facak \u015fekilde ko\u015fulland\u0131r\u0131lm\u0131\u015ft\u0131r. Bu i\u015f, test_job<\/code>'dan sonra \u00e7al\u0131\u015f\u0131r ve \u00f6rnek bir da\u011f\u0131t\u0131m komutu i\u00e7erir.<\/li>\n<\/ul>\nimage<\/code>, before_script<\/code>, after_script<\/code> ve variables<\/code><\/h3>\nGitLab CI\/CD, pipeline'lar\u0131n\u0131z\u0131 daha g\u00fc\u00e7l\u00fc ve esnek hale getirecek bir\u00e7ok ek anahtar kelime sunar:<\/p>\n
\nimage<\/code>: Her i\u015fin hangi Docker imaj\u0131 i\u00e7inde \u00e7al\u0131\u015faca\u011f\u0131n\u0131 belirler. Bu, i\u015fin y\u00fcr\u00fct\u00fclece\u011fi ortam\u0131 standardize etmenizi sa\u011flar. Global olarak veya i\u015f baz\u0131nda tan\u0131mlanabilir.<\/li>\nbefore_script<\/code>: Her i\u015fin script<\/code> b\u00f6l\u00fcm\u00fcnden \u00f6nce \u00e7al\u0131\u015facak komutlar\u0131 tan\u0131mlar. Genellikle ba\u011f\u0131ml\u0131l\u0131k kurulumlar\u0131 veya genel yap\u0131land\u0131rmalar i\u00e7in kullan\u0131l\u0131r.<\/li>\nafter_script<\/code>: Her i\u015fin script<\/code> b\u00f6l\u00fcm\u00fcnden sonra (ba\u015far\u0131l\u0131 veya ba\u015far\u0131s\u0131z olmas\u0131na bak\u0131lmaks\u0131z\u0131n) \u00e7al\u0131\u015facak komutlar\u0131 tan\u0131mlar. Temizlik veya raporlama i\u00e7in kullan\u0131labilir.<\/li>\nvariables<\/code>: Pipeline genelinde veya belirli bir i\u015f i\u00e7in kullan\u0131labilecek \u00f6zel de\u011fi\u015fkenleri tan\u0131mlar. Hassas bilgiler i\u00e7in GitLab UI \u00fczerinden \"CI\/CD Variables\" kullan\u0131lmas\u0131 \u00f6nerilir.<\/li>\n<\/ul>\n\n# Global bir Docker imaj\u0131 tan\u0131mlayabiliriz\ndefault:\n image: node:16-alpine # T\u00fcm i\u015fler bu imaj\u0131 kullanacak varsay\u0131lan olarak\n\nstages:\n - build\n - test\n - deploy\n\nvariables:\n # \u00d6zel bir de\u011fi\u015fken tan\u0131ml\u0131yoruz\n APP_VERSION: 1.0.0\n\nbuild_job:\n stage: build\n script:\n - echo \"Uygulama versiyonu: $APP_VERSION\"\n - npm install\n - npm run build\n artifacts:\n paths:\n - build\/\n\ntest_job:\n stage: test\n # Bu i\u015f i\u00e7in farkl\u0131 bir imaj kullanabiliriz (varsay\u0131lan\u0131 ge\u00e7ersiz k\u0131lar)\n image: node:18-alpine\n before_script:\n - echo \"Test ortam\u0131 haz\u0131rlan\u0131yor...\"\n script:\n - npm test\n after_script:\n - echo \"Testler tamamland\u0131.\"\n needs:\n - build_job\n\ndeploy_job:\n stage: deploy\n script:\n - echo \"Uygulama versiyon $APP_VERSION ile da\u011f\u0131t\u0131l\u0131yor...\"\n - # Da\u011f\u0131t\u0131m komutlar\u0131 buraya gelir\n rules:\n - if: $CI_COMMIT_BRANCH == \"main\"\n needs:\n - test_job\n <\/pre>\n<\/code><\/p>\n
Bu temel yap\u0131land\u0131rmalarla, projeniz i\u00e7in g\u00fc\u00e7l\u00fc ve otomatik bir CI\/CD pipeline'\u0131 olu\u015fturmaya ba\u015flayabilirsiniz. .gitlab-ci.yml<\/code> dosyas\u0131n\u0131 projenizin k\u00f6k dizinine ekledikten sonra, GitLab otomatik olarak yeni commit'ler i\u00e7in pipeline'\u0131 tetikleyecek ve tan\u0131mlad\u0131\u011f\u0131n\u0131z i\u015fleri \u00e7al\u0131\u015ft\u0131racakt\u0131r. Bu, geli\u015ftirme s\u00fcrecinizi otomatize etme yolunda ataca\u011f\u0131n\u0131z ilk ve en \u00f6nemli ad\u0131md\u0131r.<\/p>\nGer\u00e7ek D\u00fcnya Senaryolar\u0131nda GitLab CI\/CD: Bir Web Uygulamas\u0131 i\u00e7in Otomatik Test ve Da\u011f\u0131t\u0131m Nas\u0131l Yap\u0131l\u0131r?<\/h2>\n
Teorik bilgilerin ard\u0131ndan, \u015fimdi GitLab CI\/CD'nin ger\u00e7ek bir senaryoda nas\u0131l \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 inceleyelim. Bu vaka analizinde, hem bir frontend (React) hem de bir backend (Node.js Express API) i\u00e7eren basit bir web uygulamas\u0131n\u0131 ele alaca\u011f\u0131z. Amac\u0131m\u0131z, kod de\u011fi\u015fiklikleri yap\u0131ld\u0131\u011f\u0131nda otomatik olarak testlerin \u00e7al\u0131\u015ft\u0131r\u0131lmas\u0131n\u0131, frontend ve backend uygulamalar\u0131n\u0131n derlenmesini ve ard\u0131ndan bir test ortam\u0131na (staging) otomatik olarak da\u011f\u0131t\u0131lmas\u0131n\u0131 sa\u011flayacak bir CI\/CD pipeline'\u0131 olu\u015fturmakt\u0131r. Bu senaryo, modern web geli\u015ftirme s\u00fcre\u00e7lerinde s\u0131kl\u0131kla kar\u015f\u0131la\u015f\u0131lan zorluklar\u0131 otomasyonla nas\u0131l a\u015fabilece\u011finizi g\u00f6sterecektir.<\/p>\n
Senaryo Detaylar\u0131<\/h3>\n\n- Frontend:<\/strong> React tabanl\u0131 bir SPA (Single Page Application). Ba\u011f\u0131ml\u0131l\u0131k y\u00f6netimi i\u00e7in npm kullan\u0131l\u0131yor. Testler i\u00e7in Jest, derleme i\u00e7in Webpack\/CRA (Create React App) build scripti kullan\u0131l\u0131yor.<\/li>\n
- Backend:<\/strong> Node.js ve Express.js ile yaz\u0131lm\u0131\u015f RESTful API. Ba\u011f\u0131ml\u0131l\u0131k y\u00f6netimi i\u00e7in npm kullan\u0131l\u0131yor. Testler i\u00e7in Mocha\/Chai kullan\u0131l\u0131yor.<\/li>\n
- Hedef Ortamlar:<\/strong>
main<\/code> branch'ine yap\u0131lan push'larda otomatik olarak bir \"Staging\" ortam\u0131na da\u011f\u0131t\u0131m yap\u0131lacak. Manuel onay ile bir \"Production\" ortam\u0131na da\u011f\u0131t\u0131m opsiyonu da bulunacak.<\/li>\n<\/ul>\n.gitlab-ci.yml<\/code> Dosyas\u0131 Olu\u015fturma<\/h3>\nBu senaryo i\u00e7in olduk\u00e7a detayl\u0131 bir .gitlab-ci.yml<\/code> dosyas\u0131 olu\u015fturaca\u011f\u0131z. Her iki uygulama (frontend ve backend) i\u00e7in ayr\u0131 ayr\u0131 derleme, test ve da\u011f\u0131t\u0131m a\u015famalar\u0131n\u0131 y\u00f6netece\u011fiz. Artefaktlar\u0131 kullanarak derlenmi\u015f \u00e7\u0131kt\u0131lar\u0131 a\u015famalar aras\u0131nda aktaraca\u011f\u0131z.<\/p>\n\n# .gitlab-ci.yml - Ger\u00e7ek D\u00fcnya Web Uygulamas\u0131 i\u00e7in CI\/CD Pipeline\n\n# Varsay\u0131lan Docker imaj\u0131 ve genel ayarlar\ndefault:\n image: node:18-alpine # Ortak Node.js ortam\u0131\n tags:\n - my-self-hosted-runner # Belirli bir Runner kullanmak i\u00e7in\n\n# Pipeline a\u015famalar\u0131\nstages:\n - build # Frontend ve Backend'i derle\n - test # Frontend ve Backend testlerini \u00e7al\u0131\u015ft\u0131r\n - deploy # Staging ve Production'a da\u011f\u0131t\u0131m\n\n# ====== FRONTEND \u0130\u015eLER\u0130 ======\n\nfrontend_build:\n stage: build\n # \u00c7al\u0131\u015fma dizinini frontend projesinin i\u00e7ine ta\u015f\u0131yoruz\n before_script:\n - cd frontend\n script:\n - npm install --production=false # Geli\u015ftirme ba\u011f\u0131ml\u0131l\u0131klar\u0131 dahil\n - npm run build\n artifacts:\n paths:\n - frontend\/build\/ # Derlenmi\u015f frontend dosyalar\u0131n\u0131 sakla\n expire_in: 1 week # Artefaktlar\u0131n saklama s\u00fcresi\n # Sadece frontend klas\u00f6r\u00fcnde de\u011fi\u015fiklik oldu\u011funda \u00e7al\u0131\u015f\u0131r (performans optimizasyonu)\n rules:\n - if: '$CI_COMMIT_BRANCH == \"main\"'\n changes:\n - frontend\/**\/*\n - if: '$CI_COMMIT_BRANCH != \"main\"'\n changes:\n - frontend\/**\/*\n when: on_success\n \nfrontend_test:\n stage: test\n before_script:\n - cd frontend\n script:\n - npm install --production=false\n - npm test # Frontend testlerini \u00e7al\u0131\u015ft\u0131r\n needs:\n - frontend_build # Frontend derleme i\u015finin bitmesini bekle\n rules:\n - if: '$CI_COMMIT_BRANCH == \"main\"'\n changes:\n - frontend\/**\/*\n - if: '$CI_COMMIT_BRANCH != \"main\"'\n changes:\n - frontend\/**\/*\n when: on_success\n\n# ====== BACKEND \u0130\u015eLER\u0130 ======\n\nbackend_build:\n stage: build\n before_script:\n - cd backend\n script:\n - npm install --production=false\n artifacts:\n paths:\n - backend\/node_modules\/ # Ba\u011f\u0131ml\u0131l\u0131klar\u0131 sakla (da\u011f\u0131t\u0131m i\u00e7in)\n expire_in: 1 week\n rules:\n - if: '$CI_COMMIT_BRANCH == \"main\"'\n changes:\n - backend\/**\/*\n - if: '$CI_COMMIT_BRANCH != \"main\"'\n changes:\n - backend\/**\/*\n when: on_success\n\nbackend_test:\n stage: test\n before_script:\n - cd backend\n script:\n - npm install --production=false\n - npm test # Backend testlerini \u00e7al\u0131\u015ft\u0131r\n needs:\n - backend_build # Backend derleme i\u015finin bitmesini bekle\n rules:\n - if: '$CI_COMMIT_BRANCH == \"main\"'\n changes:\n - backend\/**\/*\n - if: '$CI_COMMIT_BRANCH != \"main\"'\n changes:\n - backend\/**\/*\n when: on_success\n\n# ====== DA\u011eITIM \u0130\u015eLER\u0130 ======\n\ndeploy_staging:\n stage: deploy\n image: alpine\/git # Da\u011f\u0131t\u0131m i\u00e7in daha hafif bir imaj\n before_script:\n - apk add --no-cache rsync openssh-client # SSH ve Rsync kur\n - eval \"$(ssh-agent -s)\"\n - echo \"$SSH_PRIVATE_KEY\" | tr -d '\\r' | ssh-add - # SSH anahtar\u0131n\u0131 ekle (GitLab CI\/CD Variable)\n - mkdir -p ~\/.ssh\n - chmod 700 ~\/.ssh\n - ssh-keyscan $STAGING_SERVER_IP >> ~\/.ssh\/known_hosts # G\u00fcvenli ba\u011flant\u0131 i\u00e7in\n - chmod 644 ~\/.ssh\/known_hosts\n script:\n - echo \"Frontend ve Backend Staging ortam\u0131na da\u011f\u0131t\u0131l\u0131yor...\"\n - rsync -avz --delete frontend\/build\/ $STAGING_USER@$STAGING_SERVER_IP:\/var\/www\/html\/frontend # Frontend da\u011f\u0131t\u0131m\u0131\n - rsync -avz --delete backend\/ $STAGING_USER@$STAGING_SERVER_IP:\/var\/www\/html\/backend # Backend da\u011f\u0131t\u0131m\u0131\n - ssh $STAGING_USER@$STAGING_SERVER_IP \"cd \/var\/www\/html\/backend && npm install --production\" # Backend ba\u011f\u0131ml\u0131l\u0131klar\u0131n\u0131 kur (artefakttan da \u00e7ekilebilir)\n - ssh $STAGING_USER@$STAGING_SERVER_IP \"pm2 restart backend-app || pm2 start \/var\/www\/html\/backend\/app.js --name backend-app\" # Backend'i yeniden ba\u015flat\n environment:\n name: staging\n url: https:\/\/staging.example.com\n rules:\n - if: '$CI_COMMIT_BRANCH == \"main\"' # Sadece main branch'inden staging'e otomatik da\u011f\u0131t\u0131m\n needs:\n - frontend_test\n - backend_test\n\ndeploy_production:\n stage: deploy\n image: alpine\/git\n before_script:\n - apk add --no-cache rsync openssh-client\n - eval \"$(ssh-agent -s)\"\n - echo \"$SSH_PRIVATE_KEY\" | tr -d '\\r' | ssh-add -\n - mkdir -p ~\/.ssh\n - chmod 700 ~\/.ssh\n - ssh-keyscan $PRODUCTION_SERVER_IP >> ~\/.ssh\/known_hosts\n - chmod 644 ~\/.ssh\/known_hosts\n script:\n - echo \"Frontend ve Backend Production ortam\u0131na da\u011f\u0131t\u0131l\u0131yor...\"\n - rsync -avz --delete frontend\/build\/ $PRODUCTION_USER@$PRODUCTION_SERVER_IP:\/var\/www\/html\/frontend\n - rsync -avz --delete backend\/ $PRODUCTION_USER@$PRODUCTION_SERVER_IP:\/var\/www\/html\/backend\n - ssh $PRODUCTION_USER@$PRODUCTION_SERVER_IP \"cd \/var\/www\/html\/backend && npm install --production\"\n - ssh $PRODUCTION_USER@$PRODUCTION_SERVER_IP \"pm2 restart backend-app || pm2 start \/var\/www\/html\/backend\/app.js --name backend-app\"\n environment:\n name: production\n url: https:\/\/example.com\n rules:\n - if: '$CI_COMMIT_BRANCH == \"main\"'\n when: manual # main branch'inden production'a manuel onay ile da\u011f\u0131t\u0131m\n needs:\n - deploy_staging # Staging da\u011f\u0131t\u0131m\u0131n\u0131n ba\u015far\u0131l\u0131 olmas\u0131n\u0131 bekle\n <\/pre>\n<\/code><\/p>\n
A\u00e7\u0131klamalar ve \u00d6nemli Detaylar<\/h3>\n\n- Dizin Yap\u0131s\u0131:<\/strong> Bu senaryo, projenizin k\u00f6k dizininde
frontend\/<\/code> ve backend\/<\/code> ad\u0131nda iki alt dizin oldu\u011funu varsayar.<\/li>\nbefore_script<\/code> ile Dizin De\u011fi\u015ftirme:<\/strong> Her i\u015fin ba\u015f\u0131nda cd frontend<\/code> veya cd backend<\/code> kullanarak ilgili proje dizinine ge\u00e7i\u015f yap\u0131yoruz. Bu, komutlar\u0131n do\u011fru yerde \u00e7al\u0131\u015fmas\u0131n\u0131 sa\u011flar.<\/li>\nartifacts<\/code> Kullan\u0131m\u0131:<\/strong> frontend_build<\/code> i\u015fi, derlenmi\u015f React uygulamas\u0131n\u0131 i\u00e7eren frontend\/build\/<\/code> dizinini artefakt olarak saklar. deploy_staging<\/code> ve deploy_production<\/code> i\u015fleri bu artefaktlar\u0131 otomatik olarak indirir ve da\u011f\u0131t\u0131m s\u0131ras\u0131nda kullan\u0131r. Benzer \u015fekilde, backend_build<\/code> i\u015fi ba\u011f\u0131ml\u0131l\u0131klar\u0131 saklar, ancak da\u011f\u0131t\u0131m a\u015famas\u0131nda do\u011frudan sunucuda npm install<\/code> yapmak daha yayg\u0131n ve g\u00fcvenlidir.<\/li>\nrules<\/code> ile Ko\u015fullu \u00c7al\u0131\u015ft\u0131rma:<\/strong>\n\n- Derleme ve test i\u015fleri, sadece ilgili dizinlerde (
frontend\/\/*<\/code> veya backend\/<\/strong>\/*<\/code>) de\u011fi\u015fiklik oldu\u011funda \u00e7al\u0131\u015facak \u015fekilde optimize edilmi\u015ftir. Bu, gereksiz pipeline \u00e7al\u0131\u015ft\u0131rmalar\u0131n\u0131 \u00f6nler ve kaynak kullan\u0131m\u0131n\u0131 azalt\u0131r.<\/li>\ndeploy_staging<\/code> i\u015fi, sadece main<\/code> branch'ine yap\u0131lan push'larda otomatik olarak tetiklenir.<\/li>\ndeploy_production<\/code> i\u015fi, main<\/code> branch'inde manuel olarak tetiklenecek \u015fekilde ayarlanm\u0131\u015ft\u0131r (when: manual<\/code>). Bu, canl\u0131ya da\u011f\u0131t\u0131m \u00f6ncesi manuel kontrol sa\u011flar.<\/li>\n<\/ul>\n<\/li>\nneeds<\/code> Kullan\u0131m\u0131:<\/strong> \u0130\u015fler aras\u0131ndaki ba\u011f\u0131ml\u0131l\u0131klar\u0131 belirtmek i\u00e7in needs<\/code> anahtar kelimesi kullan\u0131l\u0131r. \u00d6rne\u011fin, frontend testleri derleme i\u015fi bitmeden \u00e7al\u0131\u015famaz.<\/li>\n- Da\u011f\u0131t\u0131m Stratejisi (SSH ve rsync):<\/strong> Da\u011f\u0131t\u0131m i\u015fleri,
alpine\/git<\/code> gibi hafif bir Docker imaj\u0131 kullan\u0131r. SSH ve rsync ara\u00e7lar\u0131n\u0131 kurarak, derlenmi\u015f dosyalar\u0131 uzak sunuculara g\u00fcvenli bir \u015fekilde aktar\u0131r\u0131z. SSH_PRIVATE_KEY<\/code>, STAGING_SERVER_IP<\/code> gibi hassas bilgiler GitLab CI\/CD De\u011fi\u015fkenleri olarak saklanmal\u0131d\u0131r ve pipeline dosyas\u0131nda direkt olarak yer almamal\u0131d\u0131r.<\/li>\n- Ortam De\u011fi\u015fkenleri (
environment<\/code>):<\/strong> deploy_staging<\/code> ve deploy_production<\/code> i\u015fleri i\u00e7in environment<\/code> anahtar kelimesi kullan\u0131lm\u0131\u015ft\u0131r. Bu, GitLab aray\u00fcz\u00fcnde her da\u011f\u0131t\u0131m\u0131n hangi ortama yap\u0131ld\u0131\u011f\u0131n\u0131 g\u00f6sterir ve ortam ba\u011flant\u0131lar\u0131na eri\u015fim sa\u011flar.<\/li>\n<\/ul>\nBu detayl\u0131 senaryo, GitLab CI\/CD'nin bir web uygulamas\u0131n\u0131n geli\u015ftirme, test ve da\u011f\u0131t\u0131m s\u00fcre\u00e7lerini ne kadar etkili bir \u015fekilde otomatize edebilece\u011fini g\u00f6stermektedir. Bu sayede, geli\u015ftirme ekibi daha h\u0131zl\u0131 geri bildirim al\u0131r, manuel hatalar azal\u0131r ve uygulama s\u00fcrekli olarak g\u00fcncel ve kararl\u0131 bir \u015fekilde kullan\u0131c\u0131lara sunulur. Bu, modern DevOps prensiplerinin ve \u00e7evik metodolojilerin temelini olu\u015fturur.<\/p>\n
\u0130leri D\u00fczey GitLab CI\/CD \u00d6zellikleri: Pipeline'lar\u0131n\u0131z\u0131 Daha Ak\u0131ll\u0131 ve H\u0131zl\u0131 Hale Getirmek \u0130\u00e7in Ne Kullanmal\u0131s\u0131n\u0131z?<\/h2>\n
GitLab CI\/CD'nin temel \u00f6zellikleriyle bir pipeline olu\u015fturmak kolayd\u0131r, ancak b\u00fcy\u00fck ve karma\u015f\u0131k projelerde performans, g\u00fcvenlik ve esnekli\u011fi art\u0131rmak i\u00e7in ileri d\u00fczey \u00f6zelliklerden yararlanmak gerekir. Bu b\u00f6l\u00fcm, pipeline'lar\u0131n\u0131z\u0131 daha ak\u0131ll\u0131, h\u0131zl\u0131 ve y\u00f6netilebilir hale getirecek baz\u0131 kritik \u00f6zellikleri ve en iyi uygulamalar\u0131 ele alacakt\u0131r.<\/p>\n
Cache (\u00d6nbellek) Kullan\u0131m\u0131<\/h3>\n
B\u00fcy\u00fck projelerde ba\u011f\u0131ml\u0131l\u0131klar\u0131n her pipeline \u00e7al\u0131\u015ft\u0131rmas\u0131nda yeniden indirilmesi, zaman ve kaynak israf\u0131na yol a\u00e7ar. cache<\/code> anahtar kelimesi, ba\u011f\u0131ml\u0131l\u0131klar\u0131 veya derleme \u00e7\u0131kt\u0131lar\u0131n\u0131 depolayarak ve bir sonraki \u00e7al\u0131\u015ft\u0131rmalarda tekrar kullanarak bu s\u00fcreci h\u0131zland\u0131r\u0131r. Bu, \u00f6zellikle Node.js (node_modules<\/code>), Java (Maven\/Gradle) veya Python (pip) gibi dillerde ba\u011f\u0131ml\u0131l\u0131klar\u0131n boyutunun b\u00fcy\u00fck oldu\u011fu durumlarda \u00e7ok faydal\u0131d\u0131r.<\/p>\n\nmy_build_job:\n stage: build\n image: node:18-alpine\n cache:\n key: ${CI_COMMIT_REF_SLUG} # Branch'e \u00f6zg\u00fc bir anahtar\n paths:\n - node_modules\/ # node_modules klas\u00f6r\u00fcn\u00fc \u00f6nbelle\u011fe al\n policy: pull-push # \u00d6nbelle\u011fi indir ve sonunda g\u00fcncelle\n script:\n - npm install\n - npm run build\n <\/pre>\n<\/code><\/p>\n
cache<\/code> ile ba\u011f\u0131ml\u0131l\u0131klar yaln\u0131zca bir kez indirilir ve sonraki \u00e7al\u0131\u015ft\u0131rmalarda \u00f6nbellekten \u00e7ekilir, bu da i\u015flerin \u00e7ok daha h\u0131zl\u0131 tamamlanmas\u0131n\u0131 sa\u011flar. key<\/code> ile farkl\u0131 branch'ler veya projeler i\u00e7in ayr\u0131 \u00f6nbellekler olu\u015fturabilirsiniz.<\/p>\nArtifacts (\u00dcretilen Dosyalar) Y\u00f6netimi<\/h3>\n
artifacts<\/code>, bir i\u015fin sonunda \u00fcretilen dosyalar\u0131 (derlenmi\u015f uygulamalar, test raporlar\u0131, log dosyalar\u0131 vb.) saklamak ve sonraki i\u015flere aktarmak i\u00e7in kullan\u0131l\u0131r. Bu, \u00f6zellikle bir a\u015famada derlenen uygulaman\u0131n sonraki a\u015famalarda test edilmesi veya da\u011f\u0131t\u0131lmas\u0131 gerekti\u011finde \u00e7ok \u00f6nemlidir.<\/p>\n\nbuild_application:\n stage: build\n script:\n - make build\n artifacts:\n paths:\n - dist\/ # dist klas\u00f6r\u00fcn\u00fc artefakt olarak sakla\n expire_in: 1 week # Saklama s\u00fcresi\n\ntest_application:\n stage: test\n script:\n - make test ARTIFACT_PATH=dist\/ # \u00d6nceki i\u015ften gelen dist klas\u00f6r\u00fcn\u00fc kullan\n needs: [\"build_application\"] # build_application i\u015finin artefaktlar\u0131na ihtiya\u00e7 duyar\n <\/pre>\n<\/code><\/p>\n
artifacts<\/code> ayr\u0131ca GitLab UI \u00fczerinden indirilebilir veya taray\u0131c\u0131da g\u00f6r\u00fcnt\u00fclenebilir hale getirilebilir (\u00f6rne\u011fin HTML test raporlar\u0131).<\/p>\nrules<\/code> Anahtar Kelimesi ile Ko\u015fullu \u0130\u015f Y\u00fcr\u00fctme<\/h3>\nrules<\/code>, bir i\u015fin ne zaman \u00e7al\u0131\u015faca\u011f\u0131n\u0131 veya atlanaca\u011f\u0131n\u0131 son derece esnek bir \u015fekilde belirlemenizi sa\u011flar. Bu, only\/except<\/code>'ten \u00e7ok daha g\u00fc\u00e7l\u00fcd\u00fcr ve karma\u015f\u0131k ko\u015fullar tan\u0131mlaman\u0131za olanak tan\u0131r. \u00d6rne\u011fin, belirli bir branch'te, belirli bir tag'de veya bir de\u011fi\u015fkenin de\u011ferine g\u00f6re i\u015fleri \u00e7al\u0131\u015ft\u0131rabilirsiniz.<\/p>\n\ndeploy_production:\n stage: deploy\n script:\n - echo \"Deploying to production...\"\n rules:\n - if: '$CI_COMMIT_TAG =~ \/^v\\d+\\.\\d+\\.\\d+$\/' # Sadece vX.Y.Z format\u0131ndaki tag'lerde \u00e7al\u0131\u015ft\u0131r\n when: manual # Manuel onay gerektir\n - if: '$CI_COMMIT_BRANCH == \"main\"' # main branch'inde otomatik \u00e7al\u0131\u015ft\u0131r\n when: on_success\n - when: never # Di\u011fer durumlarda asla \u00e7al\u0131\u015ft\u0131rma\n <\/pre>\n<\/code><\/p>\n
Bu \u00f6rnekte, production da\u011f\u0131t\u0131m\u0131 sadece belirli bir tag yap\u0131ld\u0131\u011f\u0131nda manuel olarak veya main<\/code> branch'ine push yap\u0131ld\u0131\u011f\u0131nda otomatik olarak tetiklenir. rules<\/code> ile daha temiz ve okunabilir ko\u015fullar yazabilirsiniz.<\/p>\nParent-Child Pipelines ve DAGs (Directed Acyclic Graphs)<\/h3>\n
B\u00fcy\u00fck monorepo'lar veya mikroservis mimarileri i\u00e7in tek bir devasa .gitlab-ci.yml<\/code> dosyas\u0131 y\u00f6netmek zor olabilir. Parent-Child Pipelines ve DAGs, bu sorunu \u00e7\u00f6zmek i\u00e7in tasarlanm\u0131\u015ft\u0131r:<\/p>\n\n- Parent-Child Pipelines:<\/strong> Bir ana pipeline'\u0131n (parent) dinamik olarak alt pipeline'lar (child) olu\u015fturmas\u0131n\u0131 sa\u011flar. Her alt pipeline kendi
.gitlab-ci.yml<\/code> dosyas\u0131na sahip olabilir ve sadece ilgili kod de\u011fi\u015fiklikleri oldu\u011funda tetiklenebilir. Bu, pipeline'lar\u0131 mod\u00fcler hale getirir ve paralel \u00e7al\u0131\u015fmay\u0131 art\u0131r\u0131r.<\/li>\n- DAGs (Directed Acyclic Graphs):<\/strong> \u0130\u015fler aras\u0131ndaki ba\u011f\u0131ml\u0131l\u0131klar\u0131 tan\u0131mlaman\u0131za olanak tan\u0131r. Varsay\u0131lan olarak a\u015famalar s\u0131rayla \u00e7al\u0131\u015f\u0131rken, DAGs ile farkl\u0131 a\u015famalardaki ba\u011f\u0131ms\u0131z i\u015flerin paralel \u00e7al\u0131\u015fmas\u0131n\u0131 sa\u011flayarak pipeline s\u00fcresini k\u0131saltabilirsiniz. Bu,
needs<\/code> anahtar kelimesi ile ger\u00e7ekle\u015ftirilir.<\/li>\n<\/ul>\n\n# Parent Pipeline: child pipeline'\u0131 tetikler\ntrigger_child_pipeline:\n stage: build\n trigger:\n include: path\/to\/child-ci.yml # Child pipeline dosyas\u0131n\u0131n yolu\n strategy: depend # Parent pipeline, child pipeline'\u0131n sonucunu bekler\n <\/pre>\n<\/code><\/p>\n
Bu \u00f6zellikler, b\u00fcy\u00fck \u00f6l\u00e7ekli ve karma\u015f\u0131k projeler i\u00e7in CI\/CD s\u00fcre\u00e7lerini optimize etmede kilit rol oynar. Mod\u00fclerlik, ko\u015fullu \u00e7al\u0131\u015ft\u0131rma ve performans art\u0131r\u0131c\u0131 mekanizmalar sayesinde, pipeline'lar\u0131n\u0131z daha h\u0131zl\u0131, daha g\u00fcvenilir ve daha y\u00f6netilebilir hale gelir.<\/p>\n
GitLab CI\/CD ve Mobil Uyumlu Geli\u015ftirme S\u00fcre\u00e7leri: Responsive Tasar\u0131m\u0131n Rol\u00fc<\/h2>\n
G\u00fcn\u00fcm\u00fcz internet d\u00fcnyas\u0131nda, bir web sitesinin veya uygulamas\u0131n\u0131n farkl\u0131 cihaz boyutlar\u0131na ve ekran \u00e7\u00f6z\u00fcn\u00fcrl\u00fcklerine uyum sa\u011flayabilmesi kritik bir \u00f6neme sahiptir. Mobil uyumluluk ve responsive tasar\u0131m, art\u0131k bir l\u00fcks de\u011fil, standart bir gerekliliktir. Kullan\u0131c\u0131lar\u0131n b\u00fcy\u00fck bir k\u0131sm\u0131 internete mobil cihazlar \u00fczerinden eri\u015fti\u011fi i\u00e7in, projenizin bu beklentiyi kar\u015f\u0131lamas\u0131 do\u011frudan kullan\u0131c\u0131 deneyimini ve dolay\u0131s\u0131yla i\u015f ba\u015far\u0131s\u0131n\u0131 etkiler. Peki, GitLab CI\/CD, bu mobil uyumlu geli\u015ftirme s\u00fcre\u00e7lerine nas\u0131l entegre edilebilir ve responsive tasar\u0131m\u0131n kalitesini nas\u0131l garanti alt\u0131na alabiliriz?<\/p>\n
GitLab CI\/CD, yaz\u0131l\u0131m geli\u015ftirme s\u00fcrecinin her a\u015famas\u0131nda otomasyon sa\u011flad\u0131\u011f\u0131 gibi, mobil uyumlulu\u011fun ve responsive tasar\u0131m\u0131n da s\u00fcrekli olarak denetlenmesine olanak tan\u0131r. Bir frontend projesi i\u00e7in pipeline'\u0131n\u0131zda, responsive tasar\u0131m\u0131n do\u011frulu\u011funu ve \u00e7e\u015fitli ekran boyutlar\u0131ndaki davran\u0131\u015f\u0131n\u0131 test eden otomatik ad\u0131mlar ekleyebilirsiniz. Bu, hem g\u00f6rsel regresyonlar\u0131 erkenden yakalaman\u0131za hem de farkl\u0131 cihazlar i\u00e7in tutarl\u0131 bir deneyim sunman\u0131za yard\u0131mc\u0131 olur.<\/p>\n
CI\/CD ile Responsive Tasar\u0131m\u0131n Otomatik Kontrol\u00fc<\/h3>\n
GitLab CI\/CD pipeline'\u0131n\u0131zda responsive tasar\u0131m kontrolleri i\u00e7in \u00e7e\u015fitli y\u00f6ntemler kullanabilirsiniz:<\/p>\n
\n- G\u00f6rsel Regresyon Testleri:<\/strong> Selenium, Cypress, Playwright gibi ara\u00e7lar veya \u00f6zel g\u00f6rsel regresyon test k\u00fct\u00fcphaneleri kullanarak, belirli ekran boyutlar\u0131nda web sayfan\u0131z\u0131n ekran g\u00f6r\u00fcnt\u00fclerini al\u0131p, bu g\u00f6r\u00fcnt\u00fcleri referans g\u00f6r\u00fcnt\u00fclerle kar\u015f\u0131la\u015ft\u0131rabilirsiniz. Her yeni kod de\u011fi\u015fikli\u011finde, farkl\u0131 cihaz boyutlar\u0131 i\u00e7in sayfan\u0131n beklendi\u011fi gibi g\u00f6r\u00fcnd\u00fc\u011f\u00fcnden emin olursunuz.<\/li>\n
- Linting ve Code Standard\u0131 Kontrolleri:<\/strong> CSS preprocessor'lar\u0131n\u0131z (Sass, Less) veya PostCSS gibi ara\u00e7lar\u0131n\u0131zla responsive tasar\u0131m i\u00e7in belirlenen standartlara uyulup uyulmad\u0131\u011f\u0131n\u0131 otomatik olarak kontrol edebilirsiniz. \u00d6rne\u011fin, belirli breakpoint'lerin do\u011fru kullan\u0131l\u0131p kullan\u0131lmad\u0131\u011f\u0131 veya gereksiz stiller i\u00e7erip i\u00e7ermedi\u011fi denetlenebilir.<\/li>\n
- Performans Testleri:<\/strong> Mobil cihazlarda sayfa y\u00fckleme h\u0131z\u0131 ve performans kritik \u00f6nem ta\u015f\u0131r. Lighthouse veya WebPageTest gibi ara\u00e7lar\u0131 CI\/CD pipeline'\u0131n\u0131za entegre ederek, web uygulaman\u0131z\u0131n mobil performans skorlar\u0131n\u0131 d\u00fczenli olarak \u00f6l\u00e7ebilir ve olumsuz de\u011fi\u015fiklikleri erkenden tespit edebilirsiniz.<\/li>\n<\/ul>\n
\u00d6rne\u011fin, bir frontend projeniz varsa, derleme ve test a\u015famalar\u0131ndan sonra g\u00f6rsel regresyon testleri \u00e7al\u0131\u015ft\u0131ran bir i\u015f ekleyebilirsiniz:<\/p>\n
\nvisual_regression_test:\n stage: test\n image: cypress\/browsers:node16.14.0-chrome99-ff97\n script:\n - npm install\n - npm run cypress:run -- --config video=false --env SIZES=\"375,768,1280\" # Farkl\u0131 ekran boyutlar\u0131nda testler\n artifacts:\n when: always\n paths:\n - cypress\/screenshots\/\n - cypress\/videos\/\n expire_in: 1 day\n needs:\n - frontend_build # Frontend derleme i\u015finin artefaktlar\u0131na ihtiya\u00e7 duyabilir\n <\/pre>\n<\/code><\/p>\n
Bu i\u015f, Cypress gibi bir ara\u00e7 kullanarak belirli ekran boyutlar\u0131nda (\u00f6rne\u011fin 375px mobil, 768px tablet, 1280px masa\u00fcst\u00fc) otomatik testler \u00e7al\u0131\u015ft\u0131r\u0131r ve ekran g\u00f6r\u00fcnt\u00fcleri veya videolar olu\u015fturur. Bu \u00e7\u0131kt\u0131lar artefakt olarak saklanarak, geli\u015ftiricilerin pipeline ba\u015far\u0131s\u0131z oldu\u011funda sorunu g\u00f6rsel olarak incelemesine olanak tan\u0131r.<\/p>\n
Mobil uyumlu HTML'e bir \u00f6rnek te\u015fkil etmesi a\u00e7\u0131s\u0131ndan, tipik bir responsive CSS media query a\u015fa\u011f\u0131daki gibi g\u00f6r\u00fcnebilir. Bu t\u00fcr kurallar CI\/CD pipeline'\u0131ndaki g\u00f6rsel testlerle veya linting ara\u00e7lar\u0131yla do\u011frulanabilir:<\/p>\n
\n\/* Temel stil (Mobil \u00f6ncelikli) *\/\nbody {\n font-size: 16px;\n margin: 10px;\n}\n\n\/* Orta boyutlu ekranlar i\u00e7in (tabletler) *\/\n@media (min-width: 768px) {\n body {\n font-size: 18px;\n margin: 20px;\n }\n .sidebar {\n width: 200px;\n float: left;\n }\n}\n\n\/* B\u00fcy\u00fck ekranlar i\u00e7in (masa\u00fcst\u00fc) *\/\n@media (min-width: 1200px) {\n body {\n font-size: 20px;\n margin: 30px;\n }\n .sidebar {\n width: 250px;\n float: left;\n }\n .main-content {\n margin-left: 270px;\n }\n}\n <\/pre>\n<\/code><\/p>\n
Sonu\u00e7 olarak, GitLab CI\/CD, responsive tasar\u0131m\u0131n ve mobil uyumlulu\u011fun sadece tasar\u0131m a\u015famas\u0131nda de\u011fil, t\u00fcm geli\u015ftirme ve da\u011f\u0131t\u0131m ya\u015fam d\u00f6ng\u00fcs\u00fc boyunca s\u00fcrd\u00fcr\u00fclmesini ve kalitesinin garanti alt\u0131na al\u0131nmas\u0131n\u0131 sa\u011flayan g\u00fc\u00e7l\u00fc bir ara\u00e7t\u0131r. Otomatik testler ve kontroller sayesinde, \u00fcr\u00fcn\u00fcn\u00fcz\u00fcn her zaman ve her cihazda m\u00fckemmel bir kullan\u0131c\u0131 deneyimi sunmas\u0131n\u0131 sa\u011flayabilirsiniz.<\/p>\n
GitLab CI\/CD \u0130pu\u00e7lar\u0131 ve En \u0130yi Uygulamalar: Pipeline'lar\u0131n\u0131z\u0131 Daha Etkili Kullanmak \u0130\u00e7in P\u00fcf Noktalar\u0131 Nelerdir?<\/h2>\n
GitLab CI\/CD'den en iyi \u015fekilde yararlanmak i\u00e7in sadece temel \u00f6zelliklerini bilmek yeterli de\u011fildir; ayn\u0131 zamanda deneyimli kullan\u0131c\u0131lar\u0131n kulland\u0131\u011f\u0131 ipu\u00e7lar\u0131n\u0131 ve en iyi uygulamalar\u0131 benimsemek de \u00f6nemlidir. Bu b\u00f6l\u00fcmde, pipeline'lar\u0131n\u0131z\u0131n g\u00fcvenli\u011fini, performans\u0131n\u0131 ve s\u00fcrd\u00fcr\u00fclebilirli\u011fini art\u0131racak stratejiler \u00fczerinde duraca\u011f\u0131z.<\/p>\n
1. Hassas Veri Y\u00f6netimi: De\u011fi\u015fkenler ve Secret'lar<\/h3>\n
Da\u011f\u0131t\u0131m anahtarlar\u0131, API token'lar\u0131, veritaban\u0131 \u015fifreleri gibi hassas bilgiler asla .gitlab-ci.yml<\/code> dosyas\u0131n\u0131n i\u00e7inde veya Git deposunda d\u00fcz metin olarak saklanmamal\u0131d\u0131r. GitLab CI\/CD, bu t\u00fcr verileri g\u00fcvenli bir \u015fekilde y\u00f6netmek i\u00e7in \"CI\/CD Variables\" \u00f6zelli\u011fini sunar.<\/p>\n\n- Ortam De\u011fi\u015fkenleri:<\/strong> GitLab aray\u00fcz\u00fcnde (Settings -> CI\/CD -> Variables) tan\u0131mlanan de\u011fi\u015fkenler, pipeline i\u015fleri \u00e7al\u0131\u015f\u0131rken otomatik olarak ortam de\u011fi\u015fkenleri olarak eri\u015filebilir hale gelir. Bunlar\u0131 \"Protected\" (Korunmu\u015f) ve \"Masked\" (Maskelenmi\u015f) olarak i\u015faretleyerek daha da g\u00fcvenli hale getirebilirsiniz.<\/li>\n
- Vault Entegrasyonu:<\/strong> Daha ileri d\u00fczey g\u00fcvenlik gereksinimleri i\u00e7in, GitLab'\u0131n HashiCorp Vault gibi harici secret y\u00f6netim sistemleriyle entegrasyonu mevcuttur. Bu, secret'lar\u0131n ya\u015fam d\u00f6ng\u00fcs\u00fcn\u00fc daha merkezi ve g\u00fcvenli bir \u015fekilde y\u00f6netmenizi sa\u011flar.<\/li>\n<\/ul>\n
\ndeploy_job:\n stage: deploy\n script:\n - echo \"Deploying with API Key: $API_KEY\" # API_KEY GitLab CI\/CD Variable'dan gelir\n - ssh -i $SSH_PRIVATE_KEY user@host \"...\" # SSH_PRIVATE_KEY de bir de\u011fi\u015fkendir\n <\/pre>\n<\/code><\/p>\n
API_KEY<\/code> veya SSH_PRIVATE_KEY<\/code> gibi de\u011fi\u015fkenler GitLab UI'da tan\u0131mlanm\u0131\u015ft\u0131r ve pipeline taraf\u0131ndan g\u00fcvenli bir \u015fekilde kullan\u0131l\u0131r.<\/p>\n2. Pipeline Performans\u0131n\u0131 Optimize Etme<\/h3>\n\n- Paralel \u00c7al\u0131\u015ft\u0131rma:<\/strong> Ayn\u0131 a\u015fama i\u00e7indeki i\u015fler paralel olarak \u00e7al\u0131\u015f\u0131r. Ba\u011f\u0131ms\u0131z testleri veya derleme ad\u0131mlar\u0131n\u0131 ayr\u0131 i\u015fler olarak tan\u0131mlayarak pipeline s\u00fcrenizi k\u0131saltabilirsiniz.<\/li>\n
- \u00d6nbellekleme (Caching):<\/strong> Daha \u00f6nce bahsedildi\u011fi gibi,
cache<\/code> kullanarak ba\u011f\u0131ml\u0131l\u0131klar\u0131n yeniden indirilmesini \u00f6nleyin. Anahtar stratejisini (key<\/code>) do\u011fru belirlemek \u00f6nemlidir (\u00f6rne\u011fin branch bazl\u0131 veya global).<\/li>\n- Docker \u0130majlar\u0131n\u0131 Optimize Etme:<\/strong> \u0130\u015fleriniz i\u00e7in m\u00fcmk\u00fcn oldu\u011funca k\u00fc\u00e7\u00fck ve optimize edilmi\u015f Docker imajlar\u0131 kullan\u0131n. Gerekli ara\u00e7lar\u0131 i\u00e7eren \u00f6zel imajlar olu\u015fturmak, indirme s\u00fcrelerini ve disk alan\u0131n\u0131 azalt\u0131r.<\/li>\n
- Sadece \u0130lgili De\u011fi\u015fikliklerde \u00c7al\u0131\u015ft\u0131rma (
rules: changes<\/code>):<\/strong> Bir \u00f6nceki ger\u00e7ek d\u00fcnya senaryosunda oldu\u011fu gibi, rules: if: '$CI_COMMIT_BRANCH == \"main\"' changes: [...]<\/code> ile sadece ilgili kod veya dizinlerde de\u011fi\u015fiklik oldu\u011funda belirli i\u015flerin \u00e7al\u0131\u015fmas\u0131n\u0131 sa\u011flay\u0131n. Bu, monorepo'larda \u00e7ok verimli olabilir.<\/li>\n<\/ul>\n3. Pipeline Kodunun Yeniden Kullan\u0131labilirli\u011fi ve Mod\u00fclerli\u011fi<\/h3>\n
B\u00fcy\u00fck projelerde veya birden fazla benzer projeyi y\u00f6netirken, pipeline kodunu yeniden kullan\u0131labilir ve mod\u00fcler hale getirmek \u00f6nemlidir. Bu, DRY (Don't Repeat Yourself) prensibini uygulaman\u0131za yard\u0131mc\u0131 olur.<\/p>\n
\nextends<\/code> Anahtar Kelimesi:<\/strong> Ortak i\u015f veya job \u015fablonlar\u0131 tan\u0131mlayabilir ve di\u011fer i\u015flerin bu \u015fablonlar\u0131 miras almas\u0131n\u0131 sa\u011flayabilirsiniz. Bu, benzer i\u015fler i\u00e7in kod tekrar\u0131n\u0131 \u00f6nler.<\/li>\ninclude<\/code> Anahtar Kelimesi:<\/strong> Harici YAML dosyalar\u0131n\u0131 pipeline tan\u0131m\u0131n\u0131za dahil etmenizi sa\u011flar. Bu sayede, ortak CI\/CD yap\u0131land\u0131rmalar\u0131n\u0131 ayr\u0131 dosyalarda saklayabilir ve birden fazla projede yeniden kullanabilirsiniz. \u00d6rne\u011fin, t\u00fcm projeleriniz i\u00e7in ortak bir test i\u015fi tan\u0131mlayabilir ve her projenin .gitlab-ci.yml<\/code> dosyas\u0131na dahil edebilirsiniz.<\/li>\n<\/ul>\n\n# .gitlab-ci.yml\ninclude:\n - 'templates\/.gitlab-ci-build.yml' # Ortak build \u015fablonunu dahil et\n - 'templates\/.gitlab-ci-deploy.yml' # Ortak deploy \u015fablonunu dahil et\n\n# templates\/.gitlab-ci-build.yml i\u00e7eri\u011fi:\n.build_template: # Nokta ile ba\u015flayan i\u015fler gizli \u015fablonlard\u0131r\n image: node:18-alpine\n script:\n - echo \"Building...\"\n - npm install\n - npm run build\n\n# Mevcut pipeline'da \u015fablonu kullan\nmy_app_build:\n extends: .build_template # .build_template \u015fablonunu miras al\n stage: build\n artifacts:\n paths:\n - build\/\n <\/pre>\n<\/code><\/p>\n
Bu y\u00f6ntemler, pipeline'lar\u0131n\u0131z\u0131n daha d\u00fczenli, okunabilir ve y\u00f6netilebilir olmas\u0131n\u0131 sa\u011flar, \u00f6zellikle de CI\/CD stratejinizin zamanla evrimle\u015fmesi gerekti\u011finde esneklik sunar.<\/p>\n
\n Uzman \u0130pucu: Pipeline'lar\u0131n\u0131zda
debug<\/code> modu ekleyerek veya CI_DEBUG_TRACE: \"true\"<\/code> ortam de\u011fi\u015fkenini kullanarak i\u015flerin neden ba\u015far\u0131s\u0131z oldu\u011funu anlamak i\u00e7in daha fazla log \u00e7\u0131kt\u0131s\u0131 alabilirsiniz.\n <\/div>\nBu ipu\u00e7lar\u0131 ve en iyi uygulamalar, GitLab CI\/CD kullan\u0131m\u0131n\u0131z\u0131 bir sonraki seviyeye ta\u015f\u0131yarak, daha g\u00fcvenli, h\u0131zl\u0131 ve s\u00fcrd\u00fcr\u00fclebilir yaz\u0131l\u0131m geli\u015ftirme s\u00fcre\u00e7leri olu\u015fturman\u0131za yard\u0131mc\u0131 olacakt\u0131r. Otomasyonun g\u00fcc\u00fcnden tam olarak yararlanmak i\u00e7in s\u00fcrekli \u00f6\u011frenmeye ve pipeline'lar\u0131n\u0131z\u0131 optimize etmeye devam edin.<\/p>\n
Sonu\u00e7: GitLab CI\/CD ile Gelece\u011fin Yaz\u0131l\u0131m Geli\u015ftirme S\u00fcre\u00e7leri<\/h2>\n
Bu kapsaml\u0131 rehber boyunca, GitLab CI\/CD'nin temel prensiplerinden ba\u015flayarak, pratik pipeline olu\u015fturma ad\u0131mlar\u0131na, ger\u00e7ek d\u00fcnya senaryolar\u0131ndan ileri d\u00fczey \u00f6zelliklere ve en iyi uygulamalara kadar bir\u00e7ok konuyu derinlemesine inceledik. Modern yaz\u0131l\u0131m geli\u015ftirme d\u00fcnyas\u0131nda s\u00fcrekli entegrasyon ve teslimat\u0131n ne kadar kritik oldu\u011funu, GitLab CI\/CD'nin bu s\u00fcre\u00e7leri nas\u0131l tek bir platformda entegre ederek verimlili\u011fi ve g\u00fcvenilirli\u011fi art\u0131rd\u0131\u011f\u0131n\u0131 detayl\u0131 bir \u015fekilde g\u00f6rd\u00fck.<\/p>\n
GitLab CI\/CD, basit bir statik web sitesinden karma\u015f\u0131k mikroservis mimarilerine kadar her t\u00fcrl\u00fc projeye uyarlanabilen esnek ve g\u00fc\u00e7l\u00fc bir ara\u00e7 setidir. Kodunuzu otomatik olarak test etmek, derlemek ve da\u011f\u0131tmak, hatalar\u0131 erkenden yakalamak ve yeni \u00f6zellikleri kullan\u0131c\u0131lara h\u0131zla ula\u015ft\u0131rmak art\u0131k bir l\u00fcks de\u011fil, bir zorunluluktur. Otomatikle\u015ftirilmi\u015f pipeline'lar sayesinde geli\u015ftiriciler, operasyonel y\u00fcklerden kurtulup daha fazla inovasyona odaklanabilirken, ekipler daha \u015feffaf ve i\u015fbirli\u011fine dayal\u0131 bir \u00e7al\u0131\u015fma ortam\u0131 elde eder.<\/p>\n
Unutmay\u0131n ki CI\/CD yolculu\u011fu s\u00fcrekli bir \u00f6\u011frenme ve iyile\u015ftirme s\u00fcrecidir. Pipeline'lar\u0131n\u0131z\u0131 d\u00fczenli olarak g\u00f6zden ge\u00e7irmek, performans darbo\u011fazlar\u0131n\u0131 gidermek, g\u00fcvenlik a\u00e7\u0131klar\u0131n\u0131 kapatmak ve yeni GitLab \u00f6zelliklerini takip etmek, bu s\u00fcre\u00e7ten en y\u00fcksek verimi alman\u0131z\u0131 sa\u011flayacakt\u0131r. GitLab CI\/CD, DevOps k\u00fclt\u00fcr\u00fcn\u00fc benimseyen ekipler i\u00e7in sadece bir ara\u00e7 de\u011fil, ayn\u0131 zamanda yaz\u0131l\u0131m geli\u015ftirme pratiklerini d\u00f6n\u00fc\u015ft\u00fcren stratejik bir yat\u0131r\u0131md\u0131r. Gelece\u011fin yaz\u0131l\u0131m geli\u015ftirme s\u00fcre\u00e7lerinde otomasyonun ve s\u00fcrekli ak\u0131\u015f\u0131n vazge\u00e7ilmez bir par\u00e7as\u0131 olmaya devam edecektir.<\/p>\n
S\u0131k\u00e7a Sorulan Sorular<\/h3>\n\n- \n S: GitLab CI\/CD kullanmak \u00fccretli midir?<\/strong><\/p>\n
C: GitLab CI\/CD'nin temel \u00f6zellikleri ve Payla\u015f\u0131ml\u0131 Runner'lar, GitLab'\u0131n \u00fccretsiz (Free) plan\u0131nda s\u0131n\u0131rl\u0131 dakikalarla birlikte gelir. Kendi \u00f6zel Runner'lar\u0131n\u0131z\u0131 kurarak bu s\u0131n\u0131rlamay\u0131 a\u015fabilirsiniz. Daha geli\u015fmi\u015f \u00f6zellikler ve daha fazla CI\/CD dakikas\u0131 i\u00e7in \u00fccretli GitLab planlar\u0131 mevcuttur.<\/p>\n<\/li>\n
- \n S: Kendi GitLab Runner'\u0131m\u0131 nas\u0131l kurar\u0131m?<\/strong><\/p>\n
C: Kendi GitLab Runner'\u0131n\u0131z\u0131 Linux, Windows veya macOS sistemlerinize kolayca kurabilirsiniz. Kurulum talimatlar\u0131 GitLab dok\u00fcmantasyonunda detayl\u0131 olarak verilmi\u015ftir. Kurulumdan sonra Runner'\u0131 GitLab \u00f6rne\u011finize kaydetmeniz ve pipeline i\u015flerinde kullanmak \u00fczere etiketlemeniz gerekir.<\/p>\n<\/li>\n
- \n S: CI\/CD Pipeline'\u0131m neden ba\u015far\u0131s\u0131z oluyor? Nas\u0131l hata ay\u0131klayabilirim?<\/strong><\/p>\n
C: Pipeline ba\u015far\u0131s\u0131zl\u0131klar\u0131 genellikle .gitlab-ci.yml<\/code> dosyas\u0131ndaki s\u00f6zdizimi hatalar\u0131ndan, yanl\u0131\u015f komutlardan, eksik ba\u011f\u0131ml\u0131l\u0131klardan veya ortam sorunlar\u0131ndan kaynaklan\u0131r. Hata ay\u0131klama i\u00e7in \u015funlar\u0131 yapabilirsiniz: \u0130\u015f loglar\u0131n\u0131 dikkatlice inceleyin, i\u015fin Docker imaj\u0131n\u0131 yerel olarak \u00e7al\u0131\u015ft\u0131r\u0131p komutlar\u0131 manuel olarak deneyin, echo<\/code> komutlar\u0131yla de\u011fi\u015fken de\u011ferlerini ve komut \u00e7\u0131kt\u0131lar\u0131n\u0131 kontrol edin veya CI_DEBUG_TRACE: \"true\"<\/code> de\u011fi\u015fkenini kullanarak daha detayl\u0131 loglar al\u0131n.<\/p>\n<\/li>\n- \n S: GitLab CI\/CD'yi farkl\u0131 programlama dilleri veya teknolojileriyle kullanabilir miyim?<\/strong><\/p>\n
C: Kesinlikle! GitLab CI\/CD agnostik bir yap\u0131ya sahiptir. \u0130\u015flerinizde kullanaca\u011f\u0131n\u0131z Docker imaj\u0131n\u0131 belirleyerek (\u00f6rne\u011fin node<\/code>, python<\/code>, ruby<\/code>, maven<\/code>, golang<\/code> imajlar\u0131), herhangi bir programlama dili veya teknolojiyle CI\/CD s\u00fcre\u00e7leri olu\u015fturabilirsiniz. Sadece ilgili dillerin veya ara\u00e7lar\u0131n komutlar\u0131n\u0131 script<\/code> b\u00f6l\u00fcm\u00fcne eklemeniz yeterlidir.<\/p>\n<\/li>\n- \n S: GitLab CI\/CD'de \"stages\" ve \"needs\" aras\u0131ndaki fark nedir?<\/strong><\/p>\n
C: stages<\/code>, pipeline'daki mant\u0131ksal a\u015famalar\u0131 (\u00f6rne\u011fin build, test, deploy) tan\u0131mlar ve a\u015famalar genellikle s\u0131rayla \u00e7al\u0131\u015f\u0131r. Ayn\u0131 a\u015fama i\u00e7indeki i\u015fler paralel \u00e7al\u0131\u015fabilir. needs<\/code> ise i\u015fler aras\u0131ndaki belirli ba\u011f\u0131ml\u0131l\u0131klar\u0131 tan\u0131mlar. Bir i\u015f, kendinden \u00f6nceki herhangi bir a\u015famadaki veya kendi a\u015famas\u0131ndaki belirli bir i\u015fin tamamlanmas\u0131n\u0131 bekleyebilir. Bu, a\u015fama s\u0131ralamas\u0131ndan ba\u011f\u0131ms\u0131z olarak i\u015flerin daha esnek bir \u015fekilde paralel \u00e7al\u0131\u015fmas\u0131n\u0131 sa\u011flayarak pipeline s\u00fcresini optimize etmenizi sa\u011flar.<\/p>\n<\/li>\n<\/ul>\n<\/body><\/p>\n","protected":false},"excerpt":{"rendered":"Modern yaz\u0131l\u0131m d\u00fcnyas\u0131nda, uygulamalar\u0131n h\u0131zl\u0131, g\u00fcvenilir ve s\u00fcrekli bir \u015fekilde geli\u015ftirilip da\u011f\u0131t\u0131lmas\u0131 hi\u00e7 olmad\u0131\u011f\u0131 kadar kritik. Peki, karma\u015f\u0131k…","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_page_header_type":"","csco_page_load_nextpost":"","csco_page_subscribe_form":"","csco_page_contact_form":"","footnotes":""},"categories":[1401],"tags":[],"class_list":{"0":"post-30766","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-git","7":"cs-entry","8":"cs-video-wrap"},"yoast_head":"\n
GitLab CI\/CD: Yaz\u0131l\u0131m Geli\u015ftirme S\u00fcre\u00e7lerinde Otomasyon ve Verimlilik<\/title>\n<meta name=\"description\" content=\"Modern yaz\u0131l\u0131m d\u00fcnyas\u0131nda, uygulamalar\u0131n h\u0131zl\u0131, g\u00fcvenilir ve s\u00fcrekli bir \u015fekilde geli\u015ftirilip da\u011f\u0131t\u0131lmas\u0131 hi\u00e7 olmad\u0131\u011f\u0131 kadar kritik. Peki, karma\u015f\u0131k geli\u015ftirme s\u00fcre\u00e7lerini nas\u0131l basitle\u015ftirir, hatalar\u0131 erkenden yakalar ve \u00fcr\u00fcn\u00fcn\u00fcz\u00fc pazara daha h\u0131zl\u0131 sunars\u0131n\u0131z? \u0130\u015fte tam bu noktada GitLab CI\/CD devreye girerek, otomasyonun g\u00fcc\u00fcn\u00fc parmaklar\u0131n\u0131z\u0131n ucuna getiriyor. Bu kapsaml\u0131 rehberde, GitLab CI\/CD'nin temel prensiplerinden ileri d\u00fczey kullan\u0131m ipu\u00e7lar\u0131na kadar her \u015feyi ad\u0131m ad\u0131m ke\u015ffedece\u011fiz. Gelin, CI\/CD d\u00fcnyas\u0131na do\u011fru heyecan verici bir yolculu\u011fa \u00e7\u0131kal\u0131m ve yaz\u0131l\u0131m geli\u015ftirme s\u00fcre\u00e7lerinizi nas\u0131l d\u00f6n\u00fc\u015ft\u00fcrebilece\u011finizi \u00f6\u011frenelim!\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/fatihsoysal.com\/blog\/gitlab-ci-cd-yazilim-gelistirme-sureclerinde-otomasyon-ve-verimlilik\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"GitLab CI\/CD: Yaz\u0131l\u0131m Geli\u015ftirme S\u00fcre\u00e7lerinde Otomasyon ve Verimlilik\" \/>\n<meta property=\"og:description\" content=\"Modern yaz\u0131l\u0131m d\u00fcnyas\u0131nda, uygulamalar\u0131n h\u0131zl\u0131, g\u00fcvenilir ve s\u00fcrekli bir \u015fekilde geli\u015ftirilip da\u011f\u0131t\u0131lmas\u0131 hi\u00e7 olmad\u0131\u011f\u0131 kadar kritik. Peki, karma\u015f\u0131k geli\u015ftirme s\u00fcre\u00e7lerini nas\u0131l basitle\u015ftirir, hatalar\u0131 erkenden yakalar ve \u00fcr\u00fcn\u00fcn\u00fcz\u00fc pazara daha h\u0131zl\u0131 sunars\u0131n\u0131z? \u0130\u015fte tam bu noktada GitLab CI\/CD devreye girerek, otomasyonun g\u00fcc\u00fcn\u00fc parmaklar\u0131n\u0131z\u0131n ucuna getiriyor. Bu kapsaml\u0131 rehberde, GitLab CI\/CD'nin temel prensiplerinden ileri d\u00fczey kullan\u0131m ipu\u00e7lar\u0131na kadar her \u015feyi ad\u0131m ad\u0131m ke\u015ffedece\u011fiz. Gelin, CI\/CD d\u00fcnyas\u0131na do\u011fru heyecan verici bir yolculu\u011fa \u00e7\u0131kal\u0131m ve yaz\u0131l\u0131m geli\u015ftirme s\u00fcre\u00e7lerinizi nas\u0131l d\u00f6n\u00fc\u015ft\u00fcrebilece\u011finizi \u00f6\u011frenelim!\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fatihsoysal.com\/blog\/gitlab-ci-cd-yazilim-gelistirme-sureclerinde-otomasyon-ve-verimlilik\/\" \/>\n<meta property=\"og:site_name\" content=\"Kodlar\u0131n Gizemli D\u00fcnyas\u0131\" \/>\n<meta property=\"article:published_time\" content=\"2025-10-01T18:32:10+00:00\" \/>\n<meta name=\"author\" content=\"Fatih Soysal\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Yazan:\" \/>\n\t<meta name=\"twitter:data1\" content=\"Fatih Soysal\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tahmini okuma s\u00fcresi\" \/>\n\t<meta name=\"twitter:data2\" content=\"34 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/gitlab-ci-cd-yazilim-gelistirme-sureclerinde-otomasyon-ve-verimlilik\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/gitlab-ci-cd-yazilim-gelistirme-sureclerinde-otomasyon-ve-verimlilik\/\"},\"author\":{\"name\":\"Fatih Soysal\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"headline\":\"GitLab CI\/CD: Yaz\u0131l\u0131m Geli\u015ftirme S\u00fcre\u00e7lerinde Otomasyon ve Verimlilik\",\"datePublished\":\"2025-10-01T18:32:10+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/gitlab-ci-cd-yazilim-gelistirme-sureclerinde-otomasyon-ve-verimlilik\/\"},\"wordCount\":5112,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"articleSection\":[\"Git\"],\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/gitlab-ci-cd-yazilim-gelistirme-sureclerinde-otomasyon-ve-verimlilik\/#respond\"]}],\"copyrightYear\":\"2025\",\"copyrightHolder\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/gitlab-ci-cd-yazilim-gelistirme-sureclerinde-otomasyon-ve-verimlilik\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/gitlab-ci-cd-yazilim-gelistirme-sureclerinde-otomasyon-ve-verimlilik\/\",\"name\":\"GitLab CI\/CD: Yaz\u0131l\u0131m Geli\u015ftirme S\u00fcre\u00e7lerinde Otomasyon ve Verimlilik\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\"},\"datePublished\":\"2025-10-01T18:32:10+00:00\",\"description\":\"Modern yaz\u0131l\u0131m d\u00fcnyas\u0131nda, uygulamalar\u0131n h\u0131zl\u0131, g\u00fcvenilir ve s\u00fcrekli bir \u015fekilde geli\u015ftirilip da\u011f\u0131t\u0131lmas\u0131 hi\u00e7 olmad\u0131\u011f\u0131 kadar kritik. Peki, karma\u015f\u0131k geli\u015ftirme s\u00fcre\u00e7lerini nas\u0131l basitle\u015ftirir, hatalar\u0131 erkenden yakalar ve \u00fcr\u00fcn\u00fcn\u00fcz\u00fc pazara daha h\u0131zl\u0131 sunars\u0131n\u0131z? \u0130\u015fte tam bu noktada GitLab CI\/CD devreye girerek, otomasyonun g\u00fcc\u00fcn\u00fc parmaklar\u0131n\u0131z\u0131n ucuna getiriyor. Bu kapsaml\u0131 rehberde, GitLab CI\/CD'nin temel prensiplerinden ileri d\u00fczey kullan\u0131m ipu\u00e7lar\u0131na kadar her \u015feyi ad\u0131m ad\u0131m ke\u015ffedece\u011fiz. Gelin, CI\/CD d\u00fcnyas\u0131na do\u011fru heyecan verici bir yolculu\u011fa \u00e7\u0131kal\u0131m ve yaz\u0131l\u0131m geli\u015ftirme s\u00fcre\u00e7lerinizi nas\u0131l d\u00f6n\u00fc\u015ft\u00fcrebilece\u011finizi \u00f6\u011frenelim!\",\"breadcrumb\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/gitlab-ci-cd-yazilim-gelistirme-sureclerinde-otomasyon-ve-verimlilik\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/gitlab-ci-cd-yazilim-gelistirme-sureclerinde-otomasyon-ve-verimlilik\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/gitlab-ci-cd-yazilim-gelistirme-sureclerinde-otomasyon-ve-verimlilik\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Anasayfa\",\"item\":\"https:\/\/fatihsoysal.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"GitLab CI\/CD: Yaz\u0131l\u0131m Geli\u015ftirme S\u00fcre\u00e7lerinde Otomasyon ve Verimlilik\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/\",\"name\":\"Fatihsoysal.com\",\"description\":\"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim\",\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"tr\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\",\"name\":\"Fatih Soysal\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"tr\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"contentUrl\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"width\":512,\"height\":512,\"caption\":\"Fatih Soysal\"},\"logo\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\"},\"description\":\"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"GitLab CI\/CD: Yaz\u0131l\u0131m Geli\u015ftirme S\u00fcre\u00e7lerinde Otomasyon ve Verimlilik","description":"Modern yaz\u0131l\u0131m d\u00fcnyas\u0131nda, uygulamalar\u0131n h\u0131zl\u0131, g\u00fcvenilir ve s\u00fcrekli bir \u015fekilde geli\u015ftirilip da\u011f\u0131t\u0131lmas\u0131 hi\u00e7 olmad\u0131\u011f\u0131 kadar kritik. Peki, karma\u015f\u0131k geli\u015ftirme s\u00fcre\u00e7lerini nas\u0131l basitle\u015ftirir, hatalar\u0131 erkenden yakalar ve \u00fcr\u00fcn\u00fcn\u00fcz\u00fc pazara daha h\u0131zl\u0131 sunars\u0131n\u0131z? \u0130\u015fte tam bu noktada GitLab CI\/CD devreye girerek, otomasyonun g\u00fcc\u00fcn\u00fc parmaklar\u0131n\u0131z\u0131n ucuna getiriyor. Bu kapsaml\u0131 rehberde, GitLab CI\/CD'nin temel prensiplerinden ileri d\u00fczey kullan\u0131m ipu\u00e7lar\u0131na kadar her \u015feyi ad\u0131m ad\u0131m ke\u015ffedece\u011fiz. Gelin, CI\/CD d\u00fcnyas\u0131na do\u011fru heyecan verici bir yolculu\u011fa \u00e7\u0131kal\u0131m ve yaz\u0131l\u0131m geli\u015ftirme s\u00fcre\u00e7lerinizi nas\u0131l d\u00f6n\u00fc\u015ft\u00fcrebilece\u011finizi \u00f6\u011frenelim!","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/fatihsoysal.com\/blog\/gitlab-ci-cd-yazilim-gelistirme-sureclerinde-otomasyon-ve-verimlilik\/","og_locale":"tr_TR","og_type":"article","og_title":"GitLab CI\/CD: Yaz\u0131l\u0131m Geli\u015ftirme S\u00fcre\u00e7lerinde Otomasyon ve Verimlilik","og_description":"Modern yaz\u0131l\u0131m d\u00fcnyas\u0131nda, uygulamalar\u0131n h\u0131zl\u0131, g\u00fcvenilir ve s\u00fcrekli bir \u015fekilde geli\u015ftirilip da\u011f\u0131t\u0131lmas\u0131 hi\u00e7 olmad\u0131\u011f\u0131 kadar kritik. Peki, karma\u015f\u0131k geli\u015ftirme s\u00fcre\u00e7lerini nas\u0131l basitle\u015ftirir, hatalar\u0131 erkenden yakalar ve \u00fcr\u00fcn\u00fcn\u00fcz\u00fc pazara daha h\u0131zl\u0131 sunars\u0131n\u0131z? \u0130\u015fte tam bu noktada GitLab CI\/CD devreye girerek, otomasyonun g\u00fcc\u00fcn\u00fc parmaklar\u0131n\u0131z\u0131n ucuna getiriyor. Bu kapsaml\u0131 rehberde, GitLab CI\/CD'nin temel prensiplerinden ileri d\u00fczey kullan\u0131m ipu\u00e7lar\u0131na kadar her \u015feyi ad\u0131m ad\u0131m ke\u015ffedece\u011fiz. Gelin, CI\/CD d\u00fcnyas\u0131na do\u011fru heyecan verici bir yolculu\u011fa \u00e7\u0131kal\u0131m ve yaz\u0131l\u0131m geli\u015ftirme s\u00fcre\u00e7lerinizi nas\u0131l d\u00f6n\u00fc\u015ft\u00fcrebilece\u011finizi \u00f6\u011frenelim!","og_url":"https:\/\/fatihsoysal.com\/blog\/gitlab-ci-cd-yazilim-gelistirme-sureclerinde-otomasyon-ve-verimlilik\/","og_site_name":"Kodlar\u0131n Gizemli D\u00fcnyas\u0131","article_published_time":"2025-10-01T18:32:10+00:00","author":"Fatih Soysal","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"Fatih Soysal","Tahmini okuma s\u00fcresi":"34 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fatihsoysal.com\/blog\/gitlab-ci-cd-yazilim-gelistirme-sureclerinde-otomasyon-ve-verimlilik\/#article","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/gitlab-ci-cd-yazilim-gelistirme-sureclerinde-otomasyon-ve-verimlilik\/"},"author":{"name":"Fatih Soysal","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"headline":"GitLab CI\/CD: Yaz\u0131l\u0131m Geli\u015ftirme S\u00fcre\u00e7lerinde Otomasyon ve Verimlilik","datePublished":"2025-10-01T18:32:10+00:00","mainEntityOfPage":{"@id":"https:\/\/fatihsoysal.com\/blog\/gitlab-ci-cd-yazilim-gelistirme-sureclerinde-otomasyon-ve-verimlilik\/"},"wordCount":5112,"commentCount":0,"publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"articleSection":["Git"],"inLanguage":"tr","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fatihsoysal.com\/blog\/gitlab-ci-cd-yazilim-gelistirme-sureclerinde-otomasyon-ve-verimlilik\/#respond"]}],"copyrightYear":"2025","copyrightHolder":{"@id":"https:\/\/fatihsoysal.com\/blog\/#organization"}},{"@type":"WebPage","@id":"https:\/\/fatihsoysal.com\/blog\/gitlab-ci-cd-yazilim-gelistirme-sureclerinde-otomasyon-ve-verimlilik\/","url":"https:\/\/fatihsoysal.com\/blog\/gitlab-ci-cd-yazilim-gelistirme-sureclerinde-otomasyon-ve-verimlilik\/","name":"GitLab CI\/CD: Yaz\u0131l\u0131m Geli\u015ftirme S\u00fcre\u00e7lerinde Otomasyon ve Verimlilik","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/#website"},"datePublished":"2025-10-01T18:32:10+00:00","description":"Modern yaz\u0131l\u0131m d\u00fcnyas\u0131nda, uygulamalar\u0131n h\u0131zl\u0131, g\u00fcvenilir ve s\u00fcrekli bir \u015fekilde geli\u015ftirilip da\u011f\u0131t\u0131lmas\u0131 hi\u00e7 olmad\u0131\u011f\u0131 kadar kritik. Peki, karma\u015f\u0131k geli\u015ftirme s\u00fcre\u00e7lerini nas\u0131l basitle\u015ftirir, hatalar\u0131 erkenden yakalar ve \u00fcr\u00fcn\u00fcn\u00fcz\u00fc pazara daha h\u0131zl\u0131 sunars\u0131n\u0131z? \u0130\u015fte tam bu noktada GitLab CI\/CD devreye girerek, otomasyonun g\u00fcc\u00fcn\u00fc parmaklar\u0131n\u0131z\u0131n ucuna getiriyor. Bu kapsaml\u0131 rehberde, GitLab CI\/CD'nin temel prensiplerinden ileri d\u00fczey kullan\u0131m ipu\u00e7lar\u0131na kadar her \u015feyi ad\u0131m ad\u0131m ke\u015ffedece\u011fiz. Gelin, CI\/CD d\u00fcnyas\u0131na do\u011fru heyecan verici bir yolculu\u011fa \u00e7\u0131kal\u0131m ve yaz\u0131l\u0131m geli\u015ftirme s\u00fcre\u00e7lerinizi nas\u0131l d\u00f6n\u00fc\u015ft\u00fcrebilece\u011finizi \u00f6\u011frenelim!","breadcrumb":{"@id":"https:\/\/fatihsoysal.com\/blog\/gitlab-ci-cd-yazilim-gelistirme-sureclerinde-otomasyon-ve-verimlilik\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fatihsoysal.com\/blog\/gitlab-ci-cd-yazilim-gelistirme-sureclerinde-otomasyon-ve-verimlilik\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fatihsoysal.com\/blog\/gitlab-ci-cd-yazilim-gelistirme-sureclerinde-otomasyon-ve-verimlilik\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Anasayfa","item":"https:\/\/fatihsoysal.com\/blog\/"},{"@type":"ListItem","position":2,"name":"GitLab CI\/CD: Yaz\u0131l\u0131m Geli\u015ftirme S\u00fcre\u00e7lerinde Otomasyon ve Verimlilik"}]},{"@type":"WebSite","@id":"https:\/\/fatihsoysal.com\/blog\/#website","url":"https:\/\/fatihsoysal.com\/blog\/","name":"Fatihsoysal.com","description":"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim","publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"tr"},{"@type":["Person","Organization"],"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1","name":"Fatih Soysal","image":{"@type":"ImageObject","inLanguage":"tr","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","contentUrl":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","width":512,"height":512,"caption":"Fatih Soysal"},"logo":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/"},"description":"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.","url":"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/"}]}},"yoast_meta":{"yoast_wpseo_title":"","yoast_wpseo_metadesc":"","yoast_wpseo_canonical":""},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/30766","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/comments?post=30766"}],"version-history":[{"count":0,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/30766\/revisions"}],"wp:attachment":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/media?parent=30766"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/categories?post=30766"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/tags?post=30766"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}