Jenkins On GitHub

Re-Introducing Jenkins: Automated Testing with Pipelines - SitePoint

This article was peer reviewed by Christopher Thomas and Peter Nijssen. Thanks to all of SitePoint's peer reviewers for making SitePoint content the best it can be! As our applications become more complex - with Composer dependencies, Webpack build scripts, and per-environment variables - we inevitably reach a point where testing all of these different intricacies becomes slow and laborious, especially when you're tearing down and rebuilding the entire environment for each test.

jenkinsci/pipeline-model-definition-plugin

Contribute to pipeline-model-definition-plugin development by creating an account on GitHub.

jenkinsci/run-selector-plugin

run-selector-plugin - Jenkins plugin for selecting a Run based on specific parameters

Jenkins #1: Migrating to Pipelines

The MetaBrite dev team migrated most of their builds from Atlassian's Bamboo Cloud to Jenkins Pipelines in late 2016/early 2017. This is a series of blog posts about that experience. For three years, we used Atlassian's hosted Bamboo Cloud service to build and deploy most of our code.

Best Practices for Scalable Pipeline Code

Published on 2017-02-01 by Sam Van Oort Today I'm going to show you best practices to write scalable and robust Jenkins Pipelines. This is drawn from a combination of work with the internals of Pipeline and observations with large-scale users. Pipeline code works beautifully for its intended role of automating build/test/deploy/administer tasks.

Declarative Pipeline: Notifications and Shared Libraries

Published on 2017-02-15 by Liam Newman In the previous post, we converted a Scripted Pipeline to a Declarative Pipeline, adding descriptive stages and post sections. In one of those post blocks, we included a placeholder for sending notifications. In this blog post, we'll repeat what I did in " Sending Notifications in Pipeline but this time in Declarative Pipeline.