SAC:Repo - Revision history

Wiki-Sfrey: Fix typo.

2021-02-05T07:39:17Z

Fix typo.

Robe at 20:32, 28 May 2020

2020-05-28T20:32:03Z

Jive: /* How to use OSGeo Maven repository */

2020-05-11T19:42:43Z

How to use OSGeo Maven repository

Jive at 19:38, 11 May 2020

2020-05-11T19:38:58Z

Jive at 19:38, 11 May 2020

2020-05-11T19:38:37Z

Jive: /* Maven Instructions for OSGeo Projects */

2020-04-27T17:38:38Z

Maven Instructions for OSGeo Projects

Jive: /* Repositories */

2020-04-27T17:31:24Z

Repositories

Jive: /* Repositories */

2020-04-27T17:24:52Z

Repositories

Jive: /* Repositories */

2020-04-27T17:23:19Z

Repositories

Jive: /* Repositories */

2020-04-27T17:12:39Z

Repositories

@@ Line 99: / Line 99: @@
 To integrate repo.osgeo.org as a remote repository into artifactory:
-. Use the nexus URL: https://repo.osgeo.org/repository/releases/
+. Use the nexus URL: https://repo.osgeo.org/repository/release/
 . Note that testing the URL before saving it will give a 404 warning

← Older revision		Revision as of 20:32, 28 May 2020
Line 272:		Line 272:

	[[Category:Infrastructure]]		[[Category:Infrastructure]]
		+	[[Category:Services]]

@@ Line 27: / Line 27: @@
    </repositories>
 </pre>
 == How to fix a broken build ==

@@ Line 87: / Line 87: @@
 For additional information, including how to make use of SNAPSHOTS, please see GeoTools User Guide [https://docs.geotools.org/latest/userguide/welcome/upgrade.html Upgrade Instructions].
-=== How to integrate with Artifactory as a remote repository ===
+== How to integrate with Artifactory as a remote repository ==
 A [https://community.sonatype.com/t/maven-nexus-v3-remote-repository-integration-with-artifactory/2149 known issue] with Artifactory integration written for Nexus 2. We use Nexus 3 leading to the following workaround:

← Older revision		Revision as of 19:38, 11 May 2020
Line 86:		Line 86:

	For additional information, including how to make use of SNAPSHOTS, please see GeoTools User Guide [https://docs.geotools.org/latest/userguide/welcome/upgrade.html Upgrade Instructions].		For additional information, including how to make use of SNAPSHOTS, please see GeoTools User Guide [https://docs.geotools.org/latest/userguide/welcome/upgrade.html Upgrade Instructions].
		+
		+	=== How to integrate with Artifactory as a remote repository ===
		+
		+	A [https://community.sonatype.com/t/maven-nexus-v3-remote-repository-integration-with-artifactory/2149 known issue] with Artifactory integration written for Nexus 2. We use Nexus 3 leading to the following workaround:
		+
		+	To integrate repo.osgeo.org as a remote repository into artifactory:
		+
		+	1. Use the nexus URL: https://repo.osgeo.org/repository/releases/
		+
		+	2. Note that testing the URL before saving it will give a 404 warning
		+
		+	3. After running your maven build artifactory will be able to fetch the the artifacts
		+
		+	This problem occurs as the artifactory test expects to be able to browse to the Nexus URL location. However in Nexus 3 repository URLs are machine readable, with a separate URL for browsing.

	== Maven Instructions for OSGeo Projects ==		== Maven Instructions for OSGeo Projects ==

@@ Line 93: / Line 93: @@
 . Before you start, you will need an [https://www.osgeo.org/community/getting-started-osgeo/osgeo_userid/ OSGeo User ID]
-. Create a TRAC ticket https://trac.osgeo.org/osgeo requesting repo access with the name of your project, and OSGeo UserID requiring access.
+. Create a TRAC ticket https://trac.osgeo.org/osgeo requesting repo access with the name of your project, and OSGeo UserID requiring access. A project repository (maphappy-releases) will be setup, with access granted to the OSGeo UserID requested.
 . Update your '''pom.xml''' repositories with osgeo release repository.

@@ Line 236: / Line 236: @@
 * snapshot_policy (cleanup policy) - unused as we have switched to using tasks below. We experimented with defining cleanup policies to manage snapshots. Setting a limit of five days removed artifacts on maintenance branches that are updated infrequently; setting a "last downloaded before 15 days" results in too much storage used by active branches.
-* daily: maven delete snapshot (task) - set to clean up snapshots after five days, while maintaining a minimum of 1 snapshot
+* hourly: clean up repositories (task) - run hourly to apply cleanup policies to our repositories
 * daily: publish maven indexer files (task) - used to publish an index used by build tools to synchronize thier understanding of the artifacts we publish
 * daily: delete incomplete docker uploads (task)
 Routing policies:

@@ Line 230: / Line 230: @@
 * releases - osgeo projects artifacts
 * docker - policy will be defined in conjunction with initial projects making use of this service
-* snapshots - subject to a policy removing artifacts after an appropriate time (currently five days)
+* snapshots - publish transit artifacts produced from the active development branches (See automation below for cleanup policies and tasks)
 * cache - isolated into separate storage so we have the option of avoid backups in the future
 Routing policies:

@@ Line 213: / Line 213: @@
 == Repositories ==
-Repository naming conventions:
+Maven repository naming conventions:
-* project releases (hosted) - each project manages its releases in a distinct hosted repository. They may wish to upload third party dependencies here also.
+* ''project''-releases (hosted) - each project manages its releases in a distinct hosted repository. They may wish to upload third party dependencies here also.
-* project snapshots (hosted) - each project with build automation manages its snapshots in a distinct hosted repository, subject to a policy expiring artifacts after an appropriate time
+* ''project''-snapshots (hosted) - each project with build automation manages its snapshots in a distinct hosted repository, subject to a policy expiring artifacts after an appropriate time
-* cache (proxy) - Upstream repositories can be cached at repo.osgeo.org to improve build times. Each external repository subject to routing policies to limit contents stored.
+* ''external''-cache (proxy) - external repositories can be cached at repo.osgeo.org to improve build times. Each external repository subject to routing policies to limit contents stored.
 * release (group) - Gathering all releases (from multiple project releases repositories, upstream cached repositories) providing a single repository for the community
 * snapshot (group) - Gather all snapshots from osgeo projects into a single repository for the community
 Nexus stores artifacts in blob storage (presently on the file system). We are defining different blob stores for different kinds of content: