The document discusses Continuous Integration (CI), its purpose of improving software quality and reducing communication gaps, and positions Jenkins as a leading tool for implementing CI due to its user-friendly interface and extensive plugin support. It outlines the processes involved in CI, such as building, testing, and deploying code, while addressing the benefits and drawbacks of CI practices. Additionally, it emphasizes the importance of automated testing and early feedback in the development process to catch bugs sooner and streamline project management.

1. ou
u n
Let’s start
in io
t t s
n a
o r with
C g
Inte Jenkins

2. What’s
Continuous
Integration?

3. Organize
Current problems

4. Lots of bugs are found at the end of test phase
As the system size increases, load of test gets
bigger
Frequently degraded when merge
Hard to merge manually
Unexpected recognition differences of
requirements

5. Lots of bugs are found at the end of test phase
As the system size increases, load of test gets
bigger
Frequently degraded when merge
Hard to merge manually
Unexpected recognition differences of
requirements

6. Lots of bugs are found at the end of test phase
As the system size increases, load of test gets
bigger
Frequently degraded when merge
Hard to merge manually
Unexpected recognition differences of
requirements

7. Lots of bugs are found at the end of test phase
As the system size increases, load of test gets
bigger
Frequently degraded when merge
Hard to merge manually
Unexpected recognition differences of
requirements

8. Lots of bugs are found at the end of test phase
As the system size increases, load of test gets
bigger
Frequently degraded when merge
Hard to merge manually
Unexpected recognition differences of
requirements

9. W e d o n’t
a n y m o re !!

10. Purp
ose

11. Improve
quality

12. Decrease
frustration

13. Reduce the
communication gap
with early feedback

14. Continuous integration Continuous integration
Continuous integration Continuous integration
Continuous integration Continuous integration
Continuous integration Continuous integration
Continuous integration Continuous integration
What
isContinuous integration?
Continuous integration Continuous integration
Continuous integration Continuous integration
Continuous integration Continuous integration
Continuous integration Continuous integration
Continuous integration Continuous integration

15. CI
is the “practice”
but not a “tool”.

16. Process of CI
Build server CI server Repository
Monitor

17. Process of CI
Build server CI server Repository
Detect
Commit

18. Process of CI
Build server CI server Repository
Build

19. Process of CI
Build server CI server Repository
Report

20. CI is composed of:
connection to repository
build script
feedback means such as mail
process of integrating source code modification
(test, inspection, deployment and feedback)

21. CI is composed of:
connection to repository
build script
feedback means such as mail
process of integrating source code modification
(test, inspection, deployment and feedback)

22. CI is composed of:
connection to repository
build script
feedback means such as mail
process of integrating source code modification
(test, inspection, deployment and feedback)

23. CI is composed of:
connection to repository
build script
feedback means such as mail
process of integrating source code modification
(test, inspection, deployment and feedback)

24. "Build" in CI means
a series of processes
rather than
the so-called compilation
that is executed
at the time of committing

25. Merit

26. Reduce risk

27. Reduce routine

28. Ensure the source code
that can be deployed

29. Visualize
project

30. To be confident
for
products

31. Demerit

32. Load to build CI system
-> initial cost
Hardware cost for CI system
-> initial + running cost

33. Maintenance of CI system
-> running cost
Frequent build error
-> running cost

34. Question

35. Do you leave the problem you're having
now without any action?

36. How much cost have we taken
due to the problems that has occurred?

37. Act

38. What’s
Jenkins?

39. Merit

40. 1. Easy GUI
2. Easy to install
3. Lots of plugins
4. Leave execution logs

41. Demerit

42. 1. Frequent update
2. Difficult to understand
words for Jenkins

43. First of all
Install

44. CentOS
https://wiki.jenkins-ci.org/display/JENKINS/Installing
+Jenkins+on+RedHat+distributions

45. Download & install Jenkins
sudo wget -O /etc/yum.repos.d/jenkins.repo http://pkg.jenkins-
ci.org/redhat/jenkins.repo
sudo rpm --import http://pkg.jenkins-ci.org/redhat/jenkins-
ci.org.key
sudo yum install jenkins

46. Check java installation
java -version

47. Start
sudo service jenkins start

48. Access
http://hostname:8080

49. What can we do
with
Jenkins?

50. Realize CI environment

51. Customization
familiar
to our environment

52. Pra
Inspection
ctic
Plugin Plugin Plugin
Joined test scrum scrum scrum
Unit test agile agile agile
Deploy
e
Redmine
cakePHP
Github
git

53. Overview
of general system structure
that we’ve ever developed

54. Mainly
web application

55. cakePHP

58. Whole structure
"aiming for the time being"
with using Jenkins

59. Whole structure
Review
Build Repository
Merge
Build
Pull request
Detect

60. Whole structure
Build Repository
Push
Build Detect

61. Mus
t

62. Check inspection when committing

63. Run all unit test script and kick operation test
tool when committing

64. Coverage is reported as a result of test after
automated test

65. Build error is sent to developers automatically

66. Run all unit test script regularly

67. Inspection

68. coverage: Clover PHP Plugin
https://wiki.jenkins-ci.org/display/JENKINS/Clover+PHP+Plugin
coding convention: Checkstyle Plugin
https://wiki.jenkins-ci.org/display/JENKINS/Checkstyle+Plugin
duplicate code: DRY Plugin
https://wiki.jenkins-ci.org/display/JENKINS/DRY+Plugin
conplicated: PMD Plugin
https://wiki.jenkins-ci.org/display/JENKINS/PMD+Plugin

69. Unit test

70. Use PHPunit

71. Use bake

72. import test result in XML format that is
compatible with jUnit
xUnit Plugin
https://wiki.jenkins-ci.org/display/JENKINS/xUnit+Plugin

73. Register script to run 'AllTests'
./_lib/app/Console/cake test
-log-junit=./reports/unittest.xml
-coverage-html=./reports/coverage_html
-coverage-clover=./reports/coverage.xml
app AllTests

74. This prevents degrading
But “TDD” is required.

75. Operation test

76. Use Selenium
Do operation test with using Selenium manually first.

77. Use Selenium RC
to write test cases using PHPunit
it enables us to connect Selenium with Jenkins

78. Import test result in HTML format
seleniumhtmlreport Plugin
https://wiki.jenkins-ci.org/display/JENKINS/seleniumhtmlreport+Plugin

79. Wan
t

80. Deploy automatically on test server
after passing unit test

81. Check differences of commit on browser

82. Synchronize commit and ticket on redmine

83. Build test server automatically
when dividing branches

84. Nee
d?

85. Create documents automatically
Documents are not only for maintenance but
also one of the most important method to
share recognition between producer and
developer in offshore development.

86. In
summary

87. CI help us realize early feedback.

88. CI help us realize early feedback.
Early feedback enable us to find
bugs at the beginning of test
phase and decrease communication
gap.

89. CI help us realize early feedback.
Early feedback enable us to find bugs at the beginning of test phase
and decrease communication gap.
Automated test enable to decrease
degrade and load for test.

90. CI help us realize early feedback.
Early feedback enable us to find bugs at the beginning of test phase
and decrease communication gap.
Automated test enable to decrease degrade and load for test.
Jenkins provide us for comfortable
CI environment.

91. Thank you!!