git - Gitlab CI vs Jenkins -


can please let me know difference between jenkins , other ci gitlab-ci, drone.io coming git distribution. on research come gitlab community edition doesn't allow jenkins added gitlab enterprise edition does. there other significant differences.

this experience:

at work manage our repositories gitlab ee , have jenkins server (1.6) running.

in basis pretty same. run scripts on server/docker image.

tl;dr;

  • jenkins easier use/learn has risk become plugin hell
  • jenkins has gui (this can preferred if has accesible/maintainable other people)
  • integration gitlab less gitlab-ci
  • jenkins can split off repo

most ci servers pretty straight forward (concourse.ci, gitlab-ci, circle-ci, travis-ci, drone.io, gocd , else have you). allow execute shell/bat yaml file definition. jenkins more pluggable, , comes ui. can either advantage or disadvantage, depending on needs.

jenkins configurable because of plugins available. downside of ci server can become spaghetti of plugins.

in opinion chaining , orchestrating of jobs in jenkins simpler (because of ui) via yaml (calling curl commands). besides jenkins supports plugins install binaries when not available on server (don't know others).

nowadays (jenkins2 supports more "proper ci" jenkinsfile , pipline plugin comes default jenkins 2), used less coupled repository i.e. gitlab ci.

using yaml files define build pipeline (and in end running pure shell/bat) cleaner.

edit: forgot mention here plug-ins available jenkins allow visualize kinds of reporting, such test results, coverage , other static analyzers. of course can write or use tool you, plus jenkins (especially managers tend value these reports much)

edit2: lately have been working more , more gitlab-ci. @ gitlab doing great job making whole experience fun. understand people use jenkins, when have gitlab running , available easy started gitlab-ci. there won't integrate seamless gitlab-ci, though put quite effort in 3rd party integrations.

  • their documentation should started in no time
  • the threshold started low
  • maintenance easy (no plugins)
  • scaling runners simple
  • ci part of repository
  • jenkins jobs/views can messy

some perks @ time of writing

  • only support single file, going fixed soon

Comments

Popular posts from this blog

PySide and Qt Properties: Connecting signals from Python to QML -

c# - DevExpress.Wpf.Grid.InfiniteGridSizeException was unhandled -

scala - 'wrong top statement declaration' when using slick in IntelliJ -