Currently(before v3.3.0), all Pipeline step UI components belong to .jsx source file. So, it's not easy to add a new Pipeline step UI component if a contributor is not familiar with the relevant information.
A second big problem with the current pattern is that some steps (or commands) might be difficult for some newcomers. In some cases, some steps need a nested step. For example:
In response to [this](https://github.com/kubesphere/ks-devops/issues/602#issuecomment-1506694397):
>/close
>
Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
Background
Currently(before v3.3.0), all Pipeline step UI components belong to
.jsx
source file. So, it's not easy to add a new Pipeline step UI component if a contributor is not familiar with the relevant information.A second big problem with the current pattern is that some steps (or commands) might be difficult for some newcomers. In some cases, some steps need a nested step. For example:
or
Proposal
Design a CRD that represents a Pipeline step. Provide an API that can list all the steps CR. Then the front-end could list all the cutomized steps.
Actions
Firstly, we can provide some common steps. For example:
Examples
Send message to Feishu
References