OBS Workflows, At Your Service!
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.
Trigger Services of a Package
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
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
when a commit is pushed to the target branch
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:
- On GitHub, by opening an issue and / or commenting on an already opened issue.
- On IRC, by talking directly to us. We are in the channel
Please note that we favor GitHub to gather feedback as it allows us to easily keep track of the discussions.