[MRELEASE-839] Unable to supply tag to release for release:perform

[jira-importer]

Tuure Laurinolli opened MRELEASE-839 and commented

The documentation at http://maven.apache.org/maven-release/maven-release-plugin/examples/perform-release.html and http://maven.apache.org/maven-release/maven-release-plugin/plugin-info.html claims that releases can be ma de of a specific tag, but no mechanism for this is specified.

---

Affects: 2.4.1

Issue Links:

• MRELEASE-796 Add AbstractScmReleaseMojo

Remote Links:

• GitHub Pull Request #149
  

3 votes, 10 watchers

[jira-importer]

Tuure Laurinolli commented

This is actually a regression since MRELEASE-796.

[jira-importer]

Tuure Laurinolli commented

This is a regression caused by the fix to MRELEASE-796.

[jira-importer]

Robert Scholte commented

Duplicate of MRELEASE-832?

[jira-importer]

Anders Hammar commented

I don't understand the description of this issue. In the docs for 2.4.2 it is very clear what the command is. For example:

mvn release:perform -DconnectionUrl=scm:svn:https://svn.apache.org/repos/asf/maven/plugins/tags/maven-release-plugin-2.0

Please clarify or this ticket will be closed as incomplete!

[jira-importer]

John Gibson commented

What would the connectionUrl be for git? The Maven SCM documentation for git doesn't give a method for specifying a tag via the URL. I tried the obvious approach of -DconnectionUrl=scm:git:ssh://nowhere.invalid/foo.git/tagname, but that didn't work.

[jira-importer]

Anders Hammar commented

Not sure what scm this ticket is for; it doesn't say.

@John: Maybe the docs need to be improved wrt git, but that would be a different ticket. Please create one if one doesn't exist already!

[jira-importer]

Tuure Laurinolli commented

We are using Git.

@Anders, Are you proposing to improve the documentation to say that performing releases of specific tags is not possible with Git?

[jira-importer]

Josh Spiewak commented

I think the problem may be that the other mojos were all updated to extend the new AbstractScmReleaseMojo while PerformReleaseMojo still extends AbstractReleaseMojo. Thus mvn release:perform does not have access to the tag that is passed in, and the git scm provider tries to run git clone --branch <repo> <directory>. Since the tag is missing from the command, you get an error:

[ERROR] The git-clone command failed.
[ERROR] Command output:
[ERROR] fatal: repository '/Users/jspiewak/work/bc/mrptest/target/checkout' does not exist

This is still an issue with 2.5

[jira-importer]

Tuure Laurinolli commented

Yes, as I noted in MRELEASE-796.

[jira-importer]

Ravi Wallau commented

Hi:

Do you know if there is a workaround for this issue? We rely on releasing from a tag with different profiles (heavily, I should say). The source code is always the same, just the profile is different.

I will do some more research on this topic.

Regards, Ravi.

[jira-importer]

Archimedes Trajano commented

The workaround that I used is to create a release.properties file containing both the scm.url and scm.tag I have documented it here https://trajano.net/2017/03/maven-deploy-using-travis/3/ and provided an example in https://github.com/trajano/trajano/blob/master/.travis.yml

[jira-importer]

Vilius Šumskas commented

