Download to read offline
![(?:(?:"|'|]|}||d|(?:nan|infinity|true|false|null|undefined| symbol|math)|`|-|+)+[)]*;?((?:s|-|~|!|{}||||+)*.*(?:.*=.*)))](https://image.slidesharecdn.com/devopstoolsforjavadevelopersv2-210129102654/75/DevOps-Tools-for-Java-Developers-v2-28-2048.jpg)
![(?:(?:"|'|]|}||d|(?:nan|infinity|true|false|null|undefined| symbol|math)|`|-|+)+[)]*;?((?:s|-|~|!|{}||||+)*.*(?:.*=.*)))](https://image.slidesharecdn.com/devopstoolsforjavadevelopersv2-210129102654/75/DevOps-Tools-for-Java-Developers-v2-29-2048.jpg)
Uploaded byStephen Chin
DevOps Tools for Java Developers v2
The document discusses essential DevOps tools for Java developers, emphasizing the importance of version control systems, continuous integration and deployment, and security scanning. It outlines various workflows like git-flow, GitHub flow, and GitLab flow, highlighting their strategies for branching and merging. The document stresses that as companies become more software-centric, managing security vulnerabilities is crucial.
DevOps Tools for Java Developers v2
- 1. DevOps Tools forJava Developers Stephen Chin @steveonjava VP of Devrel @JFrog
- 2. 2 HOW I PICTUREDMYSELF DURING THE PANDEMIC
- 3. 3 HOW I ACTUALLYLOOK DURING THE PANDEMIC
- 4. Source Code Repository Package ManagerSecurity Scanner Continuous Integration Continuous Delivery Single Source of Truth Build and test on every integration Full bill of materials and binary history for traceability Deep scanning of dependencies and containers Distribution and automated deployment to the edge and beyond
- 6. Evolution of VersionControl Systems • 1st Generation – Locking • SCCS, RCS • 2nd Generation – Optimistic Locking • CVS, Subversion • 3rd Generation – Distributed • Git, Mercurial
- 7. Adoption of MajorVCS Systems Source: Google Trends
- 8. How Distributed versioncontrol works
- 9. Usage of developertools https://insights.stackoverflow.com/survey/2020
- 10. GIT-FLOW • Development Branches: Branchper feature • Merge Strategy: No fast forward merges • Rebasing History: No rebasing • Release Strategy: Separate release branch
- 11. GITHUB FLOW • DevelopmentBranches: Branch per feature • Merge Strategy: No fast forward merges • Rebasing History: No rebasing • Release Strategy: No separate release branches GITLAB FLOW • Development Branches: Branch per feature • Merge Strategy: Open ended • Rebasing History: Optional • Release Strategy: Separate release branches
- 12. Source Code Repository Package ManagerSecurity Scanner Continuous Integration Continuous Deployment Single Source of Truth Build and test on every integration Full bill of materials and binary history for traceability Deep scanning of dependencies and containers Automated deployment to the edge and beyond
- 15. Source Code Repository Package ManagerSecurity Scanner Continuous Integration Continuous Delivery Single Source of Truth Build and test on every integration Full bill of materials and binary history for traceability Deep scanning of dependencies and containers Distribution and automated deployment to the edge and beyond
- 16. “AS EVERY COMPANYBECOME A SOFTWARE COMPANY, SECURITY VULNERABILITIES ARE THE NEW OIL SPILLS”
- 21. Source Code Repository Package ManagerSecurity Scanner Continuous Integration Continuous Delivery Single Source of Truth Build and test on every integration Full bill of materials and binary history for traceability Deep scanning of dependencies and containers Distribution and automated deployment to the edge and beyond
- 22.
- 25.
- 28.
- 29.
- 30.
- 31.
- 33. Source Code Repository Package ManagerSecurity Scanner Continuous Integration Continuous Delivery Single Source of Truth Build and test on every integration Full bill of materials and binary history for traceability Deep scanning of dependencies and containers Distribution and automated deployment to the edge and beyond
- 34.
- 35. ARTIFACTORY DISTRIBUTION XRAY CI Servers RemoteRepositories Build Tools/Dependency Managers QA/QC Provisioning Tools 1 2 3 4 5 6 7 8 10 10 Version Control System Take VCS changes Commit the changes Dev. Team Declare new dependencies Resolve dependencies Resolve dependencies Resolve dependencies Deploy module Artifacts and Buildinfo BOM Contribute Metadata Deploy to Production Roll out for Internal Distribution Production Servers Build MSBuild DRONE External Data Sources Updat e ARTIFACTORY EDGE ARTIFACTORY EDGE ARTIFACTORY EDGE Analyze Build Tools/Dependency Managers 9 MSBuild
- 36.