-
New Feature
-
Resolution: Won't Do
-
Minor
-
None
When doing Jenkins plugin development, I have found that I have been able to
do almost everything that I could do in mvn quite nicely:
| mvn command | gradle command, with gradle-jpi-plugin |
|---|---|
| mvn build | gradle build |
| mvn test | gradle test |
| mvn clean | gradle clean |
| mvn hpi:run | gradle server |
| mvn release:prepare | ????? |
| mvn release:perform | gradle publish |
In gradle-jpi-plugin, there does not seem to be an equivalent to mvn release:prepare
It would be nice to add an equivalent task. That way gradle-jpi-plugin could replace
pretty much all the tasks that are commonly used for Jenkins plugin development with mvn.
I don't know which is the best way to go. The gradle-git plugin is one option.
On that plugin's wiki, he mentions several alternatives:
https://github.com/ajoberstar/gradle-git/wiki/Release-Plugins#other-options
The researchgrate/gradle-release (formerly townsfolk/gradle-release) plugin looks the most similar to mvn release:prepare.
[JENKINS-35401] Need equivalent to mvn release:prepare
Craig Rodrigues
created issue -
| Workflow | Original: JNJira [ 171694 ] | New: JNJira + In-Review [ 184413 ] |
Daniel Spilker
made changes -
| Issue Type | Original: Bug [ 1 ] | New: New Feature [ 2 ] |
Daniel Spilker
made changes -
| Assignee | Original: Daniel Spilker [ daspilker ] | New: Steve Hill [ sghill ] |
Steve Hill
added a comment - Closing this as out of scope for the gradle-jpi-plugin.
There are several options for replacing the maven-release-plugin to suite different needs. nebula.release is another option not already listed.
Consider raising this with the Gradle team for the guide Migrating Builds From Apache Maven
I don't know which is the best way to go.
I'd suggest starting with a popular option and seeing if it meets your needs. One reason there are so many options is because the needs of versioning can vary quite a lot with the delivery workflow.
Steve Hill
added a comment - Closing this as out of scope for the gradle-jpi-plugin.
There are several options for replacing the maven-release-plugin to suite different needs. nebula.release is another option not already listed.
Consider raising this with the Gradle team for the guide Migrating Builds From Apache Maven
I don't know which is the best way to go.
I'd suggest starting with a popular option and seeing if it meets your needs. One reason there are so many options is because the needs of versioning can vary quite a lot with the delivery workflow. Steve Hill
made changes -
| Resolution | New: Won't Do [ 10001 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
There are several plugins which provide this feature. Rather than adding a release task to the Gradle JPI plugin, we should just describe how to use one of the existing plugins to cut a release.