Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Migrate from Gradle and gradle-jpi-plugin to Maven and maven-hpi-plugin #321

Closed
basil opened this issue Mar 22, 2023 · 1 comment
Closed

Migrate from Gradle and gradle-jpi-plugin to Maven and maven-hpi-plugin #321

basil opened this issue Mar 22, 2023 · 1 comment

Comments

@basil
Copy link
Member

basil commented Mar 22, 2023 •
edited
Loading

Gradle and gradle-jpi-plugin are no longer a fully supported build system for Jenkins plugins. allure-plugin is the second most popular non-deprecated Jenkins plugin built with Gradle and gradle-jpi-plugin.

Our fully supported build system for Jenkins plugins is Maven and maven-hpi-plugin. To ensure the long-term viability of allure-plugin, we recommend migrating to Maven and maven-hpi-plugin.

For examples, see jenkinsci/ivy-plugin#49 and jenkinsci/job-dsl-plugin#1265.

CC @eroshenkoam
@basil basil changed the title Migrate from Gradle to Maven and gradle-jpi-plugin to maven-hpi-plugin Migrate from Gradle and gradle-jpi-plugin to Maven and maven-hpi-plugin Mar 22, 2023
@vbragin
Copy link
Collaborator

vbragin commented Apr 7, 2023

Will be done with #322

@vbragin vbragin closed this as completed Apr 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@basil @vbragin