Categories
Bibliography DevOps Java Kubernetes Software Engineering Spring Framework

Continuous Delivery for Java Apps: Build a CD Pipeline Step by Step Using Kubernetes, Docker, Vagrant, Jenkins, Spring, Maven and Artifactory – B078B3FJ7J, 2017

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

Fair Use Source:

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

Categories
Bibliography DevOps DevSecOps-Security-Privacy Django Web Framework Python Software Engineering

B074HXXXLS

See: Test-Driven Development with Python: Obey the Testing Goat: Using Django, Selenium, and JavaScript 2nd Edition

Fair Use Source:

Categories
Bibliography DevOps DevSecOps-Security-Privacy Python Software Engineering

B0773VRHWT

See: Python Testing with pytest: Simple, Rapid, Effective, and Scalable 1st Edition

Fair Use Source:

Categories
Bibliography DevOps DevSecOps-Security-Privacy Python Software Engineering

B00LJV2GXI

See: Testing Python: Applying Unit Testing, TDD, BDD and Acceptance Testing 1st Edition

Fair Use Source:

Categories
DevOps Software Engineering

Acceptance Testing

acceptance testing – “An acceptance test confirms that an story is complete by matching a user action scenario with a desired outcome.” Fair Use Source: 809137

In engineering and its various subdisciplinesacceptance testing is a test conducted to determine if the requirements of a specification or contract are met. It may involve chemical testsphysical tests, or performance tests.

In systems engineering, it may involve black-box testing performed on a system (for example: a piece of software, lots of manufactured mechanical parts, or batches of chemical products) prior to its delivery.[1]

In software testing, the ISTQB defines acceptance testing as:

Formal testing with respect to user needs, requirements, and business processes conducted to determine whether a system satisfies the acceptance criteria [2] and to enable the user, customers or other authorized entity to determine whether to accept the system.— Standard Glossary of Terms used in Software Testing[3]:2

Acceptance testing is also known as user acceptance testing (UAT), end-user testing, operational acceptance testing (OAT), acceptance test-driven development (ATDD) or field (acceptance) testing. Acceptance criteria are the criteria that a system or component must satisfy in order to be accepted by a user, customer, or other authorized entity.[4]

smoke test may be used as an acceptance test prior to introducing a build of software to the main testing process.[not verified in body]