Search before asking
Use case
As a user of Apache Devlake I want the ability to only show deployment pipelines from Jenkins that I actually care about and that are relevant to me and my organisation.
Description
The current Jenkins collector appears to fetch all pipelines - even if they are temporary branch/PR builds. Devlake should have the option to filter the collection results (or only collect certain results based on a regex). As an example there is a Jenkins collector configured in this project where only the following data scopes are selected:
However when viewing/searching for the project in Grafana it shows on the available dropdown of a bunch of random PR branches that are not selected.
I assume this has an additional underlying impact about redundant pipelines/scopes
Related issues
No response
Are you willing to submit a PR?
Code of Conduct
Search before asking
Use case
As a user of Apache Devlake I want the ability to only show deployment pipelines from Jenkins that I actually care about and that are relevant to me and my organisation.
Description
The current Jenkins collector appears to fetch all pipelines - even if they are temporary branch/PR builds. Devlake should have the option to filter the collection results (or only collect certain results based on a regex). As an example there is a Jenkins collector configured in this project where only the following data scopes are selected:
However when viewing/searching for the project in Grafana it shows on the available dropdown of a bunch of random PR branches that are not selected.
I assume this has an additional underlying impact about redundant pipelines/scopes
Related issues
No response
Are you willing to submit a PR?
Code of Conduct