Java projects hosted on Gerrit should publish artifacts to Gitlab
Closed, DuplicatePublic
Actions

Assigned To

None

Authored By

	Gehel
	Jul 18 2024, 9:49 AM

Description

We have a number of Java projects hosted on Gerrrit that we don't want to migrate to Gitlab (at least not yet). It should be reasonably easy to modify the current CI jobs to publish to a Gitlab hosted package registry instead of Archiva.

Key points

Current jobs are defined in https://gerrit.wikimedia.org/r/plugins/gitiles/integration/config/+/refs/heads/master/jjb/job-templates.yaml
Gitlab does not seem to provide a global package registry, we might need to create a project dedicated to hosting artifacts that are not gitlab projects
We need an API token created in Gitlab with proper authorization and exposed in our Jenkins CI

AC

Java projects hosted on Gerrit have a CI job that published to a Gitlab package registry

Related Objects
Search...

Status	Assigned	Task
Open	None	T367315 [Epic] Replace Archiva with Gitlab artifact repositories
Open	None	T368927 [Epic] Migrate Data Platform Engineering maintained git repos to GitLab
Open	None	T367405 Migrate existing Java packages to deploying to Gitlab, including new version of parent pom, validation that all dependencies are available, and validation that deployment to production still works
Duplicate	None	T370400 Java projects hosted on Gerrit should publish artifacts to Gitlab

Event Timeline

Gehel created this task.Jul 18 2024, 9:49 AM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJul 18 2024, 9:49 AM

@brennen : Do you have an opinion on where to host artifacts coming from projects hosted on Gerrit? Does it make sense to create a project on Gitlab that would be dedicated to hosting artifacts generated outside of Gitlab?

Gehel added a project: Release-Engineering-Team.Jul 18 2024, 9:51 AM

@Gehel, would it be easier if projects are hosted in GitLab? We are planning on migrating the DE maintained ones. Perhaps then the CI artifact publishing would not be implemented twice (once for jenkins, and then again later for GitLab CI)?

In T370400#9995143, @Ottomata wrote:

@Gehel, would it be easier if projects are hosted in GitLab? We are planning on migrating the DE maintained ones. Perhaps then the CI artifact publishing would not be implemented twice (once for jenkins, and then again later for GitLab CI)?

At least the Search Platform team has no intentions of migrating to Gitlab. Gerrit workflow works much better for us. So while it would be easier to have all projects in Gitlab in terms of publication of artifacts, it comes with a fairly high cost in terms usability. It shouldn't be too hard to publish from Gerrit to Gitlab, so let's at least check how feasible it is.

Gehel triaged this task as Medium priority.Jul 22 2024, 1:45 PM

👍

Do you have an opinion on where to host artifacts coming from projects hosted on Gerrit? Does it make sense to create a project on Gitlab that would be dedicated to hosting artifacts generated outside of Gitlab?

No strong opinion about location. It might be good to settle the question of whether packages should all get dropped into a single project (T367322#9987048) in general.

thcipriani edited projects, added Release-Engineering-Team (Radar); removed Release-Engineering-Team.Jul 31 2024, 4:44 PM

Gehel removed a project: Discovery-Search.Aug 12 2024, 3:39 PM

Gehel edited parent tasks, added: T367405: Migrate existing Java packages to deploying to Gitlab, including new version of parent pom, validation that all dependencies are available, and validation that deployment to production still works; removed: T367315: [Epic] Replace Archiva with Gitlab artifact repositories.Sep 25 2024, 8:01 AM

Gehel closed this task as a duplicate of T367405: Migrate existing Java packages to deploying to Gitlab, including new version of parent pom, validation that all dependencies are available, and validation that deployment to production still works.