maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominik Bartholdi (JIRA)" <j...@codehaus.org>
Subject [jira] (MRELEASE-736) Add dryRun flag to release:perform
Date Sat, 10 Mar 2012 09:47:03 GMT

    [ https://jira.codehaus.org/browse/MRELEASE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293768#comment-293768
] 

Dominik Bartholdi commented on MRELEASE-736:
--------------------------------------------

I would just say what it normally would do...
But there is one more thing which I think would be a good thing in a dryRun: check whether
the credentials work e.g. check if the build would at least be allowed to connect to the location
where the site should be deployed to.
This is an annoying thing in most of the dryRun implementations, because a dryRun should test
as many of the preconditions as possible but most do not test whether the configured connections
would actually work. Specially in this case: if the release works fine, but the deploy of
the site would fail - then a release job would be marked as failed - but in fact the artifact
was released, but just not the site which leafs the user in an unsure state: "what should
I do now? start over and create another version/release?"
                
> Add dryRun flag to release:perform
> ----------------------------------
>
>                 Key: MRELEASE-736
>                 URL: https://jira.codehaus.org/browse/MRELEASE-736
>             Project: Maven 2.x Release Plugin
>          Issue Type: Improvement
>          Components: perform
>    Affects Versions: 2.2.2
>         Environment: mvn 3.0.3
>            Reporter: Dominik Bartholdi
>            Assignee: Robert Scholte
>
> Please consider to add the "dryRun" flag from the "release:prepare" to the "release:perform"
goal too.
> I have the following use case:
> Jenkins/Hudson has a plugin called m2release which basically is there to help the user
to trigger a maven release. This plugin allows to define a commandline which should be executed
in case of a release build. The common configuration of this arguments are:
> "-Dresume=false release:prepare release:perform"
> the next version of the plugin would like to add a "dryRun" option when triggering a
build and in this case it would just add "-DdryRun=true" to the configured arguments and thats
it.
> Unfortunately this will not work, as the "release:perform" still gets executed and will
fail.
> Of course I could also change the Jenkins/Hudson plugin, but this would mean I have to
remove "release:perform" from the passed argument, which is relay ugly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message