Opened 5 weeks ago

Last modified 3 weeks ago

#32025 new project

Stop using corpsvn and disable it as a service

Reported by: arma Owned by: tor-gitadm
Priority: Medium Milestone:
Component: Internal Services/Service - git Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: #17202 Points:
Reviewer: Sponsor:

Description

In #17202 we're going to decommission the server that runs our various svn services.

We have a plan for the public svn.tpo service: #15948

and we are making a plan for svninternal: #15949

That leaves corpsvn, which I think is the most actively used still -- for example our accounting folks use it. This ticket is about making and finishing the plan for shutting down the corpsvn service.

Child Tickets

Change History (2)

comment:1 Changed 5 weeks ago by arma

On the plus side, I think we're much closer to being able to do this ticket now, since the main person who puts things into corpsvn these days is Sue, and I suspect she just commits things to have them somewhere for posterity, i.e. she isn't using any of the actual revision control features.

So if we froze the corpsvn repo and gave her new instructions on where to send new things (probably Nextcloud), I bet we'd have a good start here.

She would still need to reference a checkout of corpsvn e.g. for giving documents to the auditors, but she probably has one on her laptop, so maybe "being available to help her if that checkout breaks" is a win over "need to keep corpsvn going as a service".

There might be other folks who still use their copy of corpsvn in a read-only kind of way. Maybe that's Erin. Or more? We need to ask the operations team.

Then we would have a next task which is "triage and sort the current corpsvn files, probably by category, and do something smart with them" but in theory that step can be orthogonal to shutting down the corpsvn service.

comment:2 Changed 3 weeks ago by anarcat

Then we would have a next task which is "triage and sort the current corpsvn files, probably by category, and do something smart with them" but in theory that step can be orthogonal to shutting down the corpsvn service.

I've opened #32272 just for that, which is (unexpectedly for me) also a problem with svn-internal.

So we can treat this ticket as just the "shutdown SVN corp" task. Worst case, we just move everything over to Nextcloud when it's ready (#32267).

Note: See TracTickets for help on using tickets.