Define the root cause of why a job is stuck if it has to do with a runner
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Release notes
When a job is stuck, we provide you with an alert with a few reasonings of why the job may be stuck. Now, we give you the root cause so you can fix it quicker and spend last time debugging.
Problem to solve
Developers are spending time debugging when a job is stuck because of a runner. We provide them with many reasons why it may be stuck, so they end up still having to debug to figure out the root cause. Related internal convo: https://gitlab.slack.com/archives/C01RQ3AQH3R/p1674846526124809.
Intended users
User experience goal
The user should be given the root cause so they can fix it easily.
Proposal
We could start with the wrong tag scenario first. We should see if the job tags match runner tags, and if it doesn't, update the alert to say there are no matching runners with those tags.
windows-shared but the tag is actually windows-shared-1.
Further details
Permissions and Security
Documentation
Availability & Testing
Available Tier
Feature Usage Metrics
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
What is the competitive advantage or differentiation for this feature?
Links / references
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.