gradle-release-plugin | A modern release plugin for gradle | Plugin library
kandi X-RAY | gradle-release-plugin Summary
kandi X-RAY | gradle-release-plugin Summary
Gradle releases made easy. Other release processes force you to store your versioning information inside the project files such as build.gradle; this plugin keeps versions where they belong, in your version control system. We currently support subversion or git. Additional SCM choices are easy to add.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of gradle-release-plugin
gradle-release-plugin Key Features
gradle-release-plugin Examples and Code Snippets
buildscript {
repositories {
mavenCentral()
maven {
url 'http://maven.tmatesoft.com/content/repositories/releases/'
}
}
dependencies {
classpath 'au.com.ish.gradle:release:2.2.2'
}
}
apply plugin: 'release'
release {
1. If the releaseVersion property was passed to gradle via the -P command line option, then use that.
2. If the version control system is currently pointing to a tag, then use a version derived from the name of the tag
3. Use the name of the branch (
version = release.projectVersion
gradle assemble -PreleaseVersion=2.0-SNAPSHOT
Community Discussions
Trending Discussions on gradle-release-plugin
QUESTION
At my workplace, we use a monthly release branch that's shared across several developers.
Gradle version is 2.14.1
We manually trigger the code build and release (task) using Jenkins (which is effective running - gradle clean compileJava release)
The whole process takes about 30-40 minutes, basically compiling, generating the artifacts, running Junit tests and uploading the artifacts to the Artifactory.
Eventually it comes to the step of tagging and pushing the version number: preTagCommit, which tries to update the gradle.properties and bumps up the version number to it and commits and pushes.
At this point, if there have been no commits on the branch for the last 30-40 minutes (Since the build was manually triggered), the release works successfully.
The moment there is even a single commit between the whole process it fails with error: Execution failed for task ':preTagCommit'.
...ANSWER
Answered 2020-May-08 at 05:30I believe the flag you're looking for is mentioned in the GitHub page of the plugin:
Eg. To ignore upstream changes, change 'failOnUpdateNeeded' to false:
QUESTION
I am in the process of converting the existing maven project to Gradle for which I want to use alternative for maven release plugin. Mainly the functionality to remove snapshot and autoincrement by 1 once the release is cut. I came across to use researchgate gradle-release-plugin but need to identify how can I use to this to achieve maven like functionality described above.
I am trying for the first time and gone through below URL: https://github.com/researchgate/gradle-release
...ANSWER
Answered 2019-Jan-08 at 11:31it is called Maven Publish Plugin:
QUESTION
I'm using researchgate's gradle release plugin to perform version management and maven-publish
plugin to upload generated artifact to a private maven repository. When I run gradle-release-plugin's release task it runs following sub-tasks (user-dao-plugin is my dummy project's name) -
ANSWER
Answered 2017-Aug-03 at 06:58@Vampire irrespective of the order, can you tell how to run publish
after any release
sub task?
Based on your last comment, what you are after is
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install gradle-release-plugin
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page