First8 staat voor vakmanschap. Al onze collega’s zijn een groot aanhanger van Open Source en in het bijzonder het Java-platform. Wij zijn gespecialiseerd in het pragmatisch ontwikkelen van bedrijfskritische Java toepassingen waarbij integratie van systemen, hoge eisen aan beveiliging en veel transacties een belangrijke rol spelen. Op deze pagina vind je onze blogs.

How to start with declarative Jenkins pipelines

So, we have been using pipelines-as-code in Jenkins for a while now and we generally are using scripted pipelines, Groovy scripts that run in Jenkins. Very flexible, but it is missing something for me. While we were used to the webforms of Jenkins before pipelines, these constructs aren’t always available in scripted pipelines. Enter declarative pipelines. These are pipelines-as-code as … Lees verder How to start with declarative Jenkins pipelines

How to reuse pipelines with Jenkins Shared Libraries

As a continuous delivery engineer I really want software teams to work fast and safe, with ease and having fun. Happy teams are productive, learning and innovative teams. Authoring pipelines is an important aspect of a safe and smooth development cycle. Every new piece of code should be tried, tested, reworked and eventually (potentially) promoted for real use. However, there … Lees verder How to reuse pipelines with Jenkins Shared Libraries

The CDF is here! Why a continuous delivery foundation?

  March 12th 2019 a new vendor neutral foundation was created: the CDF! CDF is founded by Cloudbees and Google. For now the project has Jenkins (including the ‘jenkins-x’ project), Spinnaker (Netflix) and Tekton (kubernetes / google) on board and many companies as founding members. It was announced as definitive at FOSDEM in februari.   Some background on continuous delivery … Lees verder The CDF is here! Why a continuous delivery foundation?


Jenkins shared libraries: tested

Jenkins is a very neat tool to implement a continuous delivery process, mainly due to its flexibility. Sometimes it can be hard though to keep complexity low, and when that happens, (automated) tests become far more important. Jenkins should in fact be running tests that verify the scripts running tests, proving they actually work. Warning: this dog will chase its … Lees verder Jenkins shared libraries: tested

Strangling pipelines

Strangling pipelines This practical example is about the strangulation pattern, as explained by Martin Fowler here, applied to pipelines.   The situation Right after ditching the old manually managed Jenkins jobs, we were left with ‘simple’ but very lengthy procedural pipeline scripts. These scripts were then duplicated and slightly modified for each type of pipeline (because there’s always need for … Lees verder Strangling pipelines