www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (Issue Comment Edited) (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (INFRA-4144) Allow Nexus to act as staging repo for /dist mirrors
Date Wed, 23 Nov 2011 17:53:40 GMT

    [ https://issues.apache.org/jira/browse/INFRA-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13155998#comment-13155998
] 

Sebb edited comment on INFRA-4144 at 11/23/11 5:53 PM:
-------------------------------------------------------

quote: "This only gets you half way, but less manual steps. You would still need to copy them
to /dist"

But that is the whole point of this JIRA!

All ASF projects need to generate release packages (source, and optionally binary) that are
published via the mirroring system.
This currently requires the relevant packages to be copied to www.apache.org/dist/TLP on people.apache.org.
[Note: this also ensures that the packages end up on http://archive.apache.org/dist/]

Many ASF projects also create Maven packages, for which Nexus works well.

It would be very convenient if Nexus could act as a staging repo for non-Maven artifacts as
well; hence this JIRA.
                
      was (Author: sebb@apache.org):
    bq. This only gets you half way, but less manual steps. You would still need to copy them
to /dist

But that is the whole point of this JIRA!

All ASF projects need to generate release packages (source, and optionally binary) that are
published via the mirroring system.
This currently requires the relevant packages to be copied to www.apache.org/dist/TLP on people.apache.org.
[Note: this also ensures that the packages end up on http://archive.apache.org/dist/]

Many ASF projects also create Maven packages, for which Nexus works well.

It would be very convenient if Nexus could act as a staging repo for non-Maven artifacts as
well; hence this JIRA.
                  
> 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 Demers
>
> 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