netzwerg / gradle-release-plugin Goto Github PK

The docs say, MAJOR.MINOR.PATCH[-SNAPSHOT] is the expected pattern. But, what I just found out is that MAJOR.MINOR[-SNAPSHOT] works as well (which is great). The docs could be more clear about that.

or am I mistaking?

If plugins are applied in "wrong" order, some artifacts which base their names on project.version are named incorrectly because the property is not initialized yet

Requires partial revert of #12

I'm pretty sure you can do a release on GitHub through their REST API.
To be consistent, the same versions, titles, etc. should be used (where there is an overlap).

My Android project have multiple flavor. e.g , brand_1 , brand_2 and brand_3 i would like to maintain the separate version.txt file each flavor. Looks there is no support on the current version. Could you please add the support ?

If the git push command fails (for example, because someone else pushed a commit up while the release was running), then the release task should fail, but it does not. Instead, the build continues.

Thereby replacing project.ext.versionFile

Hello everyone.

I'm wondering why I cannot push from some machines (in this case centos).

I got always the next issue after run gradle release

> Task :shadowJar
> Task :release
To [email protected]:group*/some-repo-path.git
 * [new tag]         v1.0.14 -> v1.0.14
error: unable to push to unqualified destination: HEAD
The destination refspec neither matches an existing ref on the remote nor
begins with refs/, and we are unable to guess a prefix based on the source ref.
error: failed to push some refs to '[email protected]:group*/some-repo-path.git'

Do you have any idea about this?

Thanks in advance

In other words: Offer 'vanilla' behavior which doesn't need configuration at all

Currently, the following tasks exist:

• release
• releaseMinorVersion
• releaseMajorVersion

The release task creates a patch release.

For consistency reasons, a releasePatchVersion task should be introduced. For backwards compatibility, release should be kept as an alias.

Hi
I've added your plugin to my build.gradle file:

buildscript {
    repositories {
        jcenter()
    }
    dependencies {
        classpath "com.github.jengelman.gradle.plugins:shadow:1.2.3"
        classpath 'ch.netzwerg:gradle-release-plugin:1.1.0'
    }
}

plugins {
    //Gradle release plugin from: https://github.com/netzwerg/gradle-release-plugin
    id 'ch.netzwerg.release' version '1.1.0'
}

subprojects {
    group 'myGroup'

    version '1.0.0.0-SNAPSHOT'

    apply plugin: 'java'

    apply plugin: 'com.github.johnrengelman.shadow'
    apply plugin: 'maven'

    // Use Java 8
    sourceCompatibility = 1.8

    repositories {
        mavenLocal()
        jcenter()
        maven {
             // Repositories we use
        }
    }

    dependencies {

        // Dependencies we use
    }

}

When I run:

gradle tasks

I get the following error:

FAILURE: Build failed with an exception.

• What went wrong:
  Execution failed for task ':tasks'.

  Could not determine the dependencies of task ':release'.

Is it necessary to have a separate version.txt in all subprojects? or am I doing something wrong? I have a version.txt in the main project root also.

A problem occurred evaluating root project 'zipkin'.
> Failed to apply plugin [id 'ch.netzwerg.release']
   > /Users/main_project/subproject/version.txt (No such file or directory)

Is there any way to build and publish release artifacts:

• build snapshot
• update version
• commit version
• push version
• tag version
• build release
• publish release
• update version
• commit version
• push version

git push origin HEAD

A handy way to push the current branch to the same name on the remote.
git push documentation

• LICENSE file in root
• License header in source

Using project.afterEvaluate to trigger project version initialization causes trouble in multi-project builds (subproject-versions not properly initialized).

commitVersionFile("Release v$project.version", releaseExtension)

this leads to the problem that when git command is called it cant interprete correctly:

git commit -m Release v0.0.1 version.txt

vs

git commit -m "Release v0.0.1" version.txt

First of thanks for the plugin. I like the plugins outstanding simplicity.

I have a question regarding the version.txt file. Why is it needed? Would it not be better to just update the gradle build file instead?

Allow to bump up major, minor, or patch version through different Gradle tasks.

I am calling gradle -x test -s -d release -Prelease.push=true from my Jenkins/CI server to create tag and push the changes into git.

From the debug output I see that a tag was committed successfully but it is never pushed to origin/remote.

14:37:51.655 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Changing state to: STARTING
14:37:51.657 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Waiting until process started: command 'git'.
14:37:51.661 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Changing state to: STARTED
14:37:51.662 [DEBUG] [org.gradle.process.internal.ExecHandleRunner] waiting until streams are handled...
14:37:51.663 [INFO] [org.gradle.process.internal.DefaultExecHandle] Successfully started process 'command 'git''
14:37:51.695 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Changing state to: SUCCEEDED
14:37:51.696 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Process 'command 'git'' finished with exit value 0 (state: SUCCEEDED)
14:37:51.697 [DEBUG] [ch.netzwerg.gradle.release.ReleaseTask] [detached HEAD 593f269] Prepare next release v0.0.6-SNAPSHOT

when adding the push entry in my build.gradle it is working.

release{
   push=true
}

is the parameter -Prelease.push=true incorrect?

Hi,

The plugin has worked well on MacOS, running the gradle script on a Windows machine using GitBash, the following error results. Is this an issue with the use of Single Quotes rather than Double Quotes? If so, what recommendations do you have for resolving this?

Thanks!

:releaseerror: pathspec 'version.txt' did not match any file(s) known to git.
FAILED

FAILURE: Build failed with an exception.

• What went wrong:
  Execution failed for task ':release'.

Process 'command 'git'' finished with non-zero exit value 1

Gradle supports usage of abbreviated task names, e.g. relMinVer instead of releaseMinorVersion. The plugin's strategy resolution fails when an abbreviated task name is being used.

This seems to be a fairly simple but very useful plugin. I got a questions:

1. how to configure authentication username/password for git
2. Is there releasePatch task?

Thanks
-cl

Regardless of whether I run "release", "releaseMinorVersion", or "releaseMajorVersion" the version always increments the last number. So "1.0.0-SNAPSHOT" will increment to "1.0.1-SNAPSHOT"

I think this is the offending line, but I'm not familiar enough with gradle plugins to be sure:
https://github.com/netzwerg/gradle-release-plugin/blob/master/src/main/groovy/ch/netzwerg/gradle/release/ReleaseTask.groovy#L58

A release block without setting the 'dependsOn' property fails the build

Hello Rahel,

I enabled to push on release and I now have the problem that the plugin is pushing to a new master branch. On the screenshot you see TAG 1.0.1. This was actually my master brach 19da802 it now became 1.0.1

On the second screenshot you can see that the current master is a complete new branch.

Jenkins is checking out the code in this way

Checking out Revision 19da802c997053214cef316e895e018089286c11 (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 19da802c997053214cef316e895e018089286c11 # timeout=10
 > git branch -a -v --no-abbrev # timeout=10
 > git checkout -b master 19da802c997053214cef316e895e018089286c11
 > git rev-list 19da802c997053214cef316e895e018089286c11 # timeout=10

Is this normal behavior