Migrate Data Engineering NodeJS library repos to GitLab
Closed, ResolvedPublic8 Estimated Story Points
Actions

Assigned To

Authored By

	Ottomata
	Jun 4 2024, 3:24 PM

Description

To do for each:

Move repo to GitLab
Delete or archive original repo. If archived, add link in README to new home in GitLab.
Use GitLab CI to run tests
Update any relevant documentation in code or on wikitech.

Libraries

These are packages that are depended on by other repositories / services.

jsonschema-tools (GitHub 🐱)
- Convert this PR to a GitLab MR.
node-rdkafka-factory (Last update: 2022-05-05T15:14:55-07:00)
eventgate (GitHub 🐱)

To Remove

node-rdkafka-statsd (Last update: 2022-05-05T15:10:05-07:00)
- To do this, we will need to remove node-rdkafka-statsd related code from eventgate, eventgate-wikimedia, and eventstreams. This should be easy enough, as code should not be used anymore.

Since these are mostly libraries, we should also update the downstream dependers to use them from new locations.

That will be done in:

Details

Related Changes in Gerrit:

	Subject	Repo	Branch	Lines +/-
	Edit Readme to notify users of move to Gitlab	node-rdkafka-factory	master	+1 -34

Customize query in gerrit

Related Changes in GitLab:

Title	Reference	Author	Source Branch	Dest Branch
Remove node-rdkafka-statsd related code from Eventgate repository.	repos/data-engineering/eventgate!2	ebysans	remove_node_rdkafka_statsd	master
Remove node-rdkafka-statsd related code from Eventgate-wikimedia repository	repos/data-engineering/eventgate-wikimedia!3	ebysans	remove_node_rdkafka_statsd	master
Remove node-rdkafka-statsd related code from Eventstrams repository	repos/data-engineering/eventstreams!12	ebysans	remove_node_rdkafka_statsd	master
Setup Gitlab CI for Node-rdkafka-factory	repos/data-engineering/node-rdkafka-factory!2	ebysans	gitlab_ci_test	master
Add Gitlab CI test pipeline	repos/data-engineering/jsonschema-tools!52	ebysans	Gitlab_migration	master

Customize query in GitLab

Related Objects
Search...

Status	Assigned	Task
Open	None	T368927 [Epic] Migrate Data Platform Engineering maintained git repos to GitLab
Open	None	T384364 Create an instance-level npm package registry in Gitlab
Open	None	T366614 [Epic] Migrate Data Engineering maintained NodeJS repositories to GitLab
Resolved	Snwachukwu	T366611 Migrate Data Engineering NodeJS library repos to GitLab
Resolved	tchin	T366537 Create gitlab ci npm publish pipeline and job in workflow_utils gitlab_ci_templates
Resolved	tchin	T366612 Publish Data Engineering maintained NodeJS packages to GitLab and use them in depender code
Resolved	Ottomata	T383814 Upgrade eventgate-wikimedia to node20

Event Timeline

Ottomata created this task.Jun 4 2024, 3:24 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJun 4 2024, 3:24 PM

Ottomata mentioned this in T344730: Migrate Data Engineering Pipelinelib repos to GitLab.Jun 4 2024, 3:25 PM

Ottomata updated the task description. (Show Details)Jun 4 2024, 3:28 PM

Ottomata updated the task description. (Show Details)Jun 4 2024, 3:32 PM

Ottomata renamed this task from Migrate Data Engineering NodeJS repos to GitLab to Migrate Data Engineering NodeJS library repos to GitLab.Jun 4 2024, 3:38 PM

Ottomata assigned this task to Snwachukwu.

Ottomata added a parent task: T366614: [Epic] Migrate Data Engineering maintained NodeJS repositories to GitLab.

Ottomata added a subtask: T366537: Create gitlab ci npm publish pipeline and job in workflow_utils gitlab_ci_templates.

Ottomata updated the task description. (Show Details)Jun 4 2024, 3:41 PM

Ottomata updated the task description. (Show Details)Jun 5 2024, 12:02 AM

Ottomata updated the task description. (Show Details)Jun 6 2024, 6:37 PM

Ottomata set the point value for this task to 8.Jun 6 2024, 6:40 PM

Note: I have moved the event schema repo GitLab migration to its own task: T366836: Migrate Event Platform Schema Respositories to Gitlab

@Ottomata can we close this PR in jsonschema-tools before migrating to gitlab?

Good q! @tchin asked the same thing. @tchin if you have time to review and merge the PR, let's go for it. If you think there should be more back and forth dev on it, then let's close the PR and re-open as a GitLab MR after the repo is migrated.