You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The project that I work on has created a fair amount of pipeline templates using Carvel's ytt in order to assign consistency to pipelines but also quickly spin up new pipelines in an easy way. Currently the way we identify these pipeline types across teams is having a suffix of {project}-container-pipeline or {project}-microservice-pipeline. Understandably these pipeline names can get a bit wordy if the prefix name is lengthy in itself.
Potential Solution
Proposing adding the concept of labels to pipelines to be searched against and display within the UI similar to how issues / pull requests work in GitHub. A new section could be created called pipeline_config which contains the already existing background_image property and a new labels property that would be an array of potential labels.
Potential Problems
The one potential problem I could see if the display of these labels. With one to two labels, this issue probably doesn't exist, but if Pipeline Engineers add 5, 10, or more labels, the display would become a problem.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Problem
The project that I work on has created a fair amount of pipeline templates using Carvel's ytt in order to assign consistency to pipelines but also quickly spin up new pipelines in an easy way. Currently the way we identify these pipeline types across teams is having a suffix of
{project}-container-pipelineor{project}-microservice-pipeline. Understandably these pipeline names can get a bit wordy if the prefix name is lengthy in itself.Potential Solution
Proposing adding the concept of labels to pipelines to be searched against and display within the UI similar to how issues / pull requests work in GitHub. A new section could be created called
pipeline_configwhich contains the already existingbackground_imageproperty and a newlabelsproperty that would be an array of potential labels.Potential Problems
The one potential problem I could see if the display of these labels. With one to two labels, this issue probably doesn't exist, but if Pipeline Engineers add 5, 10, or more labels, the display would become a problem.
Beta Was this translation helpful? Give feedback.
All reactions