Page MenuHomePhabricator

[Epic] Migrate Data Platform Engineering maintained git repos to GitLab
Open, Needs TriagePublic

Description

This is an epic parent task. Actual work will be done in subtasks.

Java repos

Deployment of these repo's jar artifacts to GitLab is tracked in 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. Ideally we could migrate these to GitLab before work is done in that ticket to make Jenkins deploy to GitLab. That way the work to deploy via CI only has to be done once in Gitlab CI.

Other repos

Note: scap & 'deploy' repos are listed here, but we may not need to migrate them if we change our deployment process. See T322690: Add support for repository artifacts in Airflow

Other work

Related Objects

StatusSubtypeAssignedTask
OpenNone
OpenNone
ResolvedSnwachukwu
ResolvedSnwachukwu
Resolvedtchin
Resolvedtchin
ResolvedOttomata
ResolvedSnwachukwu
Openpfischer
DuplicateNone
ResolvedEBernhardson
Duplicateamastilovic
Resolvedpfischer
OpenNone
Openamastilovic
Resolvednshahquinn-wmf

Event Timeline

Ottomata renamed this task from [Epic] Migrate Data Engineering maintained git repos to GitLab to [Epic] Migrate Data Platform Engineering maintained git repos to GitLab.Jul 1 2024, 3:46 PM
Ottomata updated the task description. (Show Details)
Ottomata updated the task description. (Show Details)
Ottomata added a project: Data-Platform-SRE.
Ottomata added subscribers: Gehel, BTullis, brouberol.

@Ahoelzl here's my first attempt at pulling this together.

Note that most of the work is around migrating Java lib repos to GitLab. These are tracked in T367315: [Epic] Replace Archiva with Gitlab artifact repositories and are dependent on Data-Platform-SRE work being done for T367315: [Epic] Replace Archiva with Gitlab artifact repositories.

We should coordinate with DPE-SRE before embarking and/or committing to this work.

Note that most of the work is around migrating Java lib repos to GitLab. These are tracked in T367315: [Epic] Replace Archiva with Gitlab artifact repositories and are dependent on Data-Platform-SRE work being done for T367315: [Epic] Replace Archiva with Gitlab artifact repositories.

We should coordinate with DPE-SRE before embarking and/or committing to this work.

I think that those 2 tickets are mostly orthogonal. T367315 is about the publication of artifacts not about where the code is hosted.

Yes sorry, phab ticket # copy/paste fail. I meant to link 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.

Just checking, did I interpret T367405 wrong then? Is that only about the deployment stuff, and not about migration of repos and CI to gitlab? If so then I'll update and make tickets for that work.

Just checking, did I interpret T367405 wrong then? Is that only about the deployment stuff, and not about migration of repos and CI to gitlab? If so then I'll update and make tickets for that work.

The Archiva to Gitlab migration is purely about deployment, not about code hosting. We should still be able to have code hosted on Gerrit, built in Jenkins and artifacts published to Gitlab. Obviously, if everything is hosted on Gitlab, it makes things slightly easier, but not all that much (I think it would actually be easier if everything was hosted on Gerrit :) )

Removing Data Platform SRE, code management isn't our area of concern. Ping us if you need help, but you should be able to move forward without us.

Got it, thanks @Gehel. I'll update this task to incorporate GitLab code hosting of Java projects directly.