How should we deal with gitea updates in the future?

[DO1JLR]

Gitea has been updated more often lately. And the practice of updating it every time in this role can be done... But it doesn't seem to make that much sense in the long run.

What do you think about extending this ansible role by adding some magic that automatically downloads the newest gitea version? For example by evaluating a curl on https://github.com/go-gitea/gitea/releases/latest...

Of course the variable gitea_version: 1.12.1 should still be valid. But if you write something like gitea_version: latest, a download of the latest version would be nice.

Or what do you think?

[thomas-maurice]

That makes sense to approach it this way, that would actually be cooler that manually updating it like we do right now

It would have to be clear in the documentation that using latest will grab whatever version is the latest so you may expect restarts when running.

I am however concerned if we allow the user to both use latest and a fixed version, then sometimes we might end up in a case where a user is using the version X but we added to the templates config options that were introduced after version X so that might create issues

[thomas-maurice]

@DO1JLR any opinion about that ?

I am worried that people would pin Gitea versions and end up with completely fucked configs because we will follow the latest release, which might not be good.

I am not sure ansible allows that but maybe we could do one release per Gitea release. That would however tremendously increase the maintenance time.

At this point I have no strong opinions so I am really open to suggestions.

[sapk]

There is a download url for the last version of a minor version.
For example, https://dl.gitea.io/gitea/1.12 will be the last 1.12.x release.
That way you could easely grab the last non-breaking binary and update less often (around 2 times a year) the link.

[DO1JLR]

I like the idea from @sapk

[sapk]

Sorry, I made a assomption that it follow the same scheme of docker but dl.gitea.io/gitea/1.12 is the last build from 1.12 branch. It is the last commit and not the last release.

Maybe we could do something on gitea to have the same scheme somewhere on dl.gitea.io as we use for docker release.

• 1 = last 1.x.x
• 1.12 = last 1.12.x

[thomas-maurice]

@sapk like have gitea to have a pattern that accomodates us ? xD I mean that sure would be swell but I'm not sure they even know we exist

[thomas-maurice]

Should I just mention @giteaio on twitter and ask them for advice ?

[techknowlogick]

@thomas-maurice @sapk is a maintainer of Gitea, and I suspect he found this issue from the official Gitea twitter account retweeting your request for help.

[thomas-maurice]

Well then that would be truely awesome!

[thomas-maurice]

The idea here is not to inadvertently break people's setups

[techknowlogick]

The idea here is not to inadvertently break people's setups

Indeed. Like @sapk suggested above, we could probably move to align dl.gitea.io with the way we tag docker images, which isn't a huge change.

[thomas-maurice]

That would be brilliant mate <3