OBS Workflows, At Your Service!

by the OBS Team posted on 4th Apr 2022

After receiving feedback from users of OBS workflows in the SCM/CI integration, we are now introducing a step to trigger services of a package. Do not forget to join the beta program before trying this out.

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.

Trigger Services of a Package

With the trigger_services step, it’s now possible to trigger services of a package in a OBS workflow. Be sure to have a _service file in your package if you use this step.

Here’s how to define a trigger_services step:

workflow:
  steps:
    - trigger_services:
        project: home:Admin
        package: ctris

As an example, this could be used in combination with filters to only trigger services of the package home:Admin/ctris when a commit is pushed to the target branch main:

workflow:
  steps:
    - trigger_services:
        project: home:Admin
        package: ctris
  filters:
    event: push
    branches:
      only:
        - main

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.