[tor-bugs] #30857 [Internal Services/Services Admin Team]: migrate (some projects? everything?) from trac to gitlab
Tor Bug Tracker & Wiki
blackhole at torproject.org
Mon Jun 24 15:49:39 UTC 2019
#30857: migrate (some projects? everything?) from trac to gitlab
-------------------------------------------------+-------------------------
Reporter: anarcat | Owner: (none)
Type: project | Status: new
Priority: Medium | Milestone:
Component: Internal Services/Services Admin | Version:
Team |
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: #29400 | Points:
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by anarcat):
> If I remember correctly, we can't move tickets between projects in
gitlab. I've added it to the list as something to check.
I think that was solved recently:
https://about.gitlab.com/2016/04/20/feature-highlight-move-issues/
> I checked the GitLab integrations, Jenkins works, but Travis and
Appveyor don't. So we need to keep mirroring git to GitHub for Travis and
Appveyor.
Yeah, I don't know if we're talkinga bout getting rid of GitHub here yet.
One thing at a time. GitLab CI, however, might allow us to replace Travis
eventually...
> I also wonder how many GitLab CI runner machines we will have, and who
will pay for them.
... however this is also out of scope for now. We're talking abuot
(possibly) replacing Trac, not Trac '''and''' Jenkins all at once. One
thing at a time. :)
(That said, if we do eventually replace jenkins with Gitlab CI, the
builders we have now can just be repurposed for GitLab CI. It's all
hardware in the end.)
So, TL;DR: no runers yet, as far as I know, but if people want to
provision external ones, the sweet thing is this can be done without
intervention from TPA or GitLab admins...
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30857#comment:34>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list