[
https://issues.apache.org/jira/browse/COMMONSSITE-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16478084#comment-16478084
]
Rob Tompkins commented on COMMONSSITE-111:
------------------------------------------
[~garydgregory] thoughts on this? I think doing promotion of the SVN repo isn't
going to be too too hard, but it would be nice if it also performed the
promotion of the nexus repository. To really automate that, assuming no
pre-knowledge of the release, I would think that we would need to download one
of the -bin artifacts from the SVN dist location, unpack it, get the sha1 (or
whichever signature) of one of the artifacts in it. Then we'd need to go and
RESTfully search through the existing staging repos in nexus to find the
matching staging repo, and then we'd release that one.
The problem here is that testing this is, well, kinda scary. I know I can write
unit tests, but you quickly run into the problem of you can't test for what you
can't think to test for.
> [release-plugin] create mojo for release promotion in svn
> ---------------------------------------------------------
>
> Key: COMMONSSITE-111
> URL: https://issues.apache.org/jira/browse/COMMONSSITE-111
> Project: Commons All
> Issue Type: Improvement
> Reporter: Rob Tompkins
> Assignee: Rob Tompkins
> Priority: Major
>
> Currently we have to run a series of svn commands to promote releases. It
> would be nice if the release plugin did this for us.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
