We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi team, I'm currently POC of using this tool to track Gitlab CI Pipelines in my company.
Currently my config looks like this:
gitlab: url: https://gitlab.mycompany.com/ enable_health_check: true health_url: https://gitlab.mycompany.com/-/health enable_tls_verify: false token: "" server: webhook: enabled: true secret_token: "" pull: projects_from_wildcards: on_init: false scheduled: false environments_from_projects: on_init: false scheduled: false refs_from_projects: on_init: false scheduled: false metrics: on_init: false scheduled: false projects: - path/to/project1 - path/to/project2
With this configuration, it can retrieved the pipeline on master/main branch but it's not whenever there is pipeline running on an MR.
We want to leverage webhook as much as possible to avoid too many requests to our gitlab instance.
It seems these issues are related: #889 and #280, but I'm still confused on what could be the most ideal setup for my use case.
Hence, creating a new issue here for easy tracking in case there is someone else having the same requirement.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi team, I'm currently POC of using this tool to track Gitlab CI Pipelines in my company.
Currently my config looks like this:
With this configuration, it can retrieved the pipeline on master/main branch but it's not whenever there is pipeline running on an MR.
We want to leverage webhook as much as possible to avoid too many requests to our gitlab instance.
It seems these issues are related: #889 and #280, but I'm still confused on what could be the most ideal setup for my use case.
Hence, creating a new issue here for easy tracking in case there is someone else having the same requirement.
The text was updated successfully, but these errors were encountered: