once the builds are up and running it is ‘just’ a matter of keeping the packages up-to-date.
The openSUSE Build Service is a wonderful tool that allows easy build against various distributions and flavours of distributions (Leap 15.x, Tumbleweed) as well as architectures (Intel, ARM, …), and it assures consistency in case a base package (any of the ones Tryton depends on) is changed.
This can be combined with an automated test in openQA (which we currently have set-up for GNU Health, so a base test of Tryton is included). That makes the difference between Tumbleweed and other (untested) rolling releases. (enough marketing, but I had to say this
But to come back to the original point of keeping it up to date - I have build be a small python program that automates the update process. Once the announcement of updates fly in - like some days ago - I run the script and I’m basically done.
Let me know if you have additional questions!