<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pipeline on Xianpeng Shen</title><link>https://shenxianpeng.dev/en/tags/pipeline/</link><description>Recent content in Pipeline on Xianpeng Shen</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>xianpeng.shen@gmail.com (Xianpeng Shen)</managingEditor><webMaster>xianpeng.shen@gmail.com (Xianpeng Shen)</webMaster><copyright>Copyright © 2017–2026 Xianpeng Shen. All rights reserved.</copyright><lastBuildDate>Sun, 12 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://shenxianpeng.dev/en/tags/pipeline/index.xml" rel="self" type="application/rss+xml"/><item><title>Jenkinsfile Lint 1.5.0 Released— Standalone Mode Without a Jenkins Server</title><link>https://shenxianpeng.dev/en/posts/2026/jenkinsfilelint-standalone/</link><pubDate>Sun, 12 Jul 2026 00:00:00 +0000</pubDate><author>xianpeng.shen@gmail.com (Xianpeng Shen)</author><guid>https://shenxianpeng.dev/en/posts/2026/jenkinsfilelint-standalone/</guid><description>Previously, jenkinsfilelint required connecting to an available Jenkins server for syntax validation. Now, v1.5.0 introduces a new standalone mode. With just Docker, you can launch a minimal Jenkins environment locally to validate Jenkinsfile syntax. This article details the implementation idea and usage of this mode.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://shenxianpeng.dev/posts/2026/jenkinsfilelint-standalone/featured.jpg"/></item><item><title>Originally Just Wanted to Propose a Doc PR, Ended Up Moving the Project to the Official Jenkins Organization</title><link>https://shenxianpeng.dev/en/posts/2026/jenkinsfilelint/</link><pubDate>Tue, 09 Jun 2026 00:00:00 +0000</pubDate><author>xianpeng.shen@gmail.com (Xianpeng Shen)</author><guid>https://shenxianpeng.dev/en/posts/2026/jenkinsfilelint/</guid><description>I wrote a small tool to validate Jenkinsfiles, initially just wanting it to appear in Jenkins&amp;rsquo; official list of development tools. However, a Jenkins maintainer suggested: why not just transfer the project directly into the jenkinsci organization? This article records the complete process from PR to transfer to an official blog post, including an interesting pitfall encountered along the way.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://shenxianpeng.dev/posts/2026/jenkinsfilelint/featured.jpg"/></item><item><title>Three Ways to Solve the Jenkins Declarative Pipeline "Method code too large" Exception</title><link>https://shenxianpeng.dev/en/posts/2020/jenkins-troubleshooting/</link><pubDate>Mon, 20 Apr 2020 00:00:00 +0000</pubDate><author>xianpeng.shen@gmail.com (Xianpeng Shen)</author><guid>https://shenxianpeng.dev/en/posts/2020/jenkins-troubleshooting/</guid><description>This article introduces three methods to solve the &amp;ldquo;Method code too large&amp;rdquo; exception in Jenkins declarative pipelines, including moving steps outside the pipeline, migrating from declarative to scripted pipelines, and using Shared Libraries.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://shenxianpeng.dev/posts/2020/jenkins-troubleshooting/featured.jpg"/></item></channel></rss>