In the previous posts, I’ve shown how to set up your Jenkins Shared Library, create Custom Pipeline Steps in it, set up the test frameworks, run complete pipelines from your Library and write tests for your Custom Pipeline Steps. Now the time has come to test the full...
After explaining how to set up your Shared Library, how to build it and how to run complete pipelines from this Library, it is time to create tests for the behaviour of the Library itself. This post is part of a Series in which I elaborate on my best practices for...
As shown in the previous blog post, Jenkins enables you to write your own pipeline code, which can be shared among all pipelines in your Jenkins instance. This post is part of a Series in which I elaborate on my best practices for running Jenkins at scale which might...
Pipelines in Jenkins, especially the declarative kind, can be very powerful and expressive at the same time. As a caveat, it is also very easy to get overly verbose by (mis)using the script-tag to write all business logic not provided by Jenkins by default or by a...
Being able to test your Jenkins pipeline Shared Library code, and therefore minimising the risk of pushing new pipelines or functionality to your Production instance, is vital for organisations using Jenkins at scale. Having your teams impeded by a ‘simple’ change in...
Versnel je reis naar de cloud en zet koers op applicatie modernisatie. Meld je nu aan voor het event en leer meer over de best practices!
Fijn dat we je op de hoogte mogen houden!
We gebruiken cookies om ervoor te zorgen dat onze website zo soepel mogelijk draait. Als je doorgaat met het gebruiken van de website, gaan we er vanuit dat je ermee instemt.OkCookie statement
