The Jenkins core release automation project has been delivering Jenkins weekly releases since Jenkins 2.232, April 16, 2020. The Linux repositories that deliver the weekly release were updated with new GPG keys with the release of Jenkins 2.232. Beginning with Jenkins LTS release 2.235.3, stable repositories will be signed with the same GPG keys that sign the weekly repositories. Administrators of Linux systems must install the new signing keys on their Linux servers before installing Jenkins 2.235.3. Debian/Ubuntu Update Debian compatible operating systems (Debian, Ubuntu, Linux Mint Debian Edition, etc.) with the command: Debian/Ubuntu # wget -qO - https://pkg.jenkins.io/debian-stable/jenkins.io.key | apt-key add - Red Hat/CentOS Update Red Hat compatible operating systems (Red Hat Enterprise Linux, CentOS, Fedora, Oracle Linux, Scientific Linux, etc.) with the command: Red Hat/CentOS # rpm --import https://pkg.jenkins.io/redhat-stable/jenkins.io.key Frequently Asked Questions What if I don’t update the repository signing key? Updates will be blocked by the operating system package manager (apt, yum, dnf) on operating systems that have not installed the new repository signing key. Sample messages from the operating system may look like: Debian/Ubuntu Reading package lists... Done W: GPG error: https://pkg.jenkins.io/debian-stable binary/ Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY FCEF32E745F2C3D5 E: The repository 'https://pkg.jenkins.io/debian-stable binary/ Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. Red Hat/CentOS Downloading packages: warning: /var/cache/yum/x86_64/7/jenkins/packages/jenkins-2.235.3-1.1.noarch.rpm: Header V4 RSA/SHA512 Signature, key ID 45f2c3d5: NOKEY Public key for jenkins-2.235.3-1.1.noarch.rpm is not installed Why is the repository signing key being updated? The original repository GPG signing key is owned by Kohsuke Kawaguchi. Rather than require that Kohsuke disclose his personal GPG signing key, the core release automation project has used a new repository signing key. The updated GPG repository signing key is used in the weekly repositories and the stable repositories. Which operating systems are affected? Operating systems that use Debian package management (apt) and operating systems that use Red Hat package management (yum and dnf) need the new repository signing key. Other operating systems like Windows, macOS, FreeBSD, OpenBSD, Solaris, and OpenIndiana are not affected. Are there other signing changes? Yes, there are other signing changes, though they do not need specific action from users. The jenkins.war file is signed with a new code signing certificate. The new code signing certificate has been used on weekly releases since April 2020.

Documentation is not glamorous, but it is goodness. — Thomas Otter Jenkins technical documentation is an important part of our project as it is key to using Jenkins well. Good documentation guides users and encourages good implementation choices. It is a crucial part of the user experience. In the recent Jenkins UI/UX hackfest, documentation was a specific track to improve the Jenkins user experience. We received many improvements from experienced Jenkins contributors and newcomers alike. Contributors from all around the world submitted pull requests for documentation on installing, managing, administering, and operating Jenkins. Documentation migration from Wiki The Jenkins Wiki pages have collected 15 years of experience and wisdom for Jenkins users. However, that experience and wisdom is intermixed with inaccurate, incomplete, and outdated information. The Jenkins Wiki migration project identified the 50 most accessed pages on the Jenkins wiki and created GitHub issues to track the migration of those pages to www.jenkins.io. This was our first large scale experiment using GitHub issues for documentation. The results have been overwhelmingly positive. Hackfest contributors added new sections to many documentation chapters, including: Using Jenkins Pipeline Managing Jenkins System Administration The Hackfest closed 19 of the wiki migration issues. Work is in progress on an additional 25 wiki migration issues. We’ve made great progress and look forward to even better results in the future. New contributors used the "good first issue" label very effectively. We started the Hackfest with most of the 25 "good first issues" unassigned and completed the Hackfest with 14 closed and 10 others in progress. We’ll provide more "good first issues" as we use the Jenkins Wiki migration to welcome new documentation contributors. Migrating plugin documentation Plugin documentation is also in transition. Since November 2019, plugins have been moving their documentation into the GitHub repository that hosts the plugin source code. This"documentation as code" approach allows plugin maintainers to include documentation improvements in the same pull requests that implement new capabilities. It assures that documentation changes are reviewed by the same maintainers who review and approve new capabilities. Hackfest participants submitted pull requests to migrate plugin documentation to GitHub. 10 plugin pull requests are in progress from the Hackfest. 5 plugin pull requests from the Hackfest have been already merged and are awaiting the release of the plugin. Chuck Norris uses documentation as code In the spirit of fun and adventure, Oleg Nenashev migrated the "Chuck Norris plugin" to GitHub documentation as code in a live Hackfest presentation May 26, 2020. Links to the recording, the plugin migration guide, and the export tool are available from"Migrating plugins to documentation-as-code". Documentation updates Jenkins works with other technologies to solve automation challenges in many different environments. We describe those environments in our"Solution Pages". As part of the Hackfest, we’ve started a series of improvements to the solution pages. The Docker solutions page now includes updated videos and a better page layout for easier reading and better navigation. Other solution pages will receive similar improvements in the future. System properties The global configuration of Jenkins can be modified at startup by defining Java properties. System properties can change system defaults and can provide compatibility "escape hatches" when a new default configuration might be incompatible with existing installations. Daniel Beck has improved the navigation and user experience of the system properties page as part of the Hackfest. It is now much easier to read and to reference, with embeddable links available with a mouse-over to the right of every property and labels that categorize and classify each property. Plugin site improvements During the Hackfest, Gavin Mogan has continued his efforts to improve the Jenkins Plugins Site so that users can easily access plugin changelogs and reported issues. Once this pull request is merged, it will greatly improve the experience of those Jenkins users who want to update plugins and look for documentation about what has changed in them and what are the possible issues they might experience. Example of the incoming UI for the Jira plugin: What’s next? There is still much to do in Jenkins documentation and we need your help to do it. There are many ways to participate in the Jenkins project, including documentation. See the contributing guidelines for detailed instructions. Join the documentation chat for personalized help and encouragement. The Jenkins project has been also accepted to Google Season of Docs this year. This open-source mentorship program brings together open source and technical writers communities for the benefit of both. We are looking for technical writers who are interested to contribute to the project in September-December 2020. It is a great opportunity to study Documentation-as-code tools and to learn more about contributing to open-source projects. You can find Jenkins project ideas and more information here.

