Gitlab CI/CD
I am Fathi Jemli
Software engineer at Proxym-IT
You can find me at
@jemlifathi
2HELLO!
Plan
» CI/CD
» Gitlab
» Usage of Gitlab (CI/CD) at Proxym
3
CI/CD
Continuous Integration / Continuous Delivery
4
1.
5CI/CD lifecycle
Continuous Integration
» The process of validation of new code changes compared to the
main code base
» Testing and merging the new features and their integration in the
main release branch
» CI tools:
» Code test
» Code review
» Build, etc.
6
7
Main code base
New code
CI
Failure
Success
Continuous delivery
» The process of releasing new changes to clients in an automated
way
» New features are delivered to customers in a record time
» Bugs are detected instantly for each new release
» Customers participate in the improvement of the product
» Minimise client acceptance period
8
» Most used CI/CD platforms:
» Circle CI
» Travis CI
» Code Ship
» Gitlab CI
9
Gitlab
“A single application for the complete DevOps lifecycle”
10
2.
Gitlab
» Open source project (MIT licence) created October 2011 using
Ruby
» Offers commercial solution (Gitlab Enterprise Edition)
» Features:
» Hosting Git repositories
» Supports merge requests and issues management
» A complete DevOps solution including CI/CD
» Offers an integration solutions with other services such as
Jira, Redmine, Slack and email notifications
11
12Gitlab CI/CD
13Gitlab CI/CD
Usage of Gitlab at Proxym
14
3.
Gitlab Proxym
» Gitlab instance hosted on AWS (https://gitlab.proxym-group.net)
» Three runners (at the moment)
» 2 runners based on docker
» 1 iOS runner
» Docker images registry
» LDAP authentication
» Email notifications
15
Any questions?
You can find me at:
» @jemlifathi
16THANKS for your attention!
Demo time

Gitlab CI/CD

  • 1.
  • 2.
    I am FathiJemli Software engineer at Proxym-IT You can find me at @jemlifathi 2HELLO!
  • 3.
    Plan » CI/CD » Gitlab »Usage of Gitlab (CI/CD) at Proxym 3
  • 4.
    CI/CD Continuous Integration /Continuous Delivery 4 1.
  • 5.
  • 6.
    Continuous Integration » Theprocess of validation of new code changes compared to the main code base » Testing and merging the new features and their integration in the main release branch » CI tools: » Code test » Code review » Build, etc. 6
  • 7.
    7 Main code base Newcode CI Failure Success
  • 8.
    Continuous delivery » Theprocess of releasing new changes to clients in an automated way » New features are delivered to customers in a record time » Bugs are detected instantly for each new release » Customers participate in the improvement of the product » Minimise client acceptance period 8
  • 9.
    » Most usedCI/CD platforms: » Circle CI » Travis CI » Code Ship » Gitlab CI 9
  • 10.
    Gitlab “A single applicationfor the complete DevOps lifecycle” 10 2.
  • 11.
    Gitlab » Open sourceproject (MIT licence) created October 2011 using Ruby » Offers commercial solution (Gitlab Enterprise Edition) » Features: » Hosting Git repositories » Supports merge requests and issues management » A complete DevOps solution including CI/CD » Offers an integration solutions with other services such as Jira, Redmine, Slack and email notifications 11
  • 12.
  • 13.
  • 14.
    Usage of Gitlabat Proxym 14 3.
  • 15.
    Gitlab Proxym » Gitlabinstance hosted on AWS (https://gitlab.proxym-group.net) » Three runners (at the moment) » 2 runners based on docker » 1 iOS runner » Docker images registry » LDAP authentication » Email notifications 15
  • 16.
    Any questions? You canfind me at: » @jemlifathi 16THANKS for your attention!
  • 17.