https://github.com/openrewrite/rewrite-jenkins
OpenRewrite recipes to continuously modernize Jenkins plugins.
https://github.com/openrewrite/rewrite-jenkins
jenkins openrewrite openrewrite-recipes
Last synced: 5 months ago
JSON representation
OpenRewrite recipes to continuously modernize Jenkins plugins.
- Host: GitHub
- URL: https://github.com/openrewrite/rewrite-jenkins
- Owner: openrewrite
- License: other
- Created: 2022-06-03T16:50:50.000Z (about 4 years ago)
- Default Branch: main
- Last Pushed: 2026-01-13T10:54:07.000Z (5 months ago)
- Last Synced: 2026-01-13T13:44:28.775Z (5 months ago)
- Topics: jenkins, openrewrite, openrewrite-recipes
- Language: Java
- Homepage:
- Size: 1.01 MB
- Stars: 13
- Watchers: 4
- Forks: 12
- Open Issues: 24
-
Metadata Files:
- Readme: README.md
- License: LICENSE.md
Awesome Lists containing this project
README
rewrite-jenkins
[](https://github.com/openrewrite/rewrite-jenkins/actions/workflows/ci.yml)
[](https://mvnrepository.com/artifact/org.openrewrite.recipe/rewrite-jenkins)
[](https://ge.openrewrite.org/scans)
[](https://github.com/openrewrite/.github/blob/main/CONTRIBUTING.md)
## What is this?
This project contains a series of Rewrite recipes and visitors to automatically upgrade and migrate Jenkins plugins.
[Jenkins][jenkins] is a fast-moving project that recommends plugins [update quarterly][choosing-version].
As Jenkins evolves, functionality is regularly factored out from core into plugins.
Implicit dependencies are added to plugins based on the version of Jenkins they depend on to retain backwards compatibility.
By regularly marching plugins forward, we can drop these dependencies when unnecessary, making our deployments smaller and simpler.
Additionally, depending on newer versions of Jenkins allows our builds to pick up deprecations.
These deprecations can often be migrated with new OpenRewrite recipes.
Proactively handling deprecations in the plugins we depend on allows us to avoid runtime issues if and when the deprecated code is removed.
## Quick start
[Running Rewrite on a Maven project without modifying the build][mvn-cli] is very helpful for getting started.
To run the `org.openrewrite.jenkins.github.AddTeamToCodeowners` recipe:
```shell
$ mvn -U org.openrewrite.maven:rewrite-maven-plugin:run \
-Drewrite.recipeArtifactCoordinates=org.openrewrite.recipe:rewrite-jenkins:RELEASE \
-Drewrite.activeRecipes=org.openrewrite.jenkins.github.AddTeamToCodeowners
```
[mvn-cli]: https://docs.openrewrite.org/running-recipes/running-rewrite-on-a-maven-project-without-modifying-the-build
## How to use?
See the full documentation at [docs.openrewrite.org](https://docs.openrewrite.org/).
## Contributing
We appreciate all types of contributions. See the [contributing guide](https://github.com/openrewrite/.github/blob/main/CONTRIBUTING.md) for detailed instructions on how to get started.
### Licensing
For more information about licensing, please visit our [licensing page](https://docs.openrewrite.org/licensing/openrewrite-licensing).
[jenkins]: https://jenkins.io
[choosing-version]: https://www.jenkins.io/doc/developer/plugin-development/choosing-jenkins-baseline/