GitLab.com CI minutes and fork workflows
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
I came across a customer issue today that blows a hole wide open in our CI plans, unless I'm missing something.
We have two users, Alice and Bob, both with subscriptions that include some minutes.
They are members of a group, let's call it FooGroup.
The project makes use of CI tools to run tests through commit hooks.
The structure of the project is FooGroup is the main line repository. Alice and Bob each work in their own repository and periodically submit merge requests to FooGroup.
Whenever Alice or Bob commits to their repository, I expect their minutes to be used.
When a merge request happens, whose minutes are used? Does the group need to have its own minutes?
If Alice & Bob are pushing to their own branches, I assume CI will also happen on those branches, but within their namespaces rather than the parent? Obviously, the MR build will happen on the canonical repo.
However, Alice & Bob are really working within the context of the group, rather than their own personal accounts.
What is the best way to solve this? Could we use the fork network and effectively consume the canonical repository's minutes? Is there another solution?
For a bit of background context, also see this: https://gitlab.com/gitlab-com/www-gitlab-com/issues/1678
@DouweM @markpundsack @ayufan @bikebilly @JobV
cc @lbot