One of the things we loved about going to developer conferences was meeting Jenkins users — newbies and old-timers alike — who are excited to talk about their projects and share tips on how to move forward using Jenkins. Since the coronavirus pandemic, we’re learning to rely more on new ways to gather, and it’s happening via Jenkins online meetups, GitHub collaborations, and Twitter threads, to name a few. It’s a significant change. But what hasn’t changed is the need to share stories about the things users have built, the solutions they’ve developed, and the excellent results they’re getting from some really innovative Jenkins implementations. Then we wondered, why isn’t anyone collecting these user stories and sharing them with the Jenkins community. Introducing Jenkins is the Way So we took the first step to record and archive all the great stuff everyone in our community is building with Jenkins. This way, Jenkins users old and new can come to an archive and search for Jenkins solutions for inspiration. We foresee a vast library of solutions from all around the world, solving a wide array of challenges in every industry imaginable. We decided to call this archive " Jenkins Is The Way" and host it at https://JenkinsIsTheWay.io. To aggregate all these stories, we built a simple online questionnaire so that Jenkins users can submit their own experience using this leading open source automation server. With so many plugins to support building, deploying, and automating your projects, we expect to see a vast collection of stories. We’ve already received a handful, including stories that illustrate how Jenkins Is The Way : to code your own release pipelines to cast magic of continuous delivery to understand and simplify your software lifecycle to accelerate automation in the cloud to facilitate day-to-day work Add your story. Show your Jenkins pride. Get our T-shirt Be an inspiration to the Jenkins community by sharing your Jenkins story. Just go to this link and fill out the form. We’ll ask you about your project’s goals, the technical challenges you overcame with Jenkins, and the solutions you created. It should take no more than 20-30 minutes to complete. We’ll clean it up for clarity and publish it on https://JenkinsIsTheWay.io. Once it’s part of our archive, we’ll send you our new 2020 Jenkins Is the Way t-shirt. And since the more, the merrier, please share this blog post with peers and colleagues. We want to hear everyone’s stories about the clever ways Jenkins is used to automate all that we need to do. Thanks and Acknowledgement Special thanks to abConsulting for creating and managing the https://JenkinsIsTheWay.io site and for reviewing, editing, and publishing the submitted stories. Thanks to the Jenkins Advocacy and Outreach SIG for their reviews and feedback. Thanks also to CloudBees for sponsoring the " Jenkins is the Way" program.

