-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add ability to set "displayName" for Pipeline tasks #3466
Comments
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
:( |
/remove-lifecycle stale This seems like a fairly straightforward FR, possibly even a [good first issue]. I think a TEP is a good next step, to get feedback and input from the community, particularly in the CLI and Dashboard areas. If you're interested in drafting a brief TEP I can help shepherd this through the process. 👍 |
ill need a a definition of TEP, but happy to help push it along |
The TEP (Tekton Enhancement Proposal) process is described here: https://github.com/tektoncd/community/blob/master/teps/0001-tekton-enhancement-proposal-process.md Basically, write up a short Markdown document using the template, send a PR to tektoncd/community, people will discuss and (🤞) approve, then we can implement. Since the proposal is small, just adding a field, I suspect discussion will be light, but it helps get visibility from other teams before making changes that might affect them. |
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
@imjasonh the TEP got merged, should this stay alive for the actual implementation or allowed to die? |
/lifecycle frozen Let's keep it open. |
TEP-0047: Pipeline Task Display Name is implementable - we welcome contributions in implementing it |
/assign |
Thank you @nanjingfm for implementing this feature! Could you please update the status of TEP-0047, and add a link to the implementation PR? 🙏🏾 |
Here is the pr marking |
is this supported by the dashboard? |
Yes, this is supported by the dashboard! |
Feature request
Currently when a pipeline is rendered in the UI the
Pipeline.tasks.*.name
is used in the UI. The problem is that field has character requirments on it designed for a machine so it can be used for other params likerunAfter
. This means that the pipelines are not very human readable in the UI.Use case
For instance when converting a pipeline from Jenkins to Tekton. had a Jenkins stage named
CI: Static Image Scan: Compliance
in tekton i have to name the taskci-static-image-scan-compliance
and that is what gets rendered in the UI for end users rather then something nice a pretty like in jenkins.Solution
Need a new filed, such as
Pipeline.tasks.*.displayName
which is optional and allows a human readable text that gets rendered in the UI if supplied instead ofPipeline.tasks.*.name
.The text was updated successfully, but these errors were encountered: