Hook into Open Build Service (OBS) similar as you do with Travis CI?

[KurtPfeifle]

The owner of a GitHub repo can hook in additional external tools similar to hooking in Travis CI. For this project it would be beneficial to hook in openSUSE's Open Build Service (OBS). Go to the repo settings (here: https://github.com/AppImage/AppImageUpdate/settings), "Integration & services" to see what I mean.

OBS is listed as "Obs" in the drop-down list of available services when clicking the "Add service 'v'".

I cannot be of any help to actually set it up (or even to provide a pull request), because so far I failed to wrap my mind around the challenge to understand at all how OBS works and how to set it up.

But I guess you know all the beneficial features OBS can potentially provide:

1. Building not only .AppImage, but also RPM, DEB and other formats for lots of native distro package managers. This could be beneficial in order to increase visibility of the AppImage project and to remove some FUD which is spread by certain parties.

2. Building not only for x86_64, but also for i586, aarch64 and armvl7. The latter two are especially important in order to get AppImages built for ARM/Raspberry systems. (Currently there are only few ARM AppImages out there; these cannot be auto-updated, because tools like zsync2 and appimageupdatetool currently are not available for ARM.)

[probonopd]

The owner of a GitHub repo can hook in OBS, so that whenever the code in GitHub changes then OBS builds the software. I know this for sure because @adrianschroeter told me this.

For this to work, you need to get a token from your OBS project (OBS must somewhere have an option to generate a token...) and enter it into GitHub.

Then, whenever you do a git push to GitHub, it triggers OBS to do any builds of that project which you have configured on OBS (AppImage and/or other formats).

[probonopd]

Also see https://github.com/eliostvs/step-obs-service