Gitea Joins the SCM/CI Party!

As we disclosed a few days ago, the roll-out of the SCM/CI feature was not the end. The proof is that we are here to announce another important milestone regarding the OBS SCM/CI integration. Starting today, Gitea is available for you to be integrated with OBS!

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. And now, we bring notifications for failed workflow runs.

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

Gitea and OBS logos
Gitea and Open Build Service Integration

It was our idea from the beginning to make this feature SCM-agnostic because there are so many of them we would like to support. In a similar way you did with GitHub or GitLab before, you can run different workflows in OBS when some relevant events happen on the Gitea side. For instance, a newly created pull request in Gitea can trigger the building of the corresponding packages in OBS or some changes pushed to a branch can end up re-building a package in our instance.

All you need to know is available in our user documentation. Enjoy setting up the integration with Gitea and please let the feedback coming.

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.