-
Notifications
You must be signed in to change notification settings - Fork 265
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
Web panelling for 'manually create a pipelinerun' #108
Comments
/assign |
@mnuttall @AlanGreene Also, what is the flow for how the user should access this page to create a PipelineRun? (what link does the user click to get them to this page, and what page is this link on?) My paneling could probably be linked to from the main menu. Or, if the user is on a Pipeline's page, should I add a button to create a PipelineRun for that Pipeline? |
Update: I just talked with Mark about the namespace selection, and we agreed to use the "global" namespace that was recently introduced. |
Here are a couple of approaches to how the user should access the Create PipelineRun page. Option 1: from the side menuIn this approach, there is always a button in the side menu that will bring the user to the Create PipelineRun page. Maybe we could make another category called Option 2: button in the PipelineRun listIn this approach, the Pipeline option on the Create PipelineRun page would be pre-populated with the Pipeline ref. So, in this example it would be pre-populated with Example barebones Create PipelineRun page:@mnuttall @AlanGreene which option do you think is best for navigating to the Create PipelineRun page? Is there another approach that you have in mind? Should I do both option 1 and 2? |
Personally I'd prioritise option 2, and also consider adding it to the Pipeline list as described in #38 For option 1 I'm concerned the nav could get a bit busy with all the create options added (Pipeline, PipelineRun, Resource, Credential, etc.). We should definitely have something easily accessible that doesn't require navigating through multiple layers of the application, so let's try option 2 first and see if we feel we need more. |
Ok, thanks for the feedback Alan. I'll put a button in the PipelineRun list. |
PR #295 completes this issue |
@ncskier: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
We have a REST API that supports the manual creation of pipelineruns.
The parameters that a user must provide will be specific to the pipeline they're creating a run for - luckily they're all defined in the pipeline.
The UI will need to obtain and parse the desired pipeline before populating the fields that need user entry.
The text was updated successfully, but these errors were encountered: