infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (INFRA-18458) Hosting of Maven snapshot artefacts for Apache Netbeans
Date Tue, 18 Jun 2019 02:44:00 GMT

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

Chris Lambertus resolved INFRA-18458.
-------------------------------------
    Resolution: Fixed
      Assignee: Chris Lambertus

Everything looks fine.


> Hosting of Maven snapshot artefacts for Apache Netbeans
> -------------------------------------------------------
>
>                 Key: INFRA-18458
>                 URL: https://issues.apache.org/jira/browse/INFRA-18458
>             Project: Infrastructure
>          Issue Type: Wish
>          Components: Nexus
>            Reporter: Eric Barboni
>            Assignee: Chris Lambertus
>            Priority: Minor
>
> Hi, 
>  I'm lacking the word. 
>  With great help of Infra, Apache NetBeans can stage and populate on nexus for release
version of the maven artefacts.
>  Basic workflow are : (jenkins build at asf, zip retrival by release manager, signing
by release manager + populating staging via nexus plugin+ vote + release) 
>  We would like to have also the  SNAPSHOT artifacts. The volume is huge and tesselated
(550Mo, lots of file). 
> It should be not human signed it's too long for build per day. It's only required to
have the last SNAPSHOT version (not the n last timestamped)
> I don't know if repository.apache.org can handle that. As I mention in slack maybe also
possible to setup an Apache Archiva server in a vm.
> Staged repo stay for a short amount of time. 
> Snapshot repo will be online permanently for more test potentially than staged.
> I hope it's possible to determine a solution. I will be happy to clarify.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message