make it so that the CI builds an RPM of a given branch rather than of the latest tag

Actually it looks like it does this, just the naming of the RPM is a bit strange i.e it still uses the name of the latest tag. Is this expected @dinyar ?

Yeah, I'm not aware of a better alternative. To be able to upgrade a package it has to have a version + release number higher than the previous one. It would be difficult for the CI to guess the next tag's name, so we use the latest one and compute the release number from the number of commits.

Got it, thanks, I'll close this then

closed

Ok, just a last question: What did you test in B40 yesterday if you weren't sure whether the RPM contained the new changed? ;)

I checked in the /opt install that it had the changes (and it does/did)