Permalink
Cannot retrieve contributors at this time
Name already in use
A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
jenkins.io/content/_data/roadmap/roadmap.yml
Go to fileThis commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| statuses: | |
| - id: released | |
| displayName: "Released" | |
| description: > | |
| The initiative is completed and available to users. | |
| There might be follow-up improvements to the initiative, and any contributions are welcome. | |
| - id: preview | |
| displayName: "Preview" | |
| description: > | |
| This initiative is available to Jenkins users and contributors for preview. | |
| We would appreciate testing and any feedback! | |
| - id: current | |
| displayName: "Current" | |
| description: > | |
| Things being worked on presently with a specific scope, typically a JEP, though no specific delivery databases. | |
| Please see the link if you want to contribute to the initiative. | |
| - id: near-term | |
| displayName: "Near Term" | |
| description: "We intend to work on that in the short term, but there is no ongoing development" | |
| - id: future | |
| displayName: "Future" | |
| description: > | |
| There is a consensus within the community that we would like this initiative to happen. | |
| We intend to work on that in the future, but there is no ongoing development. | |
| - id: withdrawn | |
| hide: true | |
| displayName: "Withdrawn" | |
| description: > | |
| This initiative is no longer relevant due to the ecosystem change or competing initiatives. | |
| The status is used to indicate archived items which were not delivered. | |
| labels: | |
| - name: feature | |
| displayName: Features | |
| description: New features and improvements for users and maintainers | |
| - name: documentation | |
| displayName: Documentation | |
| description: Documentation-focused initiatives | |
| link: /sigs/docs | |
| - name: outreach-program | |
| displayName: Outreach Programs | |
| description: Initiatives which facilitate contributions to specific areas | |
| link: /sigs/advocacy-and-outreach/outreach-programs/ | |
| - name: infrastructure | |
| displayName: Infrastructure and Services | |
| description: Services for Jenkins users and developers provided by the Jenkins project infrastructure | |
| link: /projects/infrastructure/ | |
| - name: policies | |
| displayName: Policies | |
| description: Jenkins policies and governance | |
| - name: tools | |
| displayName: Tools | |
| description: Tools for Jenkins users and developers | |
| - name: events | |
| displayName: Community Events | |
| description: Jenkins community events, e.g. conferences, meetups, hackathons, etc. | |
| link: /events | |
| - name: security | |
| displayName: Security | |
| description: > | |
| Initiatives related to the Jenkins security hardening and security management. | |
| Planned Security vulnerability fixes and advisories are not listed on the roadmap. | |
| link: /security | |
| categories: | |
| - name: Pipeline authoring and development tools | |
| description: Initiatives focused on improving Jenkins Pipeline and experience of Pipeline developers | |
| link: /doc/developer/tutorial-improve/improve-pipeline-documentation/ | |
| initiatives: | |
| - name: Jenkins Templating Engine 2.0 | |
| description: "JTE enables the creation of tool-agnostic pipeline templates that can be shared across teams. Version 2.0 will have improved integration with the underlying pipeline engine and incorporate many of the community's top feature requests." | |
| status: released | |
| link: https://github.com/jenkinsci/templating-engine-plugin | |
| labels: | |
| - feature | |
| - name: Pipeline development in IDE | |
| description: > | |
| The goal is to extend support for Pipeline development in IDEs, visual editors, and other development tools. | |
| The scope may include creation of new IDE plugins and extending Jenkins Pipeline to support common features like live code deployment and debugging. | |
| status: future | |
| labels: | |
| - feature | |
| - name: Pipeline Documentation | |
| description: > | |
| Expand Pipeline reference documentation, tutorials, and more. | |
| status: future | |
| labels: | |
| - documentation | |
| - name: Pipeline as YAML | |
| description: Official support for defining Jenkins Pipelines in YAML, without additional Pipeline libraries | |
| status: preview | |
| link: /projects/gsoc/2020/project-ideas/pipeline-as-yaml-experiment/ | |
| labels: | |
| - feature | |
| - name: Promotion support for Pipeline jobs | |
| description: Provide out-of-the-box support for manual and automatic promotion of build artifacts in a separate Pipeline after the job completion | |
| status: future | |
| link: https://issues.jenkins.io/browse/JENKINS-36089 | |
| labels: | |
| - feature | |
| - name: Improve Pipeline step documentation generator | |
| status: future | |
| description: > | |
| Enhance the Jenkins Pipeline documentation generator to produce better documentation for thousands of Pipeline developers. | |
| link: /projects/gsoc/2020/project-ideas/pipeline-step-documentation-generator/ | |
| labels: | |
| - documentation | |
| - name: Tool and Service integrations | |
| description: > | |
| Initiatives focused on integrations with various external tools and services. | |
| It includes but not limited to SCMs, source code hosting services, build and testing tools. | |
| initiatives: | |
| - name: "Pipeline: GitHub App authentication" | |
| status: released | |
| link: /blog/2020/04/16/github-app-authentication/ | |
| labels: | |
| - feature | |
| - name: "Git Plugin Performance Improvements" | |
| status: released | |
| description: > | |
| Improve Jenkins git plugin performance by fixing known issues in performance critical areas | |
| link: /projects/gsoc/2020/projects/git-plugin-performance/ | |
| labels: | |
| - feature | |
| - name: "GitHub Checks API integrations" | |
| status: released | |
| description: > | |
| Create a new plugin API so that plugins can publish GitHub Checks statuses. | |
| Implement Checks API support in Warnings NG and Code Coverage API plugins. | |
| link: /projects/gsoc/2020/projects/github-checks/ | |
| labels: | |
| - feature | |
| - name: Machine Learning Plugin for Data Science | |
| status: released | |
| description: > | |
| Integrate Machine Learning workflow with Jenkins build tasks, including Data preprocessing, Model Training, Evaluation and Prediction. | |
| This plugin will be capable of executing code fragments via IPython kernel as currently supported by Jupyter. | |
| link: /projects/gsoc/2020/projects/machine-learning/ | |
| labels: | |
| - feature | |
| - name: OpenAPI for Jenkins core and plugins | |
| status: future | |
| description: > | |
| Expose Jenkins REST APIs as the OpenAPI Specification so that users could easily integrate with Jenkins and create clients for it. | |
| link: /projects/gsoc/2020/project-ideas/automatic-spec-generator-for-jenkins-rest-api/ | |
| labels: | |
| - feature | |
| - name: "Docker: image changes polling and security scans" | |
| status: future | |
| description: > | |
| Create a new Jenkins plugin to automate polling of image changes and security scans. | |
| link: /projects/gsoc/2020/project-ideas/docker-registries-polling-plugin/ | |
| labels: | |
| - feature | |
| - security | |
| - name: End user experience and interface | |
| description: Initiatives focused on improving the Jenkins user interface and user experience | |
| link: /sigs/ux | |
| initiatives: | |
| - name: "UI/UX: Look and Feel updates" | |
| status: current | |
| description: "Modernize the Jenkins Web interface styling and appearance" | |
| link: /sigs/ux/#project-ui-look-and-feel | |
| labels: | |
| - feature | |
| - name: "Dark Theme" | |
| status: released | |
| description: "A new official Dark Theme for Jenkins, and Jenkins core and plugin changes to make it possible" | |
| link: https://github.com/jenkinsci/dark-theme-plugin | |
| labels: | |
| - feature | |
| - name: "Plugin management UI/UX revamp" | |
| description: > | |
| This initiative aims to improve plugin management UI for Jenkins administrators | |
| so that they can easily discover plugins and make decisions about plugin upgrades. | |
| Scope: Plugin Manager in the Jenkins core, plugins.jenkins.io, Jenkins Update Center and other services. | |
| status: preview | |
| labels: | |
| - feature | |
| - infrastructure | |
| link: /sigs/ux/#project-plugin-management-ui-ux | |
| - name: Plugin docs migration to GitHub | |
| description: Host plugin documentation on GitHub rather than the Jenkins Wiki | |
| status: current | |
| link: /sigs/docs/#ongoing-projects | |
| labels: | |
| - documentation | |
| - name: Docs migration to jenkins.io | |
| description: Migrate remaining documentation from the Jenkins Wiki to jenkins.io | |
| status: current | |
| link: https://issues.jenkins.io/browse/INFRA-2328 | |
| labels: | |
| - documentation | |
| - name: Add site search | |
| description: Add site search to www.jenkins.io and plugins.jenkins.io | |
| status: released | |
| link: https://plugins.jenkins.io | |
| labels: | |
| - documentation | |
| - name: "UI/UX: Accessibility" | |
| status: near-term | |
| description: Improve Jenkins navigation and layouts to make it more usable by as many user groups as possible. | |
| link: /sigs/ux/#project-ui-accessibility | |
| labels: | |
| - feature | |
| - name: "Configuration UI: Tables to Divs migration" | |
| status: released | |
| description: > | |
| Improve visualization of configuration pages by changing layouts from tables to divs. | |
| It will improve layout on narrow screens and particularly on mobile devices. | |
| link: https://issues.jenkins.io/browse/JENKINS-62437 | |
| labels: | |
| - feature | |
| - name: "Improve UI Theme Management" | |
| status: released | |
| description: > | |
| Create a new Theme Manager plugin for Jenkins. | |
| In addition to the features offered by the Simple Theme Plugin, | |
| it will help users to easily discover and manage themes compatible with their Jenkins version. | |
| link: https://github.com/jenkinsci/theme-manager-plugin | |
| labels: | |
| - feature | |
| - name: "UI/UX: User interface rework" | |
| status: future | |
| link: /sigs/ux/#project-ui-overhaul | |
| labels: | |
| - feature | |
| - name: User Guide improvements | |
| description: Improve Jenkins User Guide with pipeline examples, additional tutorials, and better navigation | |
| status: future | |
| link: https://issues.jenkins.io/browse/WEBSITE-739 | |
| labels: | |
| - documentation | |
| - name: Solution Pages | |
| description: Improve the navigation and content of the solution pages | |
| status: future | |
| link: https://issues.jenkins.io/browse/WEBSITE-742 | |
| labels: | |
| - documentation | |
| - name: Modernize mirror infrastructure | |
| description: > | |
| Improve and expand the mirror infrastructure to provide fast and reliable downloads to Jenkins users. | |
| status: released | |
| link: https://issues.jenkins.io/browse/INFRA-2516 | |
| labels: | |
| - infrastructure | |
| - name: Non-inclusive terminology cleanup | |
| description: > | |
| In 2016, the Jenkins community decided to change the non-inclusive terminology within the project. | |
| The “slave” term was deprecated and replaced by “agent” in Jenkins 2.0. | |
| In July 2020 we also adopted the “controller” term instead of “master”, and deprecated the “whitelist/blacklist” terms. | |
| There are many places where the old terminology still needs to be replaced. | |
| We want to replace the deprecated terminology by new terms: “controller”, “agent”, “allowlist”, “denylist”, and “main” for branch names. | |
| Scope: documentation, Web UI, localizations, API, etc. | |
| status: current | |
| link: /sigs/advocacy-and-outreach/#inclusive-naming | |
| labels: | |
| - documentation | |
| - feature | |
| - policies | |
| - name: Management and Administration | |
| description: "Initiatives which help to manage Jenkins as Code: JCasC Plugin, etc." | |
| initiatives: | |
| - name: "JCasC: Plugin compatibility" | |
| description: > | |
| Ensure wide support for Jenkins Configuration-as-Code in the Jenkins core and plugins. | |
| status: current | |
| link: https://github.com/jenkinsci/configuration-as-code-plugin/issues/809 | |
| labels: | |
| - feature | |
| - name: 'JEP-222: Remoting over WebSockets' | |
| status: preview | |
| link: https://github.com/jenkinsci/jep/tree/master/jep/222 | |
| labels: | |
| - feature | |
| - name: 'JEP-223: Manage permissions' | |
| status: preview | |
| link: https://github.com/jenkinsci/jep/tree/master/jep/223 | |
| labels: | |
| - feature | |
| - name: 'JEP-224: SystemRead permissions' | |
| description: > | |
| Update Jenkins Web UI to support read-only access to system configuration and diagnostics information. | |
| It complements Jenkins Configuration-as-Code stories by preventing undesired manual modifications on running instances. | |
| status: released | |
| link: https://github.com/jenkinsci/jep/tree/master/jep/224 | |
| labels: | |
| - feature | |
| - name: "Windows Services: YAML Configuration Support" | |
| status: current | |
| description: > | |
| Enhance Jenkins controller and agent service management on Windows by | |
| offering new configuration file formats and improving settings validation. | |
| link: /projects/gsoc/2020/projects/winsw-yaml-configs/ | |
| labels: | |
| - feature | |
| - name: "Script Security: Improve approval management" | |
| status: current | |
| description: > | |
| In the current version of the "In-process Script Approval" page, | |
| you have the possibility to approve/deny a script and then, once approved, you can only revoke all approvals at once. | |
| It complicates administration and exposes the instance to potential security concerns due to obsolete scripts. | |
| link: https://issues.jenkins.io/browse/JENKINS-62448 | |
| labels: | |
| - feature | |
| - security | |
| - name: Built-in plugin management as-code | |
| description: > | |
| Evolution of plugin management capabilities in the Jenkins core and Docker images. | |
| It includes adoption of the new Plugin Management Tool in distributions, and support of advanced plugin definition formats like YAML. | |
| status: near-term | |
| link: /projects/gsoc/2020/project-ideas/plugin-installation-manager-tool/ | |
| labels: | |
| - feature | |
| - name: "JCasC: Pluggable configuration sources" | |
| description: > | |
| Support external configuration sources in the Jenkins Configuration-as-Code plugin. | |
| Examples of potential configuration sources: Git, S3 Buckets, Kubernetes CRD. | |
| status: future | |
| link: https://github.com/jenkinsci/configuration-as-code-plugin/issues/1365 | |
| labels: | |
| - feature | |
| - name: Administrator Guide overhaul | |
| description: Create a Jenkins Administrator Guide from the administration content in the Jenkins Handbook | |
| status: future | |
| link: https://issues.jenkins.io/browse/WEBSITE-738 | |
| labels: | |
| - documentation | |
| - name: "Better Remoting Monitoring" | |
| status: future | |
| description: > | |
| Support monitoring of Jenkins networking (controller to agent communications, etc.) with open source monitoring tools such as Prometheus, Grafana, etc. | |
| link: /projects/gsoc/2020/project-ideas/remoting-monitoring/ | |
| labels: | |
| - feature | |
| # - name: Jenkins Security | |
| # description: "Public security hardening and management initiatives. Vulnerability fixes are not listed" | |
| # initiatives: | |
| - name: Jenkins on cloud platforms | |
| description: > | |
| Initiatives focused on making Jenkins easy to deploy and run in cloud environments, | |
| including Kubernetes and various cloud providers. | |
| It also includes integrations with cloud storage providers. | |
| link: /sigs/cloud-native/pluggable-storage/ | |
| initiatives: | |
| - name: CloudEvents support | |
| status: current | |
| description: > | |
| Microservices are the de facto architecture of the cloud and events are the primary way in which microservices communicate a change of state. | |
| CloudEvents is a specification for describing event data in common, standardised formats. | |
| The CloudEvents plugin would enable Jenkins support for CloudEvents by allowing events to be emitted in Jenkins pipelines and triggering Jobs on certain events, | |
| bringing Jenkins one step closer to interoperability with other technologies in the cloud. | |
| link: /projects/gsoc/2021/project-ideas/cloudevents-plugin/ | |
| labels: | |
| - feature | |
| - name: 'JEP-219: Jenkins Kubernetes Operator' | |
| description: > | |
| Further evolution of a Kubernetes Native Operator which manages operations for Jenkins on Kubernetes. | |
| It has been built with Immutability and declarative Configuration as Code in mind. | |
| status: released | |
| link: https://github.com/jenkinsci/jep/tree/master/jep/219 | |
| labels: | |
| - feature | |
| - name: 'Jenkinsfile Runner 1.0' | |
| description: > | |
| Finalization of Jenkinsfile Runner prototype which would allow running jobs and pipelines as Function-as-Service in cloud environments. | |
| status: preview | |
| link: https://github.com/jenkinsci/jenkinsfile-runner/milestone/1 | |
| labels: | |
| - feature | |
| - name: 'JEP-226: External Fingerprint Storage' | |
| description: > | |
| Extend Jenkins to support storing artifact usage history in external databases. | |
| The project also includes a reference implementation, powered by Redis. | |
| status: preview | |
| link: https://github.com/jenkinsci/jep/tree/master/jep/226 | |
| labels: | |
| - feature | |
| - name: "Jenkins on Kubernetes online meetups" | |
| status: current | |
| description: > | |
| Promote best practices and success stories for Jenkins on Kubernetes by organizing a series of online meetups. | |
| link: https://www.meetup.com/Jenkins-online-meetup/ | |
| labels: | |
| - outreach-program | |
| - events | |
| - name: 'Jenkins FaaS Capability' | |
| description: > | |
| Continued development of the Jenkinsfile Runner and its packaging/development tools to simplify usage of the tool as Function-as-Service. | |
| status: near-term | |
| link: https://github.com/jenkinsci/jenkinsfile-runner | |
| labels: | |
| - feature | |
| - name: Document Jenkins on Kubernetes | |
| description: Describe the concepts, techniques, and choices available for Jenkins on Kubernetes | |
| status: near-term | |
| link: /sigs/docs/#jenkins-on-kubernetes | |
| labels: | |
| - outreach-program | |
| - documentation | |
| - name: 'Tekton Pipelines build steps' | |
| description: > | |
| Support managing and triggering Tekton Pipelines on a Kubernetes Cluster as Jenkins build steps. | |
| status: preview | |
| link: https://github.com/jenkinsci/tekton-client-plugin/blob/master/roadmap.md | |
| labels: | |
| - feature | |
| - name: 'Tekton Pipelines execution engine' | |
| description: > | |
| Seamless integration of Tekton Pipelines as additional Pipeline execution engine in Jenkins. | |
| It would allow running executions on Tekton while benefiting from the Jenkins Pipeline orchestration and UI features: | |
| Multi-Branch Pipeline, organization folders, pipeline browsers, etc. | |
| status: near-term | |
| link: https://github.com/tektoncd/pipeline | |
| labels: | |
| - feature | |
| - name: 'Pluggable Build Log storage for Jenkins Pipeline' | |
| description: > | |
| Support for externalizing build logs in Jenkins Pipeline. | |
| Includes streaming logs from agents directly to the storage, as well as support for log visualization in Jenkins. | |
| status: preview | |
| link: /sigs/cloud-native/pluggable-storage/#build-log-storage | |
| labels: | |
| - feature | |
| - name: 'Pluggable Build Results Storage' | |
| description: > | |
| Support for storing build results in an external storage or a databases. | |
| It includes build histories, metadata, and build actions which are stored in build.xml files. | |
| status: future | |
| link: /sigs/cloud-native/pluggable-storage/#status-summary | |
| labels: | |
| - feature | |
| - name: 'Pluggable Unit Test Results Storage' | |
| description: > | |
| Support for storing unit test results in an external database or a test management system. | |
| status: preview | |
| link: https://github.com/jenkinsci/junit-plugin/issues/142 | |
| labels: | |
| - feature | |
| - name: 'Pluggable Build Log storage for all job types' | |
| description: > | |
| Support for externalizing logs for all build types, not just for Jenkins Pipeline. | |
| Includes streaming logs from agents directly to the storage, as well as support for log visualization in Jenkins. | |
| status: future | |
| link: /sigs/cloud-native/pluggable-storage/#build-log-storage | |
| labels: | |
| - feature | |
| - name: 'External/Pluggable Data Storage' | |
| description: > | |
| Continuation of the external cloud native storage initiatives. | |
| The scope includes supporting external storages in common Jenkins data types, | |
| most notably build logs build results and reports, job configurations, etc. | |
| Particular initiatives might be split off this roadmap item. | |
| status: future | |
| link: /sigs/cloud-native/pluggable-storage/ | |
| labels: | |
| - feature | |
| - name: Packaging and platform support | |
| link: /sigs/platform | |
| initiatives: | |
| - name: Docker images for Windows agents | |
| description: Official Windows Docker images for Jenkins controllers and agents. | |
| status: released | |
| link: /blog/2020/05/11/docker-windows-agents/ | |
| labels: | |
| - feature | |
| - name: Docker images for IBM s390x | |
| status: released | |
| description: Docker image support for IBM series 390 mainframes running Java 8 and Java 11 | |
| link: https://issues.jenkins.io/browse/JENKINS-61773 | |
| labels: | |
| - feature | |
| - name: Docker images for ARM 64 | |
| status: released | |
| description: Docker image support for ARM 64 running Java 8 and Java 11 | |
| link: https://issues.jenkins.io/browse/JENKINS-61775 | |
| labels: | |
| - feature | |
| - name: Multi-platform Docker images | |
| status: preview | |
| link: https://issues.jenkins.io/browse/JENKINS-52785 | |
| labels: | |
| - feature | |
| - name: New Windows installer | |
| description: > | |
| Rework of the Windows installer user experience. | |
| Java unbundling, account management and port setup. | |
| status: released | |
| link: /blog/2020/08/12/windows-installers-upgrade/ | |
| labels: | |
| - feature | |
| - security | |
| - name: Windows support policy | |
| description: Currently Jenkins has no documented Windows Support policy. We want to add one and to deprecate/remove support for old platforms | |
| status: released | |
| link: /doc/administration/requirements/windows/ | |
| labels: | |
| - documentation | |
| - policies | |
| - name: Migration to Eclipse Temurin JDK in distributions | |
| description: > | |
| Currently Jenkins uses OpenJDK in the most of official Docker packages. | |
| We would like to migrate to Eclipse Temurin which offers wider range of supported platforms. | |
| status: current | |
| link: https://issues.jenkins.io/browse/JENKINS-63286 | |
| labels: | |
| - feature | |
| - name: Custom Jenkins distribution build service | |
| description: > | |
| A new service which would allow users to configure and build their own Jenkins distributions, | |
| with custom plugin sets and configurations included. | |
| This would be a self-hosted service initially. | |
| status: preview | |
| link: /projects/gsoc/2020/projects/custom-jenkins-distribution-build-service | |
| labels: | |
| - feature | |
| - tools | |
| - name: "customize.jenkins.io" | |
| description: > | |
| Hosted versions of the Custom Jenkins distribution build service provided by the Jenkins project | |
| status: current | |
| link: /projects/gsoc/2020/projects/custom-jenkins-distribution-build-service | |
| labels: | |
| - feature | |
| - infrastructure | |
| - name: Custom WAR/Docker Packager 2.0 | |
| description: > | |
| New edition of Custom WAR Packager with a new configuration YAML format. | |
| It also includes integrations with other Jenkins tools and services: Update Centers, Plugin Installation Manager, Jenkinsfile Runner Packager, etc. | |
| status: near-term | |
| link: https://github.com/jenkinsci/custom-war-packager/blob/master/ROADMAP.adoc#custom-war-packager-2x | |
| labels: | |
| - feature | |
| - tools | |
| - name: Java 17 support | |
| description: > | |
| We would like to support future mainstream JVM versions (Java 17). | |
| Right now Jenkins runs well on Java 11, but we may need to do some changes towards the next LTS baseline. | |
| status: preview | |
| link: /sigs/platform/#java-support | |
| labels: | |
| - feature | |
| - name: Cloud native Java support | |
| description: > | |
| We are interested to run Jenkins in cloud native environments. | |
| To do so, we would like to introduce support for perspective virtual machines like GraalVM or Quarkus. | |
| status: future | |
| link: /sigs/platform/#java-support | |
| labels: | |
| - feature | |
| - name: Jenkins developer tools and services | |
| description: > | |
| Solutions and tools for Jenkins developers and contributors. | |
| User-focused developer tools, e.g. for Pipeline development, are listed in other sections. | |
| initiatives: | |
| - name: Core release automation | |
| status: preview | |
| link: https://issues.jenkins.io/browse/INFRA-910 | |
| labels: | |
| - infrastructure | |
| - name: Jenkins core BOM | |
| description: > | |
| This Bill of Materials lists libraries and versions supplied by the Jenkins core. | |
| It can be used by plugin developers to prevent risk of binary conflicts between plugins. | |
| status: released | |
| link: /doc/developer/plugin-development/dependency-management/#jenkins-core-bom | |
| labels: | |
| - tools | |
| - name: Plugin POM 4.0 | |
| description: > | |
| New Plugin POM release which enables best practices like Jenkins Core bill of materials by design. | |
| status: released | |
| link: https://github.com/jenkinsci/plugin-pom/releases/tag/plugin-4.0 | |
| labels: | |
| - tools | |
| - name: Jenkins plugin BOM | |
| description: > | |
| This Bill of materials can be used by plugin developers to more easily manage dependencies on other common plugins. | |
| It includes a cross-verified set of plugins compatible with a particular Jenkins core baseline. | |
| status: released | |
| link: https://github.com/jenkinsci/bom | |
| labels: | |
| - tools | |
| - name: Static analysis for security issues | |
| description: > | |
| Extending static analysis to discover potential security issues with help of the Find Security Bugs tools. | |
| status: preview | |
| link: https://groups.google.com/forum/#!msg/jenkinsci-dev/exd3fc9NUAg/xn--6vNSBgAJ | |
| labels: | |
| - tools | |
| - security | |
| - name: "Changelog automation" | |
| description: > | |
| Jenkins project now offers changelog automation powered by Release Drafter GitHub Apps or GitHub Actions. | |
| We would like to update the flow and to support changelog generation within Jenkins pipelines. | |
| status: preview | |
| link: https://github.com/jenkinsci/.github/blob/master/.github/release-drafter.adoc | |
| labels: | |
| - tools | |
| - documentation | |
| - name: "Automated Dependency management" | |
| description: > | |
| We want to widely adopt Dependabot in the project to simplify dependency management along with BOMs. | |
| In order to do so, additional Jenkins-specific guidelines and documentation are needed. | |
| status: preview | |
| link: https://groups.google.com/forum/#!searchin/jenkinsci-dev/dependabot%7Csort:date/jenkinsci-dev/XMllKuWLO_8/5hagrjApEgAJ | |
| labels: | |
| - tools | |
| - name: "JEP-217: Infrastructure for Experimental Docker images" | |
| description: > | |
| Provide a storage for experimental Jenkins Docker images so that maintainers can build and deploy untrusted images | |
| from ci.jenkins.io and other services. | |
| status: near-term | |
| link: https://github.com/jenkinsci/jep/blob/master/jep/217 | |
| labels: | |
| - infrastructure | |
| - name: "JEP-229: Continuous Delivery of Jenkins Plugins" | |
| description: > | |
| Introduce a new system which would enable Jenkins plugin maintainers to add Continuous Delivery (CD) to their projects. | |
| status: preview | |
| link: https://github.com/jenkinsci/jep/blob/master/jep/229 | |
| labels: | |
| - tools | |
| - infrastructure | |
| - name: Contributing to Jenkins | |
| description: > | |
| Initiatives focused on onboarding and enabling Jenkins contributors. | |
| It includes helping newcomers to join the project, | |
| and helping experienced contributors to step up and take maintainer and other roles in the project. | |
| link: /participate | |
| initiatives: | |
| - name: Plugin adoption process revamp | |
| status: released | |
| link: /doc/developer/plugin-governance/adopt-a-plugin/ | |
| labels: | |
| - documentation | |
| - policies | |
| - name: Contributor guidelines refresh | |
| status: released | |
| link: https://issues.jenkins.io/browse/WEBSITE-662 | |
| labels: | |
| - community | |
| - documentation | |
| - name: Google Summer of Code 2021 | |
| status: released | |
| link: /projects/gsoc/2021 | |
| labels: | |
| - outreach-program | |
| - events | |
| - feature | |
| - name: Google Summer of Code 2020 | |
| status: released | |
| link: /projects/gsoc/2020 | |
| labels: | |
| - outreach-program | |
| - events | |
| - feature | |
| - name: Google Season of Docs 2020 | |
| status: released | |
| link: /sigs/docs/gsod/2020/ | |
| labels: | |
| - outreach-program | |
| - documentation | |
| - events | |
| - name: SheCodeAfrica Contributhon 2021 | |
| status: released | |
| link: /blog/2021/04/07/contributhon-participants/ | |
| labels: | |
| - outreach-program | |
| - documentation | |
| - events | |
| - name: Community Bridge Mentorship | |
| status: future | |
| link: /sigs/advocacy-and-outreach/outreach-programs/#community-bridge | |
| labels: | |
| - outreach-program | |
| - community | |
| - events | |
| - name: Hacktoberfest 2020 | |
| status: released | |
| link: /events/hacktoberfest/ | |
| labels: | |
| - outreach-program | |
| - feature | |
| - documentation | |
| - community | |
| - events | |
| - name: Hacktoberfest 2021 | |
| status: released | |
| link: /events/hacktoberfest/ | |
| labels: | |
| - outreach-program | |
| - feature | |
| - documentation | |
| - community | |
| - events | |
| - name: Hacktoberfest 2022 | |
| status: released | |
| link: /events/hacktoberfest/ | |
| labels: | |
| - outreach-program | |
| - feature | |
| - documentation | |
| - community | |
| - events | |
| - name: Community advocacy and marketing | |
| description: Initiatives related to promoting Jenkins and facilitating contributions to the project | |
| link: /sigs/advocacy-and-outreach/ | |
| initiatives: | |
| - name: Jenkins Is The Way program | |
| status: released | |
| description: > | |
| Jenkins Is The Way is a collection of experiences from all around the world showcasing how users are building, deploying, and automating great stuff with Jenkins. | |
| link: /blog/2020/04/30/jenkins-is-the-way/ | |
| labels: | |
| - outreach-program | |
| - name: New online meetup platform | |
| status: released | |
| description: > | |
| Make it possible to regularly host Jenkins online meetups and webinars. | |
| link: /events/online-meetup/ | |
| labels: | |
| - outreach-program | |
| - infrastructure | |
| - name: Jenkins on LinkedIn | |
| status: released | |
| description: > | |
| Extend and automate Jenkins presence in LinkedIn so that we could outreach to its users and facilitate adoption and contributions. | |
| link: https://www.linkedin.com/company/jenkins-project/ | |
| labels: | |
| - outreach-program | |
| - name: Jenkins Project Internals | |
| description: > | |
| Initiatives which focus on project internals which have no immediate impact on users. | |
| It includes the project infrastructure maintenance and similar topics which are critical to the project health. | |
| initiatives: | |
| - name: "Migrate ci.jenkins.io agents to AWS" | |
| description: > | |
| Migration of agent workload from Azure to AWS in order to optimize the infrastructure costs for the project. | |
| status: preview | |
| link: https://issues.jenkins.io/browse/INFRA-2525 | |
| labels: | |
| - infrastructure | |
| - name: ci.jenkins.io as code | |
| status: current | |
| description: Define and maintain ci.jenkins.io configuration as code rather than through the user interface | |
| labels: | |
| - infrastructure | |
| - name: Governance | |
| description: Initiatives targeting project governance, policies, funding, etc. | |
| link: /project | |
| initiatives: | |
| - name: "JEP-14: Public roadmap" | |
| status: released | |
| link: https://github.com/jenkinsci/jep/tree/master/jep/14 | |
| description: > | |
| A new public community-driven roadmap which would list the key initiatives in the Jenkins project. | |
| It will help users, contributors and vendors to properly plan their work and to contribute to the projects they are interested in. | |
| labels: | |
| - documentation | |
| - policies | |
| - name: "JEP-15: Funding on Community Bridge" | |
| status: preview | |
| link: https://github.com/jenkinsci/jep/tree/master/jep/15 | |
| description: > | |
| We are interested to provide ways to donate to the Jenkins project. | |
| Donations help us to facilitate the project's roadmap and to run more community events and outreach programs. | |
| labels: | |
| - policies | |
| - infrastructure | |
| - name: Core Infrastructure Initiative compliance | |
| status: released | |
| description: > | |
| Pass the Core Infrastructure Initiative (CII) compliance certification so that we are aligned with Linux Foundation quality and security standards. | |
| It unlocks targeted security projects funding and access to additional developer tools and services. | |
| link: https://groups.google.com/forum/#!msg/jenkinsci-dev/n1qH1K5_td0/pA_nUN_6BgAJ | |
| labels: | |
| - documentation | |
| - policies | |
| - security | |
| - name: 2020 Governance Board and Officer elections | |
| status: released | |
| description: > | |
| In late 2020 we plan to hold new Jenkins Governance Board and officer elections. | |
| We will re-elect at least one Governance Board member and all officers. | |
| link: /blog/2020/12/03/election-results/ | |
| labels: | |
| - events | |
| - name: Technical Steering Committee | |
| status: future | |
| description: > | |
| Introduce an official entity which would drive Jenkins architecture and the technical roadmap. | |
| labels: | |
| - policies | |
| - name: Code of Conduct Update | |
| status: released | |
| description: > | |
| Updating the Jenkins Code of Conduct to Contributor Covenant 2.0, | |
| alignment with the Continuous Delivery Foundation requirements. | |
| link: /project/conduct/ | |
| labels: | |
| - documentation | |
| - policies | |
| - name: CDF Graduation | |
| status: released | |
| description: > | |
| The Technical Oversight Committee (TOC) of CDF set out a project lifecycle for projects as part of the governance model. | |
| We are interested to align the Jenkins project with the defined criteria for graduated projects. | |
| link: https://groups.google.com/forum/#!msg/jenkinsci-dev/I3sUP2SB2JI/LDS99sOtBQAJ | |
| labels: | |
| - documentation | |
| - policies |