Jenkins Website |
Documentation,
Asciidoc,
CSS |
Extend and improve Jenkins documentation, help to improve the website’s look&feel, create a new blogpost, a technology-specific solution page or a tutorial.
Contributing guidelines,
Good first issues
Additionally, we invite new and experienced Jenkins developers to help improve the developer documentation.
If you want to learn a Jenkins development topic and share your new knowledge with others, or want to help someone else learn, you’re welcome to contribute here.
Board, chat |
Jenkins Core |
Java,
Jelly,
Groovy,
Javascript,
HTML,
CSS,
SCSS |
There is always something to improve in Jenkins core itself.
You can address various issues, improve the codebase,
and add new features there.
Contributing,
newcomer-friendly issues, chat |
Jenkins Plugin Site |
Javascript, Java, React, Gatsby |
The plugin site is used to find information about 1800+ plugins available in Jenkins.
It provides plugin documentation, changelogs, open issues, and other data needed for Jenkins admins and end users.
We are interested to keep improving the plugin site’s UI/UX,
provide more search options, and to provide deeper integration with GitHub and other services.
Creating a dark mode was also mentioned a couple of times.
|
Jenkins Artwork |
Design |
Create new images and logos for Jenkins area meetups,
subprojects, and plugins.
You can also contribute new graphics to plugins.
Adding a logo |
Jenkins Infrastructure |
Asciidoctor, Docker, Github Actions, Jenkins Pipeline, Kubernetes, Markdown, Packer, Puppet, Python, Shell, YAML |
An infrastructure is constantly moving forward: there are always dependencies to update,
security issues to fix, new feature to release, tools to improve, etc.
Any kind of contribution is welcome: from documentation to real life code.
Either you are a beginner in this area, or a veteran of system administration,
you are welcome to pick an issue and contribute!
|
Content Security Policy (CSP) |
JavaScript, Jelly, Security |
During the last years, the Jenkins Security team has seen a lot of Cross-Site Scripting (XSS) vulnerabilities, inside Jenkins core and also for a lot of plugins.
They have put in place different kinds of mechanisms to enhance the protection of some of the common dangerous code locations.
But this kind of approach does not scale enough to cover the wide ecosystem and the numerous different ways of introducing (accidentally) XSS vulnerabilities.
|
French translation |
Git, French, Jenkins developer tools |
Improve coverage of French localization of the Jenkins web interface, including the Jenkins core and plugins.
The same is possible for other languages, let us know if you are interested!
|
