Child pages
  • Home
94 more child pages
Skip to end of metadata
Go to start of metadata

Jenkins' real top page lives in and link to three pages in the Wiki


Do you blog about Jenkins? Do you have any interesting URL to share with Jenkins community? Check out our News Aggregator.

Introducing Tracy Miranda as the CloudBees Open Source Program Lead
I’m Tracy Miranda, and I’m really excited to have joined CloudBees this month leading the open source program. CloudBees’ contributions to Jenkins include developing Pipeline and Blue Ocean, staffing the infrastructure team, advocacy and events work, as well as security efforts. My focus is on making sure there is a great relationship between the Jenkins community and CloudBees, which means strong communication, help get traction on things the community wants, and generally working to make Jenkins and the community thrive and stay awesome in an ever-changing tech landscape. Here’s a little background on me: I come from an electronics/EDA background but...
When using tags in Jenkins Pipeline
One common pattern for automated releases I have seen and used relies on Git tags as the catalyst for a release process. The immutable nature of releases and the immutable nature of tags can definitely go hand in hand, but up until few months ago Jenkins Pipeline was not able to trigger effectively off of Git tags. In this post I want to briefly share how to use tags to drive behaviors in Jenkins Pipeline. Consider the following contrived Jenkinsfile, which contains the three basic stages of Build, Test, and Deploy: pipeline { agent any stages { ...
Automatic deployment of “incremental” commits to Jenkins core and plugins
A couple of weeks ago, Tyler mentioned some developer improvements in Essentials that had been recently introduced: the ability for builds to get deployed automatically to an “Incrementals” Maven repository, as described in JEP-305. For a plugin maintainer, you just need to turn on this support and you are ready to both deploy individual Git commits from your repository without the need to run heavyweight traditional Maven releases, and to depend directly on similar commits of Jenkins core or other plugins. This is a stepping stone toward continuous delivery, and ultimately deployment, of Jenkins itself. Here I would like to peek behind the curtain a bit at how we did this, since the solution...
Security updates for Jenkins core and plugins
We just released security updates to Jenkins, versions 2.121 and 2.107.3, that fix multiple security vulnerabilities. Additionally, we announce previously published security issues and corresponding fixes in these plugins: Black Duck Hub Groovy Postbuild Gitlab Hook (fix unreleased) For an overview of what was fixed, see the security advisory. For an overview on the possible impact of these changes on upgrading Jenkins LTS, see our LTS upgrade guide. Subscribe to the jenkinsci-advisories mailing list to receive important notifications related to Jenkins security....
Jenkins X: Announcing CVE docker image analysis with Anchore
Anchore provides docker image analysis for user defined acceptance policies to allow automated image validation and acceptance. As developers we would like to know if a change we are proposing introduces a Common Vulnerability and Exposure (CVE). As operators we would like to know what running applications are affected if a new CVE is discovered. Now in Jenkins X pipelines, if we find an Anchore engine service running we will add the preview and release images to be analyzed. This means we can look at any environment including previews (created from Pull Requests) to see if your application contains a CVE. Upgrade Start by checking your current Jenkins X...

  • No labels

1 Comment

  1. Issues reported here will almost certainly not been noticed or fixed.
    Please try the users alias to get help, and file an issue if it is determined to be a bug.