Filter pipelines in Pipeline view by source
Release notes
The project pipelines list (CI/CD > Pipelines) shows all pipelines for a project without the ability to but to filter for pipelines by source. Now, users are ability to easily filler their pipelines in the Pipeline View.
Problem to solve
The project pipelines list (CI/CD > Pipelines) shows all pipelines for a project but users need the ability to filter for pipelines by source.
As a developer, I want to filter for pipelines initiated by a specific source so that I can view the pipelines that are relevant to the work I need to do.
Intended users
- Sasha (Software Developer)
- Devon (DevOps Engineer)
- Any user viewing project pipelines list that need to filter for specific pipelines
User experience goal
The user should be able to filter the pipelines list by Pipeline Source
.
Design specs can be found in the epic or here https://gitlab-org.gitlab.io/gitlab-design/hosted/dimitrie/ce18054-pipeline-filters-spec-previews/
Proposal
Enable filtering the project pipeline list on source
with these options (from ci_pipeline_source
):
- API
- External
- Git push
- Manual
- Schedule
for icons please use:
source
Enable filter pipelines by url query parameters, example:
https://gitlab.com/gitlab-org/gitlab/pipelines?page=2&scope=all&username=pburdette
Further details
This issue is a scoped down issue of #15268 (closed), which has been promoted to epic &3286 (closed).
Permissions and Security
Documentation
Update list of available filters on the View pipelines docs by adding the new pipeline filters added in this issue.
Availability & Testing
- What risks does this change pose to our availability? - No risk to our availability
- How might it affect the quality of the product? - This will increase the quality of our product, adding values to UX by providing meaningful filtered data.
- Will it require cross-browser testing? - Yes, please make sure all intended behaviors are the same cross-browser (i.e. Chrome, Firefox, IE, Safari ... etc.)
- What additional test coverage or changes to tests will be needed? - Please see below
Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance.
- Unit test changes - Yes
- Filter with
source
, ensure table updates correctly with correct pipelines by pipeline status - Filter with multiple filters (i.e. both source and tag)
- Removing filters will update table data
- Filter with
- Integration test changes
- Ensure query params are correct when making api call
- Ensure invalid/illegal inputs are being captured/handled appropriately
- End-to-end test change - not required
See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning