Talk at the Mannheim Java User Group (MAJUG) Mannheim, 15.03.2017
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.
jenkins-pipes-infra - Infrastructure (i.e. a dockerized Jenkins) and overview for the Jenkins Pipes demo
Contribute to pipeline-model-definition-plugin development by creating an account on GitHub.
jenkins-datadog-plugin - A Jenkins plugin used to forward metrics, events, and service checks to an account at Datadog, automatically.
run-selector-plugin - Jenkins plugin for selecting a Run based on specific parameters
When Jenkins Pipeline was first created, Groovy was selected as the foundation. Jenkins has long shipped with an embedded Groovy engine to provide advanced scripting capabilities for admins and users alike. Additionally, the implementors of Jenkins Pipeline found Groovy to be a solid foundation upon which to build what is now referred to as the "Scripted Pipeline" DSL.
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.
Jenkins Community Survey Shows Jenkins Usage Increased 85%, Extends Further into Operations and Deployment
After active year for the Jenkins community, 2016 Jenkins Community Survey shows significant growth FOSDEM - The Jenkins project, comprised of a community of practitioners using Jenkins, today announced results from its annual Jenkins Community Survey, sponsored by CloudBees.
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.
For this post, I'm going to use the blog/add-declarative/html branch of my fork of the hermann project. I've set up a Multibranch Pipeline and pointed it at my repository the same as did it previous post. Also the same as before, I've set this Pipeline's Git configuration to automatically "Clean after checkout".
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.