Handling broken master pipelines contribute
We currently run nightly pipelines for
building both CE and EE package in our Release mirror: https://dev.gitlab.org/gitlab/omnibus-gitlab
.
This mirror is configured to send pipeline failure notifications to
#g_distribution
channel on Slack. A broken master pipeline gets priority over
other scheduled work as per our development guidelines.
Jobs are stuck due to no runners being active
This is a transient error due to connection issues between runner manager
machine and dev.gitlab.org
.
-
Sign in to runner manager machine.
-
Run the following command to force a connection between runner and GitLab
sudo gitlab-runner verify
Docs
Edit this page to fix an error or add an improvement in a merge request.
Create an issue to suggest an improvement to this page.
Product
Create an issue if there's something you don't like about this feature.
Propose functionality by submitting a feature request.
Feature availability and product trials
View pricing to see all GitLab tiers and features, or to upgrade.
Try GitLab for free with access to all features for 30 days.
Get help
If you didn't find what you were looking for, search the docs.
If you want help with something specific and could use community support, post on the GitLab forum.
For problems setting up or using this feature (depending on your GitLab subscription).
Request support