はてなブックマーク

This project aims to develop a pull request Job Plugin. Users should be able to configure job type using YAML file placed in root directory of the Git repository being the subject of the pull request. The plugin should interact with various platforms like Bitbucket, Github, Gitlab, etc whenever a pull request is created or updated. Plugin detects the presence of certain types of the report at conv

Lately, perhaps subtle but exciting changes are starting to happen in the Jenkins project. The past few weeks have seen the birth of two new initiatives in Jenkins: Jenkins Essentials and Jenkins X. Each is exciting in its own right, and I encourage interested parties to take a look at their goals and missions and participate in them. But in this post, I want to discuss why together these two dots

use of immutable container images for distributing software which are smaller, easier to work with and lead to cheaper infrastructure costs than VMs alone (approx 20% less on average) Kubernetes has become the defacto way of installing, upgrading, operating and managing containers at scale on any public or hybrid cloud 2018 is the year all the major public clouds, operating system vendors and PaaS

As Pipeline is adopted for more and more projects in an organization, common patterns are likely to emerge. Oftentimes it is useful to share parts of Pipelines between various projects to reduce redundancies and keep code "DRY" [1]. Pipeline has support for creating "Shared Libraries" which can be defined in external source control repositories and loaded into existing Pipelines. A Shared Library

Jenkins Pipeline includes built-in documentation and the Snippet Generator which are key resources when developing Pipelines. They provide detailed help and information that is customized to the currently installed version of Jenkins and related plugins. In this section, we’ll discuss other tools and resources that may help with development of Jenkins Pipelines. Jenkins can validate, or "lint", a

The Jenkins Developer Reference serves as a resource for all serious Jenkins users and developers alike to have one central place where they can look up and refer to for reliable and accurate information related to Jenkins development overall. While this Developer Reference is by no means completely exhaustive, we welcome any contributions to improve and enhance this document, so that everyone who

Back in May 2016 we announced our intent to rethink the Jenkins User experience with the Blue Ocean project and today the Jenkins project are pleased to announce the general availability of Blue Ocean 1.0. Blue Ocean is an entirely new, modern and fun way for developers to use Jenkins that has been built from the ground up to help teams of any size approach Continuous Delivery. Easily installed as

This section builds on the information introduced in Getting started with Pipeline and should be treated solely as a reference. For more information on how to use Pipeline syntax in practical examples, refer to the Using a Jenkinsfile section of this chapter. As of version 2.5 of the Pipeline plugin, Pipeline supports two discrete syntaxes which are detailed below. For the pros and cons of each, r

This is a guest post by Sam Van Oort, Software Engineer at CloudBees and contributor to the Jenkins project. 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/a

The regressions discovered after release have now been resolved and this post has been updated with the correct plugin version numbers.

Today I’m going to show you how easy it is to tune Jenkins Java settings to make your controllers more responsive and stable, especially with large heap sizes. Basics: -server -XX:+AlwaysPreTouch GC Logging: -Xloggc:$JENKINS_HOME/gc-%t.log -XX:NumberOfGCLogFiles=5 -XX:+UseGCLogFileRotation -XX:GCLogFileSize=20m -XX:+PrintGC -XX:+PrintGCDateStamps -XX:+PrintGCDetails -XX:+PrintHeapAtGC -XX:+PrintGC

This section builds on the information covered in Getting started with Pipeline and introduces more useful steps, common patterns, and demonstrates some non-trivial Jenkinsfile examples. Creating a Jenkinsfile, which is checked into source control [1], provides a number of immediate benefits: Code review/iteration on the Pipeline Audit trail for the Pipeline Single source of truth [2] for the Pipe

This chapter covers all recommended aspects of Jenkins Pipeline functionality, including how to: get started with Pipeline — covers how to define a Jenkins Pipeline (i.e. your Pipeline) through Blue Ocean, through the classic UI or in SCM, create and use a Jenkinsfile — covers use-case scenarios on how to craft and construct your Jenkinsfile, work with branches and pull requests, use Docker with P

This is a guest post by Liam Newman, Technical Evangelist at CloudBees. Most projects need more that just JUnit result reporting. Rather than writing a custom plugin for each type of report, we can use the HTML Publisher Plugin. I’ve found a Ruby project, hermann, I’d like to build using Jenkins Pipeline. I’d also like to have the code coverage results published with each build job. I could write

The following plugin provides functionality available through Pipeline-compatible steps. Read more about how to integrate steps into your Pipeline in the Steps section of the Pipeline Syntax page. For a list of other such plugins, see the Pipeline Steps Reference page. If the body throws an exception, mark the build as a failure, but nonetheless continue to execute the Pipeline from the statement

Synopsis This shows usage of a simple build wrapper, specifically the AnsiColor plugin, which adds ANSI coloring to the console output. // This shows a simple build wrapper example, using the AnsiColor plugin. node { // This displays colors using the 'xterm' ansi color map. ansiColor('xterm') { // Just some echoes to show the ANSI color. stage "\u001B[31mI'm Red\u001B[0m Now not" } }

It’s been almost three months since we’ve released Jenkins 2.0, the first ever major version upgrade for this 10 year old project. The 2.x versions since then has been adopted by more than 20% of the users, but one segment of users who haven’t seen the benefits of Jenkins 2 is those who has been running LTS releases. But that is no more! The new version of Jenkins LTS release we just released is 2

Upgrade Spring Security from 5.8.12 to 5.8.13. Spring Security 5.8.13 includes 19 fixes and improvements. Spring Security 5.8.13, pull 9398 Upgrade Spring Framework from 5.3.36 to 5.3.37. Spring Framework 5.3.37 includes 5 fixes and improvements. Spring Security 5.3.37, pull 9385 Upgrade bundled plugins. pull 9386, pull 9419, pull 9439, pull 9444, pull 9429, pull 9464 Upgrade Commons FileUpload fr

The following plugins offer Pipeline-compatible steps. Each plugin link offers more information about the parameters for each step. Read more about how to integrate steps into your Pipeline in the Steps section of the Pipeline Syntax page.

Save up to 90% of CI cost on AWS with Jenkins and EC2 Spot Fleet Earlier this year, we published a case study on how Lyft has used Amazon EC2 Spot instances to save 75% on their continuous delivery infrastructure costs by simply changing four lines of code. Several other EC2 customers like Mozilla have also reduced costs of their continuous integration, deployment and testing pipelines by up to 90

In recent years developers have become rapidly attracted to tools that are not only functional but are designed to fit into their workflow seamlessly and are a joy to use. This shift represents a higher standard of design and user experience that Jenkins needs to rise to meet. We are excited to share and invite the community to join us on a project we’ve been thinking about over the last few month