Java Magazine, Mar/Apr 2018
Continuous Build Change request GA Build Pipeline for Dev Versions RC Build SCM Business Business Delivered change Dev Dev Dev Figure 2 The workflow pipelines that move a code change to a release build ORACLE COM JAVAMAGAZINE MARCH APRIL 2018 34 microservices and containers RC and finally a general availability GA version Major stakeholders include development Dev at the bottom of the first three columns a business representative Business or a software configuration management function SCM I discuss this scenario in more detail in the following sections The first stage is the developer workspace where developers design write and test code before checking the code changes into a version control system After checking the code in downstream Jenkins pipelines are triggered The continuous build of the second stage is just a fast running job to check whether the changes together with the existing code compile and whether some basic unit tests run successfully Continuous integration refers to these first two stages The next stage is the dev build for producing development versions This stage takes a meaningful set of commits and builds a working implementation of the product It passes through all the stages of build verification and creation of a deliverable in a container In my case this pipeline takes a Maven snapshot and derives a Maven based release packages the WAR file inspects the code I use SonarQube for static code analysis checks whether
You must have JavaScript enabled to view digital editions.
