www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Demers (Assigned) (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (INFRA-4144) Allow Nexus to act as staging repo for /dist mirrors
Date Tue, 10 Jan 2012 21:33:39 GMT

     [ https://issues.apache.org/jira/browse/INFRA-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brian Demers reassigned INFRA-4144:
-----------------------------------

    Assignee: Brian Fox  (was: Brian Demers)
    
> Allow Nexus to act as staging repo for /dist mirrors
> ----------------------------------------------------
>
>                 Key: INFRA-4144
>                 URL: https://issues.apache.org/jira/browse/INFRA-4144
>             Project: Infrastructure
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: Nexus
>            Reporter: Sebb
>            Assignee: Brian Fox
>
> Nexus is generally used to stage Maven artifacts for release votes.
> It's possible to use Nexus to store the non-Maven archives so that there is a single
public download location for the release vote.
> However, the non-Maven archives have to manually copid to the /dist mirror when the vote
succeeds.
> They then have to be deleted from the staging area before it is released/promoted.
> This is tedious and error-prone.
> It would be very useful if Nexus could also be used for staging the archives intended
for the dist mirrors (non-Maven)
> The process would be:
> - RM uploads both the Maven and non-Maven artifacts to Nexus, e.g. using "mvn deploy"
(but see below)
> - RM checks the contents and closes the staging repo
> - run the vote using the public staging repo as the source location for all release packages
> - if the vote succeeds, releasing/promoting the staging repo would publish the Maven
artifacts to the Maven releases repo, and publish the non-Maven archives to the /dist mirror
area.
> The Nexus GUI needs to have some way to distinguish which packages are Maven packages,
and which are not.
> This is essential to ensure that the packages will be correctly deployed.
> Perhaps by using a different directory in the same part of the tree?
> It also needs to be possible to easily upload non-Maven packages without using Maven.
> The intention is to have a single staging location which can be used for all Apache releases,
whether using Maven or not.
> P.S. I'm happy to help with testing this. I suggest setting up a dummy project for the
purpose.

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

        

Mime
View raw message