Иван Немытченко, GitLab

1. GitLab CI vs Jenkins
Ivan Nemytchenko | CEE SECR | October 29, 2016

2. Continous Integration

3. Motivational part of CI
Let's prevent integration
problems!

4. Motivational part of CI
Let's combine all pieces
together once a day to
check if it works!

5. No need to motivate
anyone anymore

6. CI is like VC

7. Practical part of CI
CI used to be manual

8. Practical part of CI
CI configuration used to
require separate job
position

9. Modern CI tools are
not usually that complex

10. You can use CI not only in big projects

11. GitLab CI vs Jenkins
Напрямую сравнивать неверно
Но мы сделаем это!

12. Сравниваем в лоб
→ GitLab CI - часть основного продукта
→ Jenkins - самостоятельный продукт

18. Сравниваем в лоб
→ GitLab CI - Ruby on Rails + Go
→ Jenkins - Java

19. Сравниваем в лоб
→ GitLab CI - GitLab + Runners
→ Jenkins - Master + Slaves

20. Сравниваем в лоб
→ GitLab CI - Ничего лишнего, Convention over
configuration
→ Jenkins - Плагины разработанные сообществом

21. Сравниваем в лоб
→ GitLab CI - Technology-agnostic
→ Jenkins - В каком-то смысле тоже, но плагины

22. Сравниваем в лоб
→ GitLab CI - Configuration as code
→ Jenkins - Настройка через UI*

34. CatGrep Sophisticated Technologies inc.
→ file1.txt
→ file2.txt

35. CatGrep Sophisticated Technologies inc.
The code is on GitLab.com

36. Requirement #1
Concatenation result should contain
"Hello world"

37. cat file1.txt file2.txt | grep -q "Hello world"

38. Run first test inside CI

39. Run first test inside CI
.gitlab-ci.yml

40. Run first test inside CI
test:
script: cat file1.txt file2.txt | grep -q 'Hello world'

41. Run first test inside CI

42. Run first test inside CI

43. Requirement #2
Package code before sending it to customer

44. Package code
test:
script: cat file1.txt file2.txt | grep -q 'Hello world'
package:
script: cat file1.txt file2.txt | gzip > package.gz

45. Package code

46. Make results of your build downloadable

47. Make results of your build downloadable

48. Make results of your build downloadable

49. Make results of your build downloadable
test:
script: cat file1.txt file2.txt | grep -q 'Hello world'
package:
script: cat file1.txt file2.txt | gzip > packaged.gz
artifacts:
paths:
- packaged.gz

50. Run jobs sequentially

51. Run jobs sequentially

52. Speeding up the build

53. Removing Duplication

55. Learning what Docker image to use

56. Learning what Docker image to use

57. Learning what Docker image to use
image: alpine

58. Learning what Docker image to use

59. Learning what Docker image to use

60. Requirement #3
ISO instead of GZIP

61. Dealing with complex scenarios

62. Dealing with complex scenarios
script:
- apk add -U cdrkit
- mkisofs -o ./packaged.iso ./compiled.txt

65. → 3 stages
→ passing files between stages
→ downloadable artifacts
→ optimized execution time
→ custom pipeline

66. @inemation
ivan@gitlab.com
→ bit.ly/gitlab-ci1
→ bit.ly/gitlab-ci2

67. → Environment variables
→ Environments (Staging, Production)
→ GitLab Pages
→ Roillback
→ Manual deployment

68. Requirement #4
Publish a website, containing packages

69. Publish a website
aws s3 cp ./ s3://yourbucket/ --recursive

70. Publish a website

71. Publish a website

72. First Automated Deployment
→ awscli can be installed using pip
→ pip goes together with python

73. First Automated Deployment
s3:
image: python
stage: deploy
script:
- pip install awscli
- aws s3 cp ./ s3://yourbucket/ --recursive

74. First Automated Deployment
AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY

75. First Automated Deployment

76. Keeping Secret Things Secret

77. Keeping Secret Things Secret
Settings → Variables

78. Keeping Secret Things Secret
s3:
image: python
stage: deploy
script:
- pip install awscli
- aws s3 cp ./ s3://yourbucket/ --recursive

79. Keeping Secret Things Secret

80. Requirement #5
Two developers on the project

81. Two developers on the project

82. Two developers on the project

83. Requirement #6
Need a separate place
for testing

84. Separate place for testing
GitLab Pages

85. Host website using GitLab Pages
→ your job should be named "pages"
→ put your files into "public" folder
→ specify "artifacts" section with this "public" folder

86. Host website using GitLab Pages
http://<username>.gitlab.io/<projectname>

87. Host website using GitLab Pages
pages:
stage: deploy
image: alpine
script:
- mkdir -p ./public && cp ./*.* ./public/
artifacts:
paths:
- public
except:
- master

88. Separate place for testing
s3:
image: python
stage: deploy
script:
- pip install awscli
- aws s3 cp ./ s3://yourbucket/ --recursive
only:
- master
pages:
image: alpine
stage: deploy
script:
- mkdir -p ./public && cp ./*.* ./public/
artifacts:
paths:
- public
except:
- master

89. Separate place for testing

90. Separate place for testing

91. Separate place for testing

93. Using Environments

94. Using Environments

95. Using Environments

96. Requirement #7
Do not mess up production

97. Do not mess up production

98. Do not mess up production

102. Questions?
@inem
ivan@gitlab.com
→ bit.ly/gitlab-ci1
→ bit.ly/gitlab-ci2