Response time is paramount for a CI/CD system. In this session, you will see how a few best practices in constructing pipelines can yield faster turnaround times and reduced resource use. We'll also run through plugins and tools to analyze and visualize performance, including the Pipeline Stage View plugin.
Pipeline is quickly establishing itself as the direction that Jenkins jobs are going, enabling the definition of a complete CD pipeline in a single job; Pipeline as Code via the "Jenkinsfile"; job durability across master restarts; and more. I'll be talking here about the next evolution for Pipeline: a simple, declarative model to define your Pipelines with no need to write scripts.
Pipeline as Code revolutionized how continuous delivery pipelines are defined in Jenkins by checking in the Pipeline as a 'Jenkinsfile' in your repository instead of storing the definition locally in Jenkins. This becomes especially useful when leveraging the direct integrations Jenkins has with Github and Bitbucket.
With the introduction of the Pipeline plugin, users now can implement a project's entire build/test/deploy pipeline in a Jenkinsfile and store that alongside their code, treating their pipeline as another piece of code checked into source control.
Jenkins - Continuous Delivery for every team
Published on 2016-10-16 by Patrick Wolf Recently the Pipeline team began making several changes to improve the stage step and increase control of concurrent builds in Pipeline. Until now the stage step has been the catch-all for functionality related to the flow of builds through the Pipeline: grouping build steps into visualized stages, limiting concurrent builds, and discarding stale builds.