This is a speaker blogpost for a DevOps World | Jenkins World 2019 talk in Lisbon, Portugal Come join us at DevOps World | Jenkins World 2019 for " Thinking about Jenkins Security ", a talk about securing your Jenkins server. We’ll review the layers that secure Jenkins and describe techniques that you can use to protect your Jenkins server. Topics will include: The secure by default configuration that Jenkins provides Risks associated with reducing default security settings Authentication and authorization alternatives Using " least privilege" principles Jenkins credentials and trusted access to resources Software updates and Jenkins project security notices We’ll intermix descriptions of good practices with some security horror stories. The horror stories remind us of our mistakes; we will discuss how to detect them and how to prevent them. Come join us for the presentation in Lisbon! Slides

We’re pleased to announce the formation of the Jenkins Documentation Special Interest Group. The Docs SIG encourages contributors and external communities to create and review Jenkins documentation. See the Special Interest Group Overview for more details and plans. How can I help? The Jenkins Documentation SIG would love to have your help with: reviewing and fixing open bug reports reviewing Jenkins documentation pull requests reviewing Jenkins X documentation pull requests How can I fix a documentation bug? Instructions for contributing to the Jenkins documentation are in the CONTRIBUTING file of the site repository. Follow the instructions in that file and submit pull requests for review. Instructions for contributing to the Jenkins X documentation are on the Jenkins X documentation site. Follow the instructions in that file and submit pull requests for review. How can I evaluate a pull request? Pull requests for the Jenkins project are reviewed in the Jenkins documentation repository. Log in to GitHub with your credentials and add your review comments to pull requests. Pull requests for the Jenkins X project are reviewed in the Jenkins X documentation repository. Login to GitHub with your credentials and add your review comments to pull requests.

FOSDEM 2018 is a free event for software developers to meet, share ideas and collaborate. It is an annual event that brings open source contributors from around the world for two days of presentations, discussions, and learning. Jenkins will be well-represented at FOSDEM 2018. Happy Hour before FOSDEM We’ll have a happy hour Friday evening before FOSDEM at Cafe Le Roy d’Espagne. See the meetup page for details. Jenkins table at FOSDEM A Jenkins table will be staffed by volunteers at FOSDEM to answer questions, discuss topics, and help users. See the meetup page for details. Presentations at FOSDEM Automated Linux Containers deployment for fun and profit by David Negreira Advanced testing in action on a Java project by Vincent Massol Deployment vs Provisioning vs Orchestration vs Configuration Management by Peter Souter Jenkins Hackfest after FOSDEM A Jenkins Hackfest will be held the day after FOSDEM 2018. Those who would like to join us for the hackfest 5 Feb 2018 should register for the meetup. Meals, snacks, and beverages will be provided for the hackfest. Come join us, and let’s write some code! Questions? feel free to contact Alyssa Tong or Mark Waite.

