TDC2016SP - Trilha DevOps Java
Download as PPTX, PDF1 like340 views
This document discusses continuous integration with Jenkins. It begins with an introduction of the presenter and defines continuous integration. It then covers planning a CI strategy in Jenkins, including configuring build organization, access control, notifications and dependencies. The document demonstrates setting up Jenkins, including creating projects, configuring builds, and viewing build outputs like logs, history and changes. It shows Jenkins' capabilities for integrating source control, running tests, and monitoring build status across projects.
TDC2016SP - Trilha DevOps Java
- 1. DEVOPS JAVA Continuous Integration with Jenkins Bruno Tinoco 07.07.2016
- 2. AGENDA 1. Introduction 2. CI Strategy 3. Jenkins setup 4. Demo
- 3. GFT Group 03.09.2015 3 Who I am and What I do INTRODUCTION GFT Group is a business change and technology consultancy trusted by the world’s leading financial services institutions bringing together advisory, creative and technology capabilities with innovation culture and specialist knowledge of the finance sector. Bruno Tinoco Father and Java Developer with more than 15 years of software development experience using the JavaEE platform for different companies from Financial to Travel and Distribution industries. Currently working as a Software Engineer at GFT Group for DeustcheBank projects. Previously I worked as IT Architect at IBM GBS projects. Almost 5 years working with continuous integration automation for projects using tools like Teamcity, Continuum, Harvest and Jenkins. Follow us https://twitter.com/gft_br https://twitter.com/brunocrt
- 4. GFT Group 03.09.2015 4 CI is about Software Quality INTRODUCTION Improved Software Quality Process (SDLC) Automation (Software building) Integration (Process, People and Support Softwares) Standardization Agile Devops culture
- 5. GFT Group 03.09.2015 5 Plan your builds Build organization How many build configurations (Project, Module, User defined) Build types (Snapshots/Release) Access control (Devops team, Developers) Notification (Email, Instant message, Dashboard) Build Configuration Repositories (SVN, Git, Nexus) Build dependencies (Compilers, Utilities, Code analysis) Third party tools (Sonar, uDeploy, Octopus, Docker) Deployment machines (Unix, windows, cloud) Build Times Build triggers (commit, hour, nightly, manually) Deploy conditions (Tests passing, Promote) CI STRATEGY
- 6. GFT Group 03.09.2015 6 What is Jenkins? JENKINS SETUP Open Source Continuous Integration/Delivery platform (former Hudson) Developed in Java but supports different build languages (Java, .NET, PHP...) Runs in Unix and Windows operating systems, also on Cloud More than 1k plugins (build, test, integration, deploy, reports) Extensible/Customisable (build your own plugins) Large and active community Used by many large companies
- 7. GFT Group 03.09.2015 7 Operational Model JENKINS SETUP SOURCE CODE SERVER
- 8. GFT Group 03.09.2015 8 Build Status JENKINS SETUP Build Status icons used by jenkins to measure build stability
- 10. GFT Group 03.09.2015 10 Jenkins Main Screen DEMO
- 11. GFT Group 03.09.2015 11 Jenkins Setup DEMO
- 12. GFT Group 03.09.2015 12 Jenkins Configuration (System) DEMO
- 13. GFT Group 03.09.2015 13 Create new Project (Job) DEMO
- 14. GFT Group 03.09.2015 14 Project Configuration (Job) DEMO
- 15. GFT Group 03.09.2015 15 Main Project Screen (Job) DEMO
- 16. GFT Group 03.09.2015 16 Build Console Output (Logs) DEMO
- 17. GFT Group 03.09.2015 17 Build History and Last Results DEMO
- 18. GFT Group 03.09.2015 18 Build Changes (Commits) DEMO
- 19. GFT Group 03.09.2015 19 Build Status (All projects) DEMO
- 20. Thank you Bruno.tinoco@gft.com Senior Software Engineer GFT Brasil
Editor's Notes
- #5: Automation is key element, DBConvertibles Case, Delivery in each 2 months The first step to reach continuous delivery is implement continuous integration process