Move Quarry from Gerrit to GitHub
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	• rook
	May 22 2022, 2:42 PM

Description

Quarry is currently hosted on Gerrit. Let's move it to GitHub.

Details

Related Changes in Gerrit:

Subject	Repo	Branch	Lines +/-
jjb: Drop jobs for analytics/quarry/web, no longer used	integration/config	master	+0 -8
Zuul: Mark analytics/quarry/web as archived	integration/config	master	+5 -8
Set repo to readonly	analytics/quarry/web	master	+1 -26 K

Customize query in gerrit

Related Objects
Search...

Status	Assigned	Task
Resolved	• rook	T308978 Move Quarry from Gerrit to GitHub
Resolved	• rook	T317092 test tox on PR
Resolved	• rook	T316961 test irc integration
Resolved	• rook	T316958 build container on PR

Event Timeline

• rook created this task.May 22 2022, 2:42 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMay 22 2022, 2:42 PM

• rook merged a task: T308977: change default branch name to main.May 22 2022, 2:43 PM

• rook added a subscriber: RhinosF1.

RhinosF1 added a project: GitLab (Project Migration).May 22 2022, 2:45 PM

Update links on https://meta.wikimedia.org/w/index.php?title=Research:Quarry etc once this has happened.

Seems like waiting on this until some of the CI bits of gitlab are better established is recommended.

<dancy> Ahmon Dancy 
Rook:  Sorry for the delay. We're still working on codifying best practices for converting from Jenkins to Gitlab.  There are a couple of blockers that are getting in the way.   
<Rook> Vivian Rook 
Np. Would you recommend I delay in moving quarry? It isn't currently blocking anything by remaining in at the moment 
<dancy> Ahmon Dancy 
Yeah, I recommend waiting.

zhuyifei1999 subscribed.Jun 28 2022, 4:03 AM

• rook renamed this task from Move quarry to gitlab to Move quarry to gitlab or github.Sep 6 2022, 9:06 PM

• rook added subtasks: T317092: test tox on PR, T316961: test irc integration, T316958: build container on PR.

I believe that random third-party hosting locations like GitHub should be off the table.
In my understanding, everything should be on Wikimedia GitLab in the long run, instead of Wikimedia Gerrit, Wikimedia Diffusion, GitHub, Sourceforge, wiki pages, etc.

(In any case, please disable "Issues" on https://github.com/toolforge/quarry to avoid fragmentation and duplication - thanks.)

Issues disabled.

everything should be on Wikimedia GitLab in the long run

I generally agree. As I mentioned in the email once gitlab has necessary features enabled quarry can move there.

As mentioned above github appears to serve the project requirements where gitlab is not quite ready. I don't believe I mentioned it here but one of the main problems is the lack of being able to run or build docker inside of a gitlab runner. A tool like Kaniko is a possibility for being able to build a container, however at this time its registry is not allowed to be pulled from by gitlab runners.

Going to github at this point does not prevent moving to gitlab in the future. The primary blocker is the ability to build a container. This prevents quarry from having functional ci. This would likely be resolved by T307536 The other, known, blockers are not show stoppers include a lack of irc integration (T288381) phabricator integration (T265617), being able to run a container (T307536)