This is a guest post by Mark Waite, who maintains the git plugin, the git client plugin, and is a technical evangelist for CloudBees, Inc. The Jenkins project booth at Jenkins World 2017 will include the "Pull Requests Corner", recruiting new Jenkins contributors. We think there are many people who will attend the conference without realizing how easy it is to help the Jenkins project, and how much the help is appreciated. Meet us in the "Pull Requests Corner" and we’ll help you find a way to help Jenkins. Here are some areas where we can use your help. Most of them do not require coding, and do not require a large time commitment. One Minute Feedback on Your Version The Jenkins changelog pages ( LTS and weekly) gather user experiences with specific Jenkins versions. You can help other Jenkins users by clicking one of the weather icons in the LTS changelog (or the weekly changelog) for the release you’re using. Changelog feedback from weekly releases helps the release team select the long term support version. Changelog feedback from LTS releases helps other users prepare to upgrade. It takes less than a minute, and helps the community (which will ultimately help you). Five Minutes to Answer a Question In five minutes or less, you can help other Jenkins users. For example: Answer a question on the #jenkins channel of internet relay chat (IRC) Answer a question on the Jenkins users mailing list Answer a question on stackoverflow jenkins, jenkins plugins, or jenkins pipeline Answer a question on reddit Ten Minutes to Learn and Share If you have ten minutes, you can learn something new and share what you learned. Read a Jenkins community blog post and tweet it with the hashtag #jenkinsci Read a devops.com blog post and share it on LinkedIn Read a CloudBees blog post and test drive an idea from it Find another Jenkins blog and share it (I recently discovered Matt Bajor’s ci/cd life blog) Fifteen Minutes for Pipeline Liam Newman has created the " Jenkins Minute" video series. They are brief video segments focusing on specific Jenkins functionality. Choose a video, watch it, and share what you learned on social media. Twenty Minutes for a Bug The Jenkins bug tracker contains thousands of bugs. Reviewing, duplicating, and clarifying bug reports takes time. When maintainers are reviewing, duplicating, and clarifying bug reports, they are not fixing bugs, and they are not adding new capabilities. You can help maintainers by reviewing and duplicating a bug report that matters to you. A comment on a bug report is especially helpful when it confirms you’ve been able to duplicate the bug. It is even more helpful if your verification includes the steps you took and how they differ from the original report. A bug report which has been duplicated, and includes clear instructions, is much more likely to receive maintainer attention. Help yourself and others by duplicating bugs that matter to you. Thirty Minutes for Documentation The Jenkins documentation includes user documentation ( guided tour and handbook) and developer documentation ( tutorial, how-to guides, and reference). You can help the documentation by describing something important to you clearly and completely. Refer to the instructions for documentation contributors to see how easy it is to help. Forty Five Minutes for Translation If English is not your native language, you can help with Jenkins localization. Jenkins is used worldwide, and many users will benefit from translations. Considering the rapid and continuing evolution of Jenkins, it is no surprise that there is plenty to translate. Refer to the internationalization guide for instructions to help you contribute translations. Sixty Minutes for a Meetup Local groups around the world meet often for Jenkins presentations, discussions, and demonstrations. Organizing a Jenkins Area Meetup will introduce you to other users, and will let you explore new ways to benefit from Jenkins. The team at jenkinsci-jam@googlegroups.com is ready to support your JAM with stickers, t-shirts, and more. Week or More - Adopt a Plugin The Jenkins plugin ecosystem covers a wide range of areas. Jenkins plugin maintainers come from many different backgrounds, with many different interests. Often, a plugin maintainer may find that they want to do something different on the project, or they may leave the project. When a plugin maintainer is no longer able to maintain a plugin, they can place it for adoption. Plugins placed for adoption range from very specific use cases (node stalker plugin) to very general use cases (Subversion plugin). Maintaining an orphan plugin is a great way to contribute to the project. Follow the instructions to " Adopt a Plugin". See You There! All those techniques (and more) are available on the Jenkins participate page. Look for the "Jenkins Needs You" poster at Jenkins World, and come talk to us about the ways you can learn new things, address your concerns, and help Jenkins. Join the Jenkins project at Jenkins World on August 30-31, register with the code JWFOSS for a 30% discount off your pass.

This is a guest post by Mark Waite, who maintains the git plugin, the git client plugin, and is a technical evangelist for CloudBees, Inc. While developing the " Intro to Plugin Development" workshop for Jenkins World 2017, I was impressed by the many Jenkins plugin development videos, tutorials, and guides. Here are some of my favorite plugin development topics and links. Plugin tutorial videos Jenkins Online Meetup Plugin Development Part 1 - Basics - Steven Christou and Jesse Glick Jenkins Online Meetup Plugin Development Part 2 - Web UI - Daniel Beck and Tom Fennelly Writing your third plugin - Justin Ryan Jenkins Hackathon session at TNG Technology Consulting - Kohsuke Kawaguchi Plugin tutorial pages Tutorial on jenkins.io Install a Java Development kit, for example AdoptOpenJDK 8 or 11 Install the latest maven release Install your IDE (I like Netbeans, has the Jenkins/Stapler plugin to make plugin creation as easy as menu:File[New Project > Maven > Jenkins Plugin]) More details Many of the Jenkins plugin development topics have dedicated pages of their own, including user interface, plugin testing, and javadoc. User interface UI samples plugin (bars, boxes, buttons, lists, notification, and syntax highlighting) Understanding Jelly Tags from the Jenkins wiki Form Validation from the Jenkins wiki Jelly Form Controls from the Jenkins wiki Jelly Tag Library Reference from jenkins.io DataBoundConstructor in Basic Guide to Jelly usage DataBoundSetter in google groups Testing a plugin Unit test from the Jenkins wiki Jenkins test objects like JenkinsRule and the WithoutJenkins annotation DataBoundConstructor in Basic Guide to Jelly usage DataBoundSetter in google groups Java unit testing tools like Hamcrest and AssertJ (and JenkinsMatchers) Java unit testing rules like TemporaryFolder, Timeout, and DisableOnDebug Java unit testing classes like Assume and Parameterized Java unit testing mock frameworks like mockito and powermock Javadoc Jenkins core javadoc Jenkins plugins javadoc Extension Points List of Jenkins core extension points and all Jenkins extension points Custom build steps Adding a custom build step Actions Jenkins Action and its subtypes Mark will be presenting Intro to Plugin Development at Jenkins World in August. Register with the code JWFOSS for a 30% discount off your pass.