As discussed on -devel, the rough cut plan is:
I'd recommend gitlab.com/CentOS/Archive/git.centos.org and maintaining the full hierarchy underneath it. This also has the advantage of making it trivial to put a URL rewrite path to redirect.
gitlab.com/CentOS/Archive/git.centos.org
Metadata Update from @arrfab: - Issue tagged with: authentication, centos-build-pipeline, centos-ci-infra, centos-common-infra, centos-stream, dc-move, dev, doc, feature-request, gitlab, high-gain, high-trouble, investigation, mini-initiative
Metadata Update from @arrfab: - Issue assigned to arrfab
@dcavalca : as discussed on dedicated Matrix room for this migration, I created a private repo so that the CentOS Board can see how it would look like for imported tickets. Migration seems to work for tickets (for repositories/projects themselves I think we can just use a simple wrapper to just create/git add remote/ git push /etc).
Let me know how that works or if you have other remarks
Due to centos infra tracker migration (https://lists.centos.org/hyperkitty/list/devel@lists.centos.org/thread/V3ZLBYFHMWSZFXOVGVU7R6P2X6ELGY5V/), this ticket is now closed but you can find corresponding ticket open at https://gitlab.com/CentOS/infra/tracker/-/issues/1654 Metadata for this ticket is imported in new gitlab tracker but not ownership, so feel free to visit migrated ticket to subscribe and get status update.
Metadata Update from @arrfab: - Issue close_status updated to: Ticket moved to Gitlab tracker - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.