4 ms·
Thanks for forwarding my comment, it's much appreciated! I opened a ticket a while ago ago, I'll add this comment to the conversation. We're working on setting
by bram2w 4y ago
Thanks for forwarding my comment, it's much appreciated! I opened a ticket a while ago ago, I'll add this comment to the conversation. We're working on setting up our runners in the meantime.
- dnsmichi 4y agoThanks for opening the ticket already :-) I have talked with the fulfillment team at GitLab [0], and there was a problem identified with workers not syncing the purchased CI minutes after the DB migration. Corrections have been made, and potentially you should see the synced CI minutes soon. Support teams have access and can check with you, I do not have access. Setting up your own runners is a sensible approach, and allows you to scale them for your own needs too. Maybe this workshop about pipeline efficiency can help with more ideas and insights [1]. [0] https://about.gitlab.com/handbook/engineering/development/fulfillment/ https://about.gitlab.com/handbook/engineering/development/fu... [1] https://about.gitlab.com/handbook/marketing/community-relations/developer-evangelism/projects/#efficient-devsecops-pipelines-in-a-cloud-native-world https://about.gitlab.com/handbook/marketing/community-relati...
- bram2w 4y agoThank you for the update! We already have our workers working, it was super easy to set it up. I can confirm that the pipeline minutes have been added to my account.
- dnsmichi 4y agoWonderful, thanks for letting us know, appreciate your collaboration and patience in resolving the problem. :)