Release Plugin

Allow publish-plugin in non-interactive mode

Details

  • Type: Improvement Improvement
  • Status: Resolved Resolved
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 1.0.0.RC3
  • Fix Version/s: 1.0.1
  • Labels:
    None

Description

The old release-plugin in grails 1.3.x was able to be used in an automated script by provided the necessary passwords etc and setting the non-interactive flag. The replacement publish-plugin also allows putting passwords in a file, but only for the plugin repository, not for scm (i.e. tagging). Our use case is subversion for the code repository, and maven for the plugin repository. We are still prompted for the subversion commit message and username/password when attempting to release with the --non-interactive option. Please add a method for putting the subversion credentials in a file and the commit message on the command line. If there is already a way to do this, I was not able to find in the documentation. Thanks.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Peter Ledbrook added a comment -

This is certainly doable. Do you also need it to auto-commit any modified files? I think that would require a change to the Subversion plugin as well.

Show
Peter Ledbrook added a comment - This is certainly doable. Do you also need it to auto-commit any modified files? I think that would require a change to the Subversion plugin as well.
Hide
Permalink
Peter Ledbrook added a comment -

Please try plugin version 1.0.0.BUILD-SNAPSHOT. You should then be able to use a --message argument for the command and add the Subversion username and password to ~/.grails/settings.groovy under the config options grails.project.scm.username/password.

Show
Peter Ledbrook added a comment - Please try plugin version 1.0.0.BUILD-SNAPSHOT. You should then be able to use a --message argument for the command and add the Subversion username and password to ~/.grails/settings.groovy under the config options grails.project.scm.username/password .
Hide
Permalink
Peter Ledbrook added a comment -

Actually, --message won't work on *nix platforms currently. May need to think of an alternative.

Show
Peter Ledbrook added a comment - Actually, --message won't work on *nix platforms currently. May need to think of an alternative.
Hide
Permalink
Peter Ledbrook added a comment -

Well, apparently you can do something like:

grails publish-plugin --message=\"This is a test commit message.\"
Show
Peter Ledbrook added a comment - Well, apparently you can do something like: grails publish-plugin --message=\"This is a test commit message.\"
Hide
Permalink
Craig Leyshan added a comment -

Thanks Peter, I'll give it a try

Show
Craig Leyshan added a comment - Thanks Peter, I'll give it a try
Hide
Permalink
Craig Leyshan added a comment - - edited

No go. I was still prompted for a username and password. I think a change is needed in the svn plugin - if you call scm.auth() too early the svnClient instance variable is not instantiated and the credentials do not get assigned.

Show
Craig Leyshan added a comment - - edited No go. I was still prompted for a username and password. I think a change is needed in the svn plugin - if you call scm.auth() too early the svnClient instance variable is not instantiated and the credentials do not get assigned.
Hide
Permalink
Peter Ledbrook added a comment -

Ah, I was caught out by the key chain in Mac OS X. This is indeed a bug in the Subversion plugin. Working on it now.

Show
Peter Ledbrook added a comment - Ah, I was caught out by the key chain in Mac OS X. This is indeed a bug in the Subversion plugin. Working on it now.
Hide
Permalink
Peter Ledbrook added a comment -

Fixed in the Release plugin and the Subversion plugin.

Show
Peter Ledbrook added a comment - Fixed in the Release plugin and the Subversion plugin .

People

  • Assignee:
    Peter Ledbrook
    Reporter:
    Craig Leyshan
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: