1. Breaking Bad habits
with GitLab CI
Ivan Nemytchenko | RubyConf Taiwan | December 2, 2016

2. Ivan
Nemytchenko
→ Russian, live in Serbia
→ Ruby developer since 2006
→ Co-found 2 outsource agencies
→ Team lead, Project manager, etc
→ Coorganized 2 IT conferences
→ Developer advocate at GitLab
→ inem.at
→ @inem

3. RailsHurts.com

4. How to Stop being Rails
developer

6. Why talk about GitLab?
→ big monolythic RoR application
→ open source
→ monthly releases
→ open processes (google for GitLab handbook)
→ 140 people (all remote)
→ 100.000+ companies use it
→ GitLab.com is free

7. GitLab
has been started as an attempt to build
open source alternative to GitHub

9. Breaking Bad with GitLab CI

10. Breaking Bad Habits with GitLab CI

11. Habit of not automating
routine operations

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

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

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

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

27. Run first test inside CI

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

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

30. Run first test inside CI

31. Run first test inside CI

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

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

34. Package code

35. Make results of your build downloadable

36. Make results of your build downloadable

37. Make results of your build downloadable

38. 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

39. Run jobs sequentially

40. Run jobs sequentially

41. Speeding up the build

42. Removing Duplication

44. Learning what Docker image to use

45. Learning what Docker image to use

46. Learning what Docker image to use
image: alpine

47. Learning what Docker image to use

48. Learning what Docker image to use

49. Requirement #3
ISO instead of GZIP

50. Dealing with complex scenarios

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

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

55. Requirement #4
Publish a website, containing packages

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

57. Publish a website

58. Publish a website

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

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

61. First Automated Deployment
AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY

62. First Automated Deployment

63. Keeping Secret Things Secret

64. Keeping Secret Things Secret
Settings → Variables

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

66. Keeping Secret Things Secret

67. Requirement #5
Two developers on the project

68. Two developers on the project

69. Two developers on the project

70. Requirement #6
Need a separate place
for testing

71. Separate place for testing
GitLab Pages

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

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

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

75. 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

76. Separate place for testing

77. Separate place for testing

78. Separate place for testing

80. Using Environments

81. Using Environments

82. Using Environments

83. Requirement #7
Do not mess up production

84. Do not mess up production

85. Do not mess up production

89. You can afford CI even for
small projects!

90. Why no ruby?

91. Questions?
@inem
ivan@gitlab.com
→ bit.ly/gitlab-ci