Gitlab CI - Der Fuchs im Schafspelz

Der Kampf durch zahllose Konfigurationsseiten bei jedem Build-Job ist ein frustrierendes Erlebnis im Entwickleralltag. Pipeline-as-code vermeidet diese Frustration und sorgt gleichzeitig dafür, dass die CI-Pipeline immer zur Version der Applikation passt. Außer Pipeline-as-code bietet Gitlab CI gute Integrationsmöglichkeiten für eigene Docker-Services, die während der Pipeline benutzt werden können.

Der Talk bereitet kurz die Grundlagen von CI/CD auf und zeigt dann praktisch, wie man eine Pipeline für eine Spring-Boot Anwendung mit Integrations-Tests für Gitlab CI konzipiert. Nach der Demo erzählt Jonas, warum der Fuchs den alten Platzhirschen Jenkins bei uns verdrängt hat.

Transcript

1. Jonas Bechstein | cosee GmbH jonas.bechstein@cosee.biz | @jobe93 GitLab CI - Der Fuchs im Schafspelz
2. Jonas Bechstein Cloud Backend Engineer
3. Backend Mobile Frontend DevOps Agile Coach
4. Wer benutzt CI/CD?
5. Continuous Integration?
6. Feedback
7. Benefits of Continuous Integration • Early feedback to developer • Improves bug detection • Improves collaboration • Visibility project status • Boosting Time-to-Market CC-BY Thomas Ferris Nicolaisen tfnico.com
10. 11 Practices of Continuous Integration
11. Maintain a Single Source Repository
12. Automate the Build
13. Make Your Build Self-Testing
14. Everyone Commits To the Mainline Every Day
15. Every Commit Should Build the Mainline on an Integration Machine
16. Fix Broken Builds Immediately
17. Keep the Build Fast
18. Test in a Clone of the Production Environment
19. Make it Easy for Anyone to Get the Latest Executable
20. Make it Easy for Anyone to Get the Latest Executable
21. Everyone can see what's happening Pipelines View
22. Everyone can see what's happening Premium feature: Multi-project pipelines
23. Automate Deployment
24. What are the advantages of pipelines?
26. How are individual steps connected? Jenkins 2.37
27. Pipelines build code_quality test deploy staging deploy production Integration-tests acceptance-tests
28. • Pipelines are versioned in the code repository • CI Server can be configured faster & easier to debug • Modularizable & Reusable Pipeline as Code
29. • GitLab core is Open Source • Source Code Repository
 with integrated CI/CD service • Growing range of functions
32. How to write a .gitlab-ci.yml
33. hello: #Job name image: alpine:latest #Docker image script: - echo "Hello World" #commands to run Hello World
34. Stages stages: - build - test image: maven:3-jdk-11-slim #Docker image build: #Job name stage: build #dedicated stage script: - mvn clean package -DskipTests test: stage: test script: - mvn clean verify
35. Cache #Global cache cache: paths: - .m2/repository build: stage: build script: - mvn clean package #Local cache build: stage: build script: - mvn clean package cache: paths: - .m2/repository
36. Artifacts image: maven:3-jdk-11-slim build: stage: build script: - mvn clean package artifacts: #Artifact policy expire_in: 1 week paths: - target/*.jar #Artifact Path build-docker-images: stage: pack script: - docker -t ... build . - docker push ... dependencies: build #Marks dependencies # Job fails when artifacts have expired.
37. YML-Anchor vs extends .deploy: &deploy stage: deploy script: - ... only: - master deploy-staging: <<: *deploy stage: deploy-staging after_script: - ... variables: envname: stage deploy-production: <<: *deploy stage: deploy-production before_script: - ... variables: envname: production .deploy: script: - ... only: - master deploy-staging: extends: .deploy stage: deploy-staging after_script: - ... variables: envname: stage deploy-production: extends: .deploy stage: deploy-production before_script: - ... variables: envname: production
38. Include #template.yml .template: script: - echo Hello! #.gitlab-ci.yml include: included.yml useTemplate: image: alpine extends: .template
39. Services test: stage: test image: maven:3-jdk-11 script: - mvn clean package services: - name: postgres:9.6 alias: postgres variables: POSTGRES_DB: poll POSTGRES_PASSWORD: testing-password POSTGRES_USER: user cache: paths: - .m2/repository
40. Start an other pipeline start-hello: stage: start-next image: appropriate/curl:latest script: - 'curl --request POST --header "PRIVATE-TOKEN: $CI_API_TOKEN” https://gitlab.com/api/v4/projects/{id}/pipeline?ref=master'
41. • Pre-defined CI/CD configuration • Automatically detect, build, test, deploy, and monitor your applications. • Easy bootstrapping of K8s and your services • If you want to do something unusual, forget about auto devops. Auto DevOps
42. Auto DevOps
43. Demo
44. Final thoughts
45. Nächster Talk … talks.cosee.biz | blog.cosee.biz | @coseeaner | #coseetechtalks Besser spät als nie: Testsuite in bestehenden React-Apps nachziehen Mirjam Bäuerlein | 25.07.2019