Update jsonnet-tool to release to multiple GitLab instances
Problem
jsonnet-tool is used to generate yml
from jsonnet and is a tool that is used internally. We need to start depending on this tool for tool that runs on https://ops.gitlab.net/ which is a GitLab instance used to manage GitLab.com. We can use the container registry of GitLab.com to pull docker images for jobs that run on ops.gitlab.net since we need ops.gitlab.net to work even when GitLab.com is down as discussed in https://ops.gitlab.net/gitlab-com/gitlab-com-infrastructure/-/merge_requests/2896#note_112165
Proposal
-
Set up mirroring to https://ops.gitlab.net/ 👉 https://ops.gitlab.net/gitlab-com/gl-infra/jsonnet-tool/ -
Get the pipeline to publish the version on https://ops.gitlab.net/ -
Update goreleaser
so it supports multiple git instances-
Upstream fix to support templates for URLs 👉 https://github.com/goreleaser/goreleaser/pull/2465 -
Update .goreleaser
yml file to use environment variables👉 jsonnet-tool!21 (merged)
-
-
Update semantic-release
not to have GitLab.com hardcoded👉 jsonnet-tool!21 (merged) -
Fix projectID discovery 👉 jsonnet-tool!22 (merged) -
Fix artifact upload 👉 jsonnet-tool!23 (merged)
-
Edited by Steve Xuereb