Opened 4 years ago

Last modified 4 years ago

#2498 new task

deegree maven repository

Reported by: Tfr42 Owned by: sac@…
Priority: normal Milestone: Unplanned
Component: SysAdmin Keywords:
Cc:

Description

The deegree project would like to publish it's build and release artifacts on the OSGeo Nexus Maven repository. And is asking for access rights to upload artifacts using the project's Jenkins build server.

See issue https://github.com/deegree/deegree3/issues/1075 for further information

Change History (6)

comment:1 by robe, 4 years ago

Torsten since you have been approved for SAC membership I have made you an admin of the repo.osgeo.org nexus instance.

You should be able to create degree project now.

comment:2 by robe, 4 years ago

I also added you to the shell group and also gave you admin rights to the nexus container on osgeo3 where repo.osgeo.org resides in case you need filesystem access.

In order to access these - you'll need to register your ssh keys and also setup yourself as detailed in

https://wiki.osgeo.org/wiki/SAC_Service_Status#sshing_into_osgeo3_containers

comment:3 by Tfr42, 4 years ago

Ok, thank you. Access to gitea and nexus admin UI works.

Is there any further documentation available about naming conventions of hosted repositories and their configuration?

comment:4 by robe, 4 years ago

Yes Jody did establish naming conventions which are described in below link

https://wiki.osgeo.org/wiki/SAC:Repo#Repositories

This was my attempt at explaining the docker setup and basic naming:

https://wiki.osgeo.org/wiki/SAC:Repo#Docker_Instructions_for_OSGeo_Projects_Teams

Feel free to amend that if you see any errors are things you'd like changed (now that you are a repo admin :) )

comment:5 by jive, 4 years ago

Please ask me any questions, would like to keep things consistent.

Note we are having some trouble managing snapshots at present (there are two different mechanisms and we found that setting up a task for each snapshot repository worked)

comment:6 by jive, 4 years ago

Okay the trouble managing snapshot clean has been resolved, was being a bit too aggressive cleaning them up.

Note: See TracTickets for help on using tickets.