Child pages
  • Home
177 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.

Jenkins Documentation Special Interest Group
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...
A Big Step of the Chinese Localization
Since 2017, I started to do some contributions to the Jenkins community. As a beginner, translation might be the easiest way to help the project. You don’t need to understand the whole context, even to create a ticket in the issue tracker system. Improvement of localization usually is minor. But some problems occurred soon, there isn’t a native speaker of Chinese that could review my PRs. So, sometimes my PRs are delayed from being merged into master. Some contributors told me that I can start a thread at the mailing list. Normally, discussing at the mailing list is the open source community way. We got a...
Introducing the Jenkins Templating Engine!
This is a guest post by Steven Terrana, a Lead Technologist at Booz Allen Hamilton and principal engineer working on the Templating Engine Plugin. He participates in the Pipeline Authoring Special Interest Group. Implementing DevSecOps practices at the enterprise scale is challenging. With multiple programming languages, automated testing frameworks, and security compliance tools being used by different applications within your organization, it becomes difficult to build and maintain pipelines for each team. Most pipelines are going to follow the same generic workflow regardless of which specific tech stack is employed by an application. The Templating Engine Plugin (abbreviated as JTE for Jenkins...
First successful use of Jenkins telemetry
Half a year ago we delivered a security fix for Jenkins that had the potential to break the entire Jenkins UI. We needed to change how Jenkins, through the Stapler web framework, handled HTTP requests, tightening the rules around what requests would be processed by Jenkins. In the six months since, we didn’t receive notable reports of problems resulting from this change, and it’s thanks to the telemetry we gathered beforehand. The Problem Jenkins uses the Stapler web framework for HTTP request handling. Stapler’s basic premise is that it uses reflective access to code elements matching its naming conventions. For example, any public method whose name...
Security spring cleaning
Today we published a security advisory that mostly informs about issues in Jenkins plugins that have no fixes. What’s going on? The Jenkins security team triages incoming reports both to Jira and our non-public mailing list. Once we’ve determined it is a plugin not maintained by any Jenkins security team members, we try to inform the plugin maintainer about the issue, offering our help in developing, reviewing, and publishing any fixes. Sometimes the affected plugin is unmaintained, or maintainers don’t respond in a timely manner to the notifications or the followup emails we send. In such cases, we publish security advisories informing users about these...

  • No labels


  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.

  2. Aller directement à la fin des métadonnéesAller au début des métadonnées


    I have a problem when I build Jenkins with tomcat I'm using:

    jenkins version : 2.129
    tomcat version : 7.0.69

    And this is the steps  :

    1-change port of tomcat 
    2-copy jenkins.war in tomcat/webapp 
    3-finaly run tomcat