Show pipeline iid in pipelines page
Release notes
You may want to connect your GitLab Pipelines to a file version or build number and were limited by the Pipeline ID exceeding a 16-bit integer requirement. Now, we have enabled the Pipeline IID to be exposed in the pipeline view to easily enable you to effortlessly support a Windows versioning schema.
Problem to solve
Users want to embed the build-number in Windows resource files, specifically the “file version” field which can take only 16 bits integers. In most cases ID has exceeded 16bit and thus break’s the windows versioning schema. Exposing IID as an identifier could solve this problem.
IID was added in [11.0] and is useful for things like semver, but not exposed anywhere in the UI. We're considering chaning the routing of pipelines to match IID which would be valuable, but maybe a breaking change for some use cases. Before doing that, we could add IID to the user interface elsewhere (for instance the pipelines page).
Target audience
- Delaney, Development Team Lead, https://design.gitlab.com/research/personas#persona-delaney
- Sasha, Software Developer, https://design.gitlab.com/research/personas#persona-sasha
- Devon, DevOps Engineer, https://design.gitlab.com/research/personas#persona-devon
Further details
This will help make CI more lovable, per our "Lovable" north star.
Design Proposal
Surface the IID on the pipeline index page to improve discoverability of pipelines.
What does success look like, and how can we measure that?
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.