Filter SCM Events by multiple properties

by the OBS Team posted on 18th Apr 2024

Every time your source code management system (github, gitlab etc.) sends a webhook to OBS to trigger a SCM/CI Workflow, we give our best to record what is happening during (and in case of builds even after) your workflow’s steps run. We do this because this is a complicated feature, involving two very large applications, where lot’s of things can go wrong. So you need loads of information to debug once something is.

We do this by recording things in a “log file” called workflow run. You can access them from the /my/tokens. We have just published a new search/filter interface for workflow runs.

We started off the continuous integration between OBS and GitHub/GitLab in May 2021, then made some improvements in June 2021. We introduced advanced features like reporting filters and support for self-hosted SCM together with a list of common pitfalls in July 2021 and in August 2021, we continued with two new steps and a UI for tokens. In September 2021, we supported more actions for pull/merge requests, improved the UI for tokens, and added support for push events and a rebuild step. In November 2021, we presented the user documentation and further improvements for the UI for tokens and workflow runs and more. We worked on UI and reporting improvements in February 2022, followed by a step to trigger services and the improvement of the error messages in April 2022. Afterwards, we clarified the separation between incoming webhooks and status reports in May 2022, then sharing tokens was made possible in June 2022. Later in July 2022, we added support for the SCM Bridge feature. Around September 2022, the feature was considered stable, so we enabled it for all the OBS users, but that wasn’t the end; later in September we reached the milestone of supporting Gitea on top of GitHub and GitLab. In December 2022 we introduced placeholder variables in addition to a customizable configuration file location. Later on we brought notifications for failed workflow runs, and now we introduced a new way of listing the events by multiple filter parameters

This feature is documented in the SCM/CI Workflow Integration chapter of the OBS User Guide.

Apply Multiple Filters to the List of SCM Workflow Runs

It is now possible to use more fine-grained filters for listing your SCM/CI Workflows runs. You can filter by event status, type, action and source and combine them any way you want.

Screenshot of workflow run multiple filters

If your SCM/CI Workflow is branching a package, the project the package is branched to, now contains a link back the the PR/commit that caused this workflow to run.

How To Give Us Feedback

There are two ways to reach us:

Please note that we favor GitHub to gather feedback as it allows us to easily keep track of the discussions.