My history with Jenkins

Vol.01　Jul/20/2016 Takeshi Takizawa Shared Services Technology Supervisory Department, Rakuten Inc.

2

Takeshi Takizawa

Rakuten, Inc. Shared Services Technology Supervisory Department Ecosystem Services Department Service Support Section Delivery and Reliability Solution Group DevOps Platform Team Assistant Manager

3

2010

4

Join Rakuten

5

International Ichiba Section

6

2010 No Jenkins

https://jenkins.io/

7

Physical Machine

8

Manual Test

9

Manual Release

10

2012

11

2012 First Contact

12

Virtual Machine

13

Test Automation

14

Manual Release

15

2013

16

2013 became Jenkins Maintainer

https://jenkins.io/

17

Private Cloud

18

Test Automation

19

Deploy Automation

20

Improved one task

21

2014

22

2014 Fire Jenkins

https://jenkins.io/

23

Private Cloud

24

Parallel Test with Build Flow Plugin

25

Git merge chain with Build Flow Plugin

26

Manage Job configurations with Ansible

27

Execute E2E test with Docker

28

Improved operations

29

2015

30

Service Support Section

31

2015 Master Jenkins

https://jenkins.io/

32

OpenStack

33

Manage several Jenkins

https://jenkins.io/

34

Provision Server with Terraform and Chef

35

Immutable Infrastructure

36

2016

37

2016 Ninjenkins

https://jenkins.io/

38

OpenStack &

Kurbenetes on hybrid ENV

39

Deployment Pipeline with Pipeline Plugin

40

Stage View of Pipeline Plugin

41

Trying to manage services with Kubernetes

42

Container as a Service

43

Conclusion

44

We still need Jenkins or something

Even though using Any Platform Need to handle CI/CD Pipeline by ourselves

45

Thank you!

https://jenkins.io/

46

Rakuten Technology Conference 2016

22nd Oct 2016 Futako Tamagawa Rakuten Crimson House