Java CI-CD Java Continuous Delivery – Continuous Integration
See: Cloud Native Java: Designing Resilient Systems with Spring Boot, Spring Cloud, and Cloud Foundry, 1st Edition, Publisher : O’Reilly Media; 1st edition (September 19, 2017)
See also: Spring Bibliography, Spring Framework and Cloud Native
See: DevOps Tools for Java Developers: Best Practices from Source Code to Production Containers, 1st Edition, Publisher : O’Reilly Media; 1st edition (January 18, 2022)
With the rise of DevOps, low-cost cloud computing, and container technologies, the way Java developers approach development today has changed dramatically. This practical guide helps you take advantage of microservices, serverless, and cloud native technologies using the latest DevOps techniques to simplify your build process and create hyperproductive teams.
Stephen Chin, Melissa McKay, Ixchel Ruiz, and Baruch Sadogursky help you evaluate an array of options. The list includes source control with Git, build declaration with Maven and Gradle, CI/CD with CircleCI, package management with Artifactory, containerization with Docker and Kubernetes, and much more. Whether you’re building applications with Jakarta EE, Spring Boot, Dropwizard, MicroProfile, Micronaut, or Quarkus, this comprehensive guide has you covered.
Stephen Chin is Head of Developer Relations at JFrog and author of The Definitive Guide to Modern Client Development, Raspberry Pi with Java, and Pro JavaFX Platform. He has keynoted numerous Java conferences around the world including Devoxx, JNation, JavaOne, Joker, and Open Source India. Stephen is an avid motorcyclist who has done evangelism tours in Europe, Japan, and Brazil, interviewing hackers in their natural habitat. When he is not traveling, he enjoys teaching kids how to do embedded and robot programming together with his teenage daughter. You can follow his hacking adventures at: http://steveonjava.com/.
Melissa McKay is currently a Developer Advocate with the JFrog Developer Relations team. She has been active in the software industry 20 years and her background and experience spans a slew of technologies and tools used in the development and operation of enterprise products and services. Melissa is a mom, software developer, Java geek, huge promoter of Java UNconferences, and is always on the lookout for ways to grow, learn, and improve development processes. She is active in the developer community, has spoken at CodeOne, Java Dev Day Mexico and assists with organizing the JCrete and JAlba Unconferences as well as Devoxx4Kids events.
Ixchel Ruiz has developed software applications and tools since 2000. Her research interests include Java, dynamic languages, client-side technologies, and testing. She is a Java Champion, Groundbreaker Ambassador, Hackergarten enthusiast, open source advocate, JUG leader, public speaker, and mentor.
Baruch Sadogursky (a.k.a JBaruch) is the Chief Sticker Officer @JFrog (also, Head of DevOps Advocacy) at JFrog. His passion is speaking about technology. Well, speaking in general, but doing it about technology makes him look smart, and 19 years of hi-tech experience sure helps. When he’s not on stage (or on a plane to get there), he learns about technology, people and how they work, or more precisely, don’t work together.
He is a co-author of the Liquid Software book, a CNCF ambassador and a passionate conference speaker on DevOps, DevSecOps, digital transformation, containers and cloud-native, artifact management and other topics, and is a regular at the industry’s most prestigious events including DockerCon, Devoxx, DevOps Days, OSCON, Qcon, JavaOne and many others. You can see some of his talks at jfrog.com/shownotes
See: Continuous Delivery for Java Apps: Build a CD Pipeline Step by Step Using Kubernetes, Docker, Vagrant, Jenkins, Spring, Maven and Artifactory, Publisher : Leanpub (December 14, 2017)
See also: Spring Bibliography, Spring Framework and Cloud Native
This book will guide you through the implementation of the real-world Continuous Delivery using top-notch technologies. Instead of finishing this book thinking “I know what Continuous Delivery is, but I have no idea how to implement it”, you will end up with your machine set up with a Kubernetes cluster running Jenkins Pipelines in a distributed and scalable fashion (each Pipeline run on a new Jenkins slave dynamically allocated as a Kubernetes pod) to test (unit, integration, acceptance, performance and smoke tests), build (with Maven), release (to Artifactory), distribute (to Docker Hub) and deploy (on Kubernetes) a Spring Boot app to testing, staging and production environments implementing the Canary Release deployment pattern.
TABLE OF CONTENTS:
INTRODUCTION
Agile
Scrum
Scrum and Continuous Integration
Deployed vs Released
Scrum and Continuous Delivery
XP and Continuous Delivery
Automated Tests
Continuous Integration
Feature Branch
Continuous Delivery
Continuous Delivery Pipeline
Continuous Delivery vs Continuous Deployment
Canary Release
A/B Tests
Feature Flags
NOTEPAD APP: AUTOMATED TESTS, MAVEN AND FLYWAY
Pre-Requisites
The Notepad Application
Automated Tests
Unit Tests
Integration Tests
Acceptance Tests
Page Object
Distributed Acceptance Tests with Selenium-Grid
Smoke Tests
Performance Tests with Gatling.io
Apache Maven
Maven Snapshot vs Release
The Default Lifecycle and its Phases
Maven Repositories
Repository Manager (Artifactory)
Maven Plugins: Surefire and Failsafe
Maven Profile
Running Unit Tests
Running Integration Tests
Running Acceptance Tests
Running Smoke Tests
Running Performance Tests
Publish Artifacts to Artifactory with Maven
Publish a Snapshot to Artifactory
Publish a Release to Artifactory
The release:prepare Goal
The release:perform Goal
Flyway
DOCKER
Introduction to Docker
Difference Between Container and Image
Docker Hub
Create your Account
Official Docker Repositories
Image Tags
Non-Official Docker Images
Create a Repository, an Image and Push it to Docker Hub
Running Containers on Docker
Running Containers as Daemons
Container Clean Up
Naming Containers
Exposing Ports
Persistent Data with Volumes
Environment Variables
Docker Networking
Create a Bridge Network
Container Static IP Address
Linking Containers
Most Used Docker Commands
Images
Containers
Misc
Building Docker Images: Dockerfile
JENKINS: PIPELINE AS CODE AND CHATOPS
Jenkins Overview
Jenkins Concepts
Job (or Project)
Build
Artifact
Workspace
Executor
Plugin
Node, Master, and Agent (or Slave)
ChatOps
Create a Slack Workspace
Integrate Slack with Jenkins
Slack Notification Plugin
Use Hubot to Interact with Jenkins
Jenkins Pipeline
Declarative Pipeline vs Scripted Pipeline
Scripted Pipeline
Using Docker with Jenkins Pipelines
Running Docker from Within the Jenkins Container
Scaling Jenkins with Slaves
KUBERNETES
Why Kubernetes?
Set up a Kubernetes Cluster using Vagrant
Hands-on Introduction to Kubernetes
Kubernetes Concepts
Namespaces
Pods
Labels
Replica Sets
Services
Service Discovery using DNS
Service Discovery using Namespaces
Volumes
Handling External Configurations
Config Maps
Changing Logback Log Level at Runtime
Secrets
Using Secrets as Environment Variables
Using Secrets as Files from a Pod
Deployments
Readiness Probes
Liveness Probes
Canary Release
Kubernetes Architecture
Kubernetes Master Components
Etcd
API Server
Controller Manager
Scheduler
Kubernetes Node Components
Service Proxy
Kubelet
cAdvisor
Kubernetes Add-ons
Web UI (Dashboard)
Monitoring Kubernetes with Heapster, InfluxDB and Grafana
Web UI Overview
DNS
HANDS-ON PROJECT
APPENDICES
See: Continuous Delivery in Java: Essential Tools and Best Practices for Deploying Code to Production, 1st Edition, Publisher : O’Reilly Media; 1st edition (November 29, 2018)
“A DevOps toolchain is a set or combination of tools that aid in the delivery, development, and management of software applications throughout the systems development life cycle, as coordinated by an organization that uses DevOps practices.
Generally, DevOps tools fit into one or more activities, which supports specific DevOps initiatives: Plan, Create, Verify, Package, Release, Configure, Monitor, and Version Control.[1][2]” (WP)
“In software, a toolchain is the set of programming tools that is used to perform a complex software development task or to create a software product, which is typically another computer program or a set of related programs. In general, the tools forming a toolchain are executed consecutively so the output or resulting environment state of each tool becomes the input or starting environment for the next one, but the term is also used when referring to a set of related tools that are not necessarily executed consecutively.[3][4][5]
As DevOps is a set of practices that emphasizes the collaboration and communication of both software developers and other information technology (IT) professionals, while automating the process of software delivery and infrastructure changes, its implementation can include the definition of the series of tools used at various stages of the lifecycle; because DevOps is a cultural shift and collaboration between development and operations, there is no one product that can be considered a single DevOps tool. Instead a collection of tools, potentially from a variety of vendors, are used in one or more stages of the lifecycle.[6][7]” (WP)
Further information: DevOps
Plan is composed of two things: “define” and “plan”.[8] This activity refers to the business value and application requirements. Specifically “Plan” activities include:
A combination of the IT personnel will be involved in these activities: business application owners, software development, software architects, continual release management, security officers and the organization responsible for managing the production of IT infrastructure.
Create is composed of the building (see also build automation), coding, and configuring of the software development process.[8] The specific activities are:
Tools and vendors in this category often overlap with other categories. Because DevOps is about breaking down silos, this is reflective in the activities and product solutions.[clarification needed]
Verify is directly associated with ensuring the quality of the software release; activities designed to ensure code quality is maintained and the highest quality is deployed to production.[8] The main activities in this are:
Solutions for verify related activities generally fall under four main categories: Test automation , Static analysis , Test Lab, and Security.
Packaging refers to the activities involved once the release is ready for deployment, often also referred to as staging or Preproduction / “preprod”.[8] This often includes tasks and activities such as:
Release related activities include schedule, orchestration, provisioning and deploying software into production and targeted environment.[9] The specific Release activities include:
Solutions that cover this aspect of the toolchain include application release automation, deployment automation and release management.
Configure activities fall under the operation side of DevOps. Once software is deployed, there may be additional IT infrastructure provisioning and configuration activities required.[8] Specific activities including:
The main types of solutions that facilitate these activities are continuous configuration automation, configuration management, and infrastructure as code tools.[10]
Monitoring is an important link in a DevOps toolchain. It allows IT organization to identify specific issues of specific releases and to understand the impact on end-users.[8] A summary of Monitor related activities are:
Information from monitoring activities often impacts Plan activities required for changes and for new release cycles.
Version Control is an important link in a DevOps toolchain and a component of software configuration management. Version Control is the management of changes to documents, computer programs, large web sites, and other collections of information.[8] A summary of Version Control related activities are:
Information from Version Control often supports Release activities required for changes and for new release cycles.