Almost 10 year later this is still not fixed :( Can we at least have MRELEASE-796 reverted, so we continue using release:perform on a git tag? These changes didn't add any real value and just broke everything.

[jira-importer]

Slawomir Jaranowski commented

Probably we need to add tag parameter to perform mojo.
and use it eg:

releaseDescriptor.setScmReleaseLabel( tag )

near

releaseDescriptor.setScmUsername( username );

Finally some IT test will be appreciated for it.

So PR are welcome, or more investigation.

[jira-importer]

Slawomir Jaranowski commented

There is proposition to extends documentations: #119

[jira-importer]

Vilius Šumskas commented

I can do tests if needed however I'm not Java developer so I'm unable to provide PR. The main issue here is that since changes in MRELEASE-796 arguments to git is passed incorrectly.

 

Tests I performed

This works without errors:

 

mvn org.apache.maven.plugins:maven-release-plugin:2.2.2:perform -DconnectionUrl=scm:git:https://gitlab.com/fake/r365-autoconfig.git -Dtag=0.1.14 -DuseReleaseProfile=false

[INFO] Executing: cmd.exe /X /C "git clone https://gitlab.com/fake/r365-autoconfig.git C:\temp1\r365-autoconfig\target\checkout"
[INFO] Executing: cmd.exe /X /C "git ls-remote https://gitlab.com/fake/r365-autoconfig.git"
[INFO] Executing: cmd.exe /X /C "git fetch https://gitlab.com/fake/r365-autoconfig.git"
[INFO] Executing: cmd.exe /X /C "git checkout 0.1.14"
...build starts

 however you cannot use it -DlocalCheckout=true:

 

mvn org.apache.maven.plugins:maven-release-plugin:2.2.2:perform -DconnectionUrl=scm:git:https://gitlab.com/fake/r365-autoconfig.git -Dtag=0.1.14 -DuseReleaseProfile=false -DlocalCheckout=true

 

 

[INFO] Executing: cmd.exe /X /C "git clone file://C\temp1\r365-autoconfig C:\temp1\r365-autoconfig\target\checkout"
[INFO] Working directory: C:\temp1\r365-autoconfig\target
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.2.2:perform (default-cli) on project r365-autoconfig: Unable to checkout from SCM
[ERROR] Provider message:
[ERROR] The git-clone command failed.
[ERROR] Command output:
[ERROR] Cloning into 'C:\temp1\r365-autoconfig\target\checkout'...
[ERROR] fatal: '/C/temp1/r365-autoconfig' does not appear to be a git repository

 

 

With 2.3.2 it works, and this time you can use it with localCheckout too:

 

mvn org.apache.maven.plugins:maven-release-plugin:2.3.2:perform -DconnectionUrl=scm:git:https://gitlab.com/fake/r365-autoconfig.git -Dtag=0.1.14 -DuseReleaseProfile=false

 

[INFO] Executing: cmd.exe /X /C "git clone --branch 0.1.14 https://gitlab.com/fake/r365-autoconfig.git C:\temp1\r365-autoconfig\target\checkout"
[INFO] Executing: cmd.exe /X /C "git ls-remote https://gitlab.com/fake/r365-autoconfig.git"
[INFO] Executing: cmd.exe /X /C "git fetch https://gitlab.com/fake/r365-autoconfig.git"
[INFO] Executing: cmd.exe /X /C "git checkout 0.1.14"
...build starts

 

mvn org.apache.maven.plugins:maven-release-plugin:2.3.2:perform -DconnectionUrl=scm:git:https://gitlab.com/fake/r365-autoconfig.git -Dtag=0.1.14 -DuseReleaseProfile=false -DlocalCheckout=true

[INFO] Executing: cmd.exe /X /C "git clone --branch 0.1.14 file:///C:\temp1\r365-autoconfig C:\temp1\r365-autoconfig\target\checkout"
[INFO] Executing: cmd.exe /X /C "git ls-remote file:///C:\temp1\r365-autoconfig"
[INFO] Executing: cmd.exe /X /C "git fetch file:///C:\temp1\r365-autoconfig"
[INFO] Executing: cmd.exe /X /C "git checkout 0.1.14"
..build starts

 

Anything above 2.3.2 produces errors with or without localCheckout:

mvn org.apache.maven.plugins:maven-release-plugin:2.5.2:perform -DconnectionUrl=scm:git:https://gitlab.com/fake/r365-autoconfig.git -Dtag=0.1.14 -DuseReleaseProfile=false

[INFO] Executing: cmd.exe /X /C "git clone --branch https://gitlab.com/fake/r365-autoconfig.git C:\temp1\r365-autoconfig\target\checkout"
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.2:perform (default-cli) on project r365-autoconfig: Unable to checkout from SCM
[ERROR] Provider message:
[ERROR] The git-clone command failed.
[ERROR] Command output:
[ERROR] Cloning into 'checkout'...
[ERROR] fatal: Remote branch https://gitlab.com/fake/r365-autoconfig.git not found in upstream origin

mvn org.apache.maven.plugins:maven-release-plugin:3.0.0-M5:perform -DconnectionUrl=scm:git:https://gitlab.com/fake/r365-autoconfig.git -Dtag=0.1.14 -DuseReleaseProfile=false

[INFO] Executing: cmd.exe /X /C "git clone --depth 1 --branch https://gitlab.com/fake/r365-autoconfig.git checkout"
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:3.0.0-M5:perform (default-cli) on project r365-autoconfig: Unable to checkout from SCM
[ERROR] Provider message:
[ERROR] The git-clone command failed.
[ERROR] Command output:
[ERROR] fatal: repository 'checkout' does not exist