Change the empty state for pipeline widget when no pipeline exists and Jenkins is detected
Release notes
Problem to solve
The current empty state for the pipeline widget when no pipeline exists is bulky and dismissible(probably at project or group level) and doesn't show up for a new MR. MR is a great touchpoint to suggest CI adoption or even migration to SCM users at GitLab.
Intended users
User experience goal
Users should be presented with a choice to use GitLab CI at a location where it would make the most difference to them. using GL CI would bring in high visibility into pipelines in an MR.
Proposal
Rework the empty state for pipeline widget to make it less intrusive and yet provide a quick path to getting started with GitLab CI. This message can even be contextual for users using external CI offering to help them with migration steps.
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.