CI, CD and Jenkins 2
•
6 likes•1,737 views
Continuous Integration and Continuous Delivery with Jenkins 2.0.
Recommended
More Related Content
Viewers also liked
Viewers also liked (11)
Similar to CI, CD and Jenkins 2
Similar to CI, CD and Jenkins 2 (20)
Recently uploaded
Recently uploaded (20)
CI, CD and Jenkins 2
- 2. Who Am I? • beta@cht.com.tw • You will find me here https://github.com/tan9 http://stackoverflow.com/users/3440376/tan9 • An experienced CI adaptor • Hudson: Mid 2009 – February 2011 • Jenkins: February 2011 – present 2
- 3. Before We Get Started… • Join the channel: http://bit.do/jenkins-training • Or direct link: https://gitter.im/tan9/jenkins-training • Sign in using your GitHub account • Or sign up right now! 3
- 6. 6
- 7. DevOps 7Image by Rajiv.Pant derivative work: Wylve / CC BY 3.0 https://commons.wikimedia.org/wiki/File:Devops.svg
- 9. Immutable Infrastructure 9Josha Stella, Immutable Infrastructure: Considerations for the Cloud and Distributed Systems, 2016, O’Reilly https://fugue.co/assets/docs/Immutable_Infrastructure_Fugue.pdf
- 14. Continuous What? • Build • Test • Unit tests, integration tests… • Analysis • Feedback • Publish • Deploy • ... most tedious things! 14
- 15. What To Be Integrated? • People • Code • Environment • Report • Thought • ... everything valuable! 15
- 17. CI Practices • Maintain a single source repository • Automate the build • Make your build self-testing • Every commit should build on an integration machine • Keep the build fast • Test in a clone of the production environment • Make it easy for anyone to get the latest executable • Everyone can see what’s happening • Automate deployment Continuous Integration | ThoughtWorks https://www.thoughtworks.com/continuous-integration 17
- 18. Power Tools 18Why Developers <3 CI: A Guide to Loving Continuous Integration by Rebel Labs, 2013 http://zeroturnaround.com/rebellabs/rebel-labs-report-why-devs-love-ci-a-guide-to-loving-continuous-integration/ CI Servers Build Automation Tools Artifact Repositories Test Frameworks Code Analysis
- 19. Team Responsibilities • Check in frequently • Don’t check in broken code • Don’t check in untested code • Don’t check in when the build is broken • Don’t go home after checking in until the system builds 19Continuous Integration | ThoughtWorks https://www.thoughtworks.com/continuous-integration
- 27. Personal Information • Baby of Kohsuke Kawaguchi ( ) • In a past life named Hudson 27
- 29. Popularity (as of 2016/06) • Total Jenkins installation 136,078 • Total nodes: 464,273 3.41 nodes per installation • Total jobs 8,858,054 65.56 jobs per installation 29Jenkins infra-statistics http://stats.jenkins.io/jenkins-stats/
- 30. Terminology Term Description Job/Project Runnable tasks that are controlled / monitored by Jenkins. Build Result of one run of a Project. Artifact Slave Slaves are computers that are set up to build projects for a master. Node Refer to all machine that are part of Jenkins grid, slaves and master. Executor Separated stream of builds to be run on Node in parallel. Workspace Disposable directory on Node used as a working directory for building. Publisher Part of the build process other than compilation. A publisher may report stable or unstable result depending on the result of its processing. 30
- 31. Build Status • Stable Build • A build is stable if it was built successfully and no publisher reports it as unstable. • Unstable Build • A build is unstable if it was built successfully and one or more publishers report it unstable. • Failed Build • A build is broken if it failed during building. That is, it is not successful. 31
- 32. Running Jenkins • Download • https://jenkins.io/ • Set environment variable (optional) (default path: ~/.jenkins) • Run 32 java -jar jenkins.war [--httpPort=8080] Starting and Accessing Jenkins https://wiki.jenkins-ci.org/display/JENKINS/Starting+and+Accessing+Jenkins JENKINS_HOME=/home/to/jenkins
- 33. 33 ... Jul 27, 2016 4:59:14 PM jenkins.install.SetupWizard init INFO: ************************************************************* ************************************************************* ************************************************************* Jenkins initial setup is required. An admin user has been created and a password generated. Please use the following password to proceed to installation: 9fa65e05a58c4e9c8e6fc4288dfb6c32 This may also be found at: /home/to/jenkins/secrets/initialAdminPassword ************************************************************* ************************************************************* ************************************************************* ...
- 34. 34
- 35. 35
- 36. 36
- 37. 37
- 38. Freestyle Project Configuration • Source Code Management • Build Triggers • Build Environment • Build • Post-Build Actions 38
- 39. Maven Project Configuration • Source Code Management • Build Triggers • Build Environment • Build • Pre Steps • Build • Post Steps • Build Settings • Post-Build Actions 39
- 40. MultiConfiguration Project Configuration • Source Code Management • Build Triggers • Configuration Matrix • Build Environment • Build • Post-Build Actions 40
- 42. Jenkins Grid 42
- 44. Agent Launch Methods • Via Java Web Start • The agent need not be reachable from the master. • Via execution of command on the master • Via SSH for agents on Unix machines • The slave needs to be reachable from the master, and you will have to supply an account that can log in on the target machine. • Control this Windows slave as a Windows service • Starts a Windows slave by a remote management facility built into Windows. 44
- 45. Labeling Nodes • Grouping nodes by • O.S.: windows, linux, macos… • Architecture: x86, x64… • Capability: docker, jboss-eap… • What’s meaningful to you • Restrict project run node by Label Expression 45 postgres && !vm && (linux || freebsd)
- 47. Pipeline Script 47 node { // Mark the code checkout 'stage'.... stage 'Checkout' // Get some code from a GitHub repository git url: 'https://github.com/jglick/simple-maven-project-with-tests.git' // Get the maven tool. // ** NOTE: This 'M3' maven tool must be configured // ** in the global configuration. def mvnHome = tool 'M3' // Mark the code build 'stage'.... stage 'Build' // Run the maven build sh "${mvnHome}/bin/mvn -Dmaven.test.failure.ignore clean package" step([$class: 'JUnitResultArchiver', testResults: '**/target/surefire-reports/TEST-*.xml']) }
- 48. 48
- 50. s/green/blue/g • It's not for color blind users. • It's all about (influenced by ): • Green Balls Plugin • https://wiki.jenkins- ci.org/display/JENKINS/Green+Balls 50 青Cyan #00FFFF “Why does Jenkins have blue balls?” on 2012-03-13 by R. Tyler Croy https://jenkins.io/blog/2012/03/13/why-does-jenkins-have-blue-balls/
- 51. • Gravatar - Globally Recognized Avatar • Register your own avatar • at https://en.gravatar.com/ • Make it easier to identify one 51
- 52. Static Code Analyses 52 • Checkstyle • DRY • FindBugs • PMD • Compiler Warnings • Task Scanner • TODO, FIXME, XXX...
- 53. Plugins Available • FindBugs Plugin • Checkstyle Plugin • PMD Plugin • DRY Plugin • JaCoCo Plugin • Warnings Plugin 53
- 55. SCM Sync Configuration • Keep sync'ed configurations with a SCM repository. • Track changes (and author) made on every file with commit messages. 55
- 59. 59