Breaking bad habits with GitLab CI

1. BREAKING BAD
WITH GITLAB CI
IVAN NEMYTCHENKO, DEVELOPER ADVOCATE

2. IVAN NEMYTCHENKO
> Ruby developer
> Project manager
> Co-founder of outsourcing agency
> Developer advocate at GitLab
> railshurts.com
> inem.at
> @inem

3. SOFTWARE DEVELOPMENT PROCESS

5. Every tool covers a part of the whole process

6. MODERN SOFTWARE DEVELOPMENT PROCESS
IS SPREAD ACROSS MANY TOOLS

7. Travis - GitHub - Trello - Slack

8. Bitbucket - Semaphore - Pivotal Tracker - HipChat

9. Jenkins - GitLab - Jira

17. BREAKING BAD
WITH GITLAB CIIVAN NEMYTCHENKO, DEVELOPER ADVOCATE

18. BREAKING BAD WITH GITLAB CI

19. BREAKING BAD WITH GITLAB CI

20. BREAKING BAD
HABITS
WITH GITLAB CIIVAN NEMYTCHENKO, DEVELOPER ADVOCATE

22. HABIT OF
NOT AUTOMATING
THE ROUTINE TASKS

23. THIS HABIT COMES FROM
THE FEAR OF CI SYSTEMS

36. CATGREP SOPHISTICATED TECHNOLOGIES INC.
> file1.txt
> file2.txt

37. REQUIREMENT #1
CONCATENATION RESULT SHOULD
CONTAIN "HELLO WORLD"

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

40. RUN OUR FIRST TEST INSIDE CI

41. .gitlab-ci.yml

42. test:
script: cat file1.txt file2.txt | grep -q 'Hello world'

45. REQUIREMENT #2
PACKAGE CODE BEFORE SENDING IT TO CUSTOMER

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

48. MAKE RESULTS OF YOUR BUILD DOWNLOADABLE

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

51. RUN JOBS SEQUENTIALLY

52. stages:
- test
- package
test:
stage: test
script: cat file1.txt file2.txt | grep -q 'Hello world'
package:
stage: package
script: cat file1.txt file2.txt | gzip > packaged.gz
artifacts:
paths:
- packaged.gz

53. SPEEDING UP THE BUILD

54. #1: DUPLICATION

55. stages:
- compile
- test
- package
compile:
stage: compile
script: cat file1.txt file2.txt > compiled.txt
artifacts:
paths:
- compiled.txt
test:
stage: test
script: cat compiled.txt | grep -q 'Hello world'
package:
stage: package
script: cat compiled.txt | gzip > packaged.gz
artifacts:
paths:
- packaged.gz

57. compile:
stage: compile
script: cat file1.txt file2.txt > compiled.txt
artifacts:
paths:
- compiled.txt
expire_in: 20 minutes

58. #2: RUBY 2.1 ????

59. LEARNING WHAT DOCKER IMAGE TO USE

60. image: alpine

61. image: alpine
stages:
- compile
- test
- package
compile: ...
test: ...

63. > defined 3 stages
> pass files between stages
> downloadable artifacts
> optimized execution time

64. REQUIREMENT #3
ISO INSTEAD OF GZIP

65. DEALING WITH COMPLEX SCENARIOS

67. image: alpine
stages:
- compile
- test
- package
compile: ...
test: ...
pack-gz:
stage: package
script: cat compiled.txt | gzip > packaged.gz
artifacts:
paths:
- packaged.gz
pack-iso:
stage: package
script:
- mkisofs -o ./packaged.iso ./compiled.txt
artifacts:
paths:
- packaged.iso

69. DEALING WITH MISSING SOFTWARE/PACKAGES

70. apk add -U cdrkit

71. script:
- apk add -U cdrkit
- mkisofs -o ./packaged.iso ./compiled.txt

72. pack-iso:
stage: package
before_script:
- apk add -U cdrkit
script:
- mkisofs -o ./packaged.iso ./compiled.txt
artifacts:
paths:
- packaged.iso

75. GITLAB OUIREMENT #4
PUBLISH
A SMALL WEBSITE WITH OUR
PACKAGES

76. HTML → AMAZON S3

77. aws s3 cp ./ s3://yourbucket/ --recursive

80. FIRST AUTOMATED DEPLOYMENT

81. > awscli can be installed using pip
> pip goes together with python

82. s3:
image: python:latest
stage: deploy
script:
- pip install awscli
- aws s3 cp ./ s3://yourbucket/ --recursive

83. AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY

84. variables:
AWS_ACCESS_KEY_ID: "AKIAIOSFODNN7EXAMPLE"
AWS_SECRET_ACCESS_KEY: “wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY”
s3:
image: python:latest
stage: deploy
script:
- pip install awscli
- aws s3 cp ./ s3://yourbucket/ --recursive

85. KEEPING SECRET THINGS SECRET

86. SETTINGS --> VARIABLES

87. s3:
image: python:latest
stage: deploy
script:
- pip install awscli
- aws s3 cp ./ s3://yourbucket/ --recursive

88. So far so good:

89. REQUIREMENT #5
MORE THAN ONE DEVELOPER
ON THE PROJECT

90. s3:
image: python:latest
stage: deploy
script:
- pip install awscli
- aws s3 cp ./ s3://yourbucket/ --recursive
only:
- master

92. REQUIREMENT #6
WE NEED A SEPARATE PLACE
FOR TESTING

93. GITLAB PAGES

94. HOST WEBSITES ON GITLAB PAGES
> your job should be named "pages"
> put your files into "public" folder
> specify "artifacts" section with this "public" folder

95. HOST WEBSITES ON GITLAB PAGES
> your job should be named "pages"
> put your files into "public" folder
> specify "artifacts" section with this "public" folder
HTTP://<USERNAME>.GITLAB.IO/<PROJECTNAME>

96. pages:
stage: deploy
image: alpine:latest
script:
- mkdir -p ./public && cp ./*.* ./public/
artifacts:
paths:
- public
except:
- master

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

101. INTRODUCING ENVIRONMENTS

102. s3:
environment: production
image: python:latest
stage: deploy
script:
- pip install awscli
- aws s3 cp ./ s3://$S3_BUCKET_NAME/ --recursive
only:
- master
pages:
image: alpine:latest
environment: staging
stage: deploy
script:
- mkdir -p ./public && cp ./*.* ./public/
artifacts:
paths:
- public
except:
- master

106. REQUIREMENT #7
DO NOT MESS UP PRODUCTION

107. SWITCHING TO MANUAL DEPLOYMENT

108. s3:
image: python:latest
stage: deploy
script:
- pip install awscli
- aws s3 cp ./ s3://yourbucket/ --recursive
only:
- master
when: manual

110. BOOTING UP APPLICATION INSTANCE
PER FEATURE-BRANCH

112. <S3_BUCKET>.S3-WEBSITE-US-EAST-1.AMAZONAWS.COM/<BRANCHNAME>

113. review apps:
image: python:latest
environment: review
script:
- pip install awscli
- aws s3 cp ./ s3://reviewbucket/$CI_BUILD_REF_NAME/ --recursive

114. $CI_BUILD_REF_NAME
?

115. PREDEFINED VARIABLES

116. SUMMARY
1. Deployment is just a set of commands
2. You need to provide secret keys
3. You specify where which branches should go to
4. GitLab conserves the history of deployments
5. You can enable manual deployment

120. GO TO GITLAB.COM

121. @INEM
INEM@BK.RU
BIT.LY/GITLAB-CI1
BIT.LY/GITLAB-CI2