screwdriver
screwdriver copied to clipboard
move same repository pipeline easily
What happened: When I'm looking at the pipeline of a repository with multiple pipelines, I often want to go to the other pipelines in that repository. But in order to get there, I have to search again to get to the pipeline, and I find that a bit of a pain.
What you expected to happen: Able to move the same repository pipeline easily.
For example,
When you click 1, pull-down about other branches and source directory are shown. Users click the pull-down and go to the pipeline page.
Currently, when users click 1, the GitHub repository is shown. It is inconvenient cannot move Github repositories, so move the function to 2.
When users click 2, users can go to the GitHub repository.
How to reproduce it: Nothing.
I like this idea 👍 Definitely makes more sense to have function 2 as you described.
One question: Would it only show branches for repositories that have Screwdriver pipelines? Or would it show all branches in Github?
I think only show branches for repositories that have Screwdriver pipelines is better. If there are too many branches the tooltip will become hard to see.
I agree, sounds good.
I thought about a concrete display design that pipeline's screen transitions in the same repository and the development plan. YJ members ask for confirmation, and we can proceed with confidence if the VM members can also react.
Step1: Branch
The first thing to implement is something like this:
A small caret has been added next to the branch name, and clicking on this area will expand the drop-down list as shown below:
What is displayed here is the branch name of the same repository registered as pipeline. Select to move to the branch's pipeline screen.
The scm text part turns into a link. If you have selected the feature1 branch as shown in the image, it will be a link to the feature1 branch of SCM.
Step2: SourceDirectory
Allows Source Directory to transition from a pipeline of the same repository.
This mimics the search screen of the pipeline.
The SCM link in the pipeline where the Source Directory is set is also the link to the target directory.
This looks good. 👍