Use Jenkins API plugin instead of libraries
org.openrewrite.jenkins.ReplaceLibrariesWithApiPlugin
Prefer Jenkins API plugins over bundling libraries for slimmer plugins.
Recipe source
GitHub, Issue Tracker, Maven Central
groupId: org.openrewrite.recipe
artifactId: rewrite-jenkins
version: 0.4.0
Options
Type | Name | Description | Example |
---|---|---|---|
| pluginGroupId | The first part of a dependency coordinate 'io.jenkins.plugins:ARTIFACT_ID:VERSION'. |
|
| pluginArtifactId | The second part of a dependency coordinate 'GROUP_ID:jackson2-api:VERSION'. |
|
| pluginVersion | An exact version number. |
|
| replaces | The set of library coordinates replaced by this API Plugin. |
Usage
This recipe has required configuration parameters. Recipes with required configuration parameters cannot be activated directly. To activate this recipe you must create a new recipe which fills in the required parameters. In your rewrite.yml
create a new recipe with a unique name. For example: com.yourorg.ReplaceLibrariesWithApiPluginExample
. Here's how you can define and customize such a recipe within your rewrite.yml:
Now that com.yourorg.ReplaceLibrariesWithApiPluginExample
has been defined activate it and take a dependency on org.openrewrite.recipe:rewrite-jenkins:0.4.0 in your build file:
Add the following to your
build.gradle
file:
Run
gradle rewriteRun
to run the recipe.
See how this recipe works across multiple open-source repositories
The community edition of the Moderne platform enables you to easily run recipes across thousands of open-source repositories.
Please contact Moderne for more information about safely running the recipes on your own codebase in a private SaaS.
Contributors
Last updated