![ļ¼ Continuous Integration [HUDSON]
ļ¼ Automated Polling [HUDSON ļ³ SVN]
ļ¼ Automated Build [HUDSON ļ³ SVN ļ³ MAVEN]
ļ¼ Automated Test [HUDSON ļ³ SVN ļ³ MAVEN ļ³ UTPLSQL]
ļ¼ Automated Code Analysis [HUDSON ļ³ SVN ļ³ MAVEN ļ³ UTPLSQL ļ³ SONAR]
Demonstration
JENKINS ļ§ļØ SVN ļ§ļØ MAVEN ļ§ļØ UTPLSQL ļ§ļØ SONAR
Summary](https://image.slidesharecdn.com/continuousintegration-general-150224040642-conversion-gate02/85/Continuous-Integration-Oracle-Database-Objects-18-320.jpg)
Continuous Integration - Oracle Database Objects
- 1. Oracle Database Objects Continuous Integration
- 2. āŖ Working Methods āŖ Change ļØ Pain ļØ Risks āŖ Continuous Integration āŖ The Big Picture āŖ The Toolbox āŖ Demonstration ļØ Feedback Agenda
- 4. Change is Permanent Incremental Design Development TestingDeployment Delivery Requirement Changes Distributed Team Manual Test Executions Integration Request for Re-Deployment
- 5. Change ļØ Pain Reiteration Redeployment Revalidation
- 6. Pain ļØ Risks Effort Time to Deliver Cost
- 7. Continuous Integration Build and deliver software more rapidly by eliminating pain points āContinuous Integration doesnāt get rid of bugs, but it does make them easier to find and removeā ā Martin Fowler, Chief Scientist, ThoughtWorks
- 8. Continuous Integration ļIntegrate at least Daily ļ§ Continuous Integration (CI) is a development practice ļ§ Each Check-in is verified by an automated build ļ§ Integrating regularly helps to detect errors quickly ļ¼Reduces Issues with Distributed Team Environment ļ¼Reduces Integration Issues
- 9. Continuous Integration ļSolve Problems Quickly ļ§ No more long waiting period for results ļ§ Increase visibility which enables greater communication ļ§ Spend less time debugging and more time adding features ļ§ Proceed in the confidence youāre building on a solid foundation ļ§ Stop waiting to find out if your codeās going to work ļ¼Reduces Time/Effort consumption by Manual Test Executions ļ¼Reduces Time/Effort involved in Redeployment
- 10. Continuous Integration ļPrinciples and Practices ļ¼The Practices ļ¼How to do it ? ļ§ Maintain a single source repository ļ§ Automate the build ļ§ Make your build self-testing ļ§ Every commit should build on an integration machine ļ§ 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
- 11. Overview Commit Code Version Control CI Server Feedback Mechanism Feedback Mechanism Development Team The Big Picture
- 12. POLL ANALYZE RESULTS RESULTS CI ServerVersion Control Feedback Mechanism Feedback Mechanism CommitChanges CommitChanges BUILD SUCCESS BUILD TEST DEPLOY The Big Picture BUILD FAILURE
- 13. CI Server Build & Deploy Code Version Control Unit Test Framework Code Quality The Toolbox
- 14. Why Jenkins? ļ¼ Led by Developers for Developers ļ¼ Governance and Community ļ¼ Stability ļ¼ Primary platform for Plug-ins ļ¼ Cloud-Enabled Jenkins, a continuous build tool, enables teams to focus on their work by automating the build, artifact management and deployment process
- 15. Maven helps a developer to comprehend the complete state of a development effort in the shortest period of time Why Maven? ļ¼ Making the build process easy ļ¼ Providing a uniform build system ļ¼ Controls the entire Build, Test & Deployment phase of CI Setup ļ¼ Change Log Documents ļ¼ Unit Test Reports ļ¼ Keep your test source code separate ļ¼ Easy ways to update ļ¼ Easy way to install new plugins
- 16. Four Steps for using UTPLSQL ļ¼ Install UTPLSQL ļ¼ Identify the test cases for a program ļ¼ Build a Test Package ļ¼ Run your test Why utPLSQL? utPLSQL is a unit testing framework for programmers using Oracle's PL/SQL language and allows the automated testing of packages, functions and procedures
- 17. CommentsStandards Design Complexity BugsCoverage Duplication Why SonarQube ļ¼ Code Analysers ļ¼ Reporting Tools ļ¼ Defect Hunting Modules ļ¼ Time Machine ļ¼ Extended Functionality by Plug-in(s) āOne-Shop-Stop for Source Code Quality Managementā
- 18. ļ¼ Continuous Integration [HUDSON] ļ¼ Automated Polling [HUDSON ļ³ SVN] ļ¼ Automated Build [HUDSON ļ³ SVN ļ³ MAVEN] ļ¼ Automated Test [HUDSON ļ³ SVN ļ³ MAVEN ļ³ UTPLSQL] ļ¼ Automated Code Analysis [HUDSON ļ³ SVN ļ³ MAVEN ļ³ UTPLSQL ļ³ SONAR] Demonstration JENKINS ļ§ļØ SVN ļ§ļØ MAVEN ļ§ļØ UTPLSQL ļ§ļØ SONAR Summary