Publish Gitea releases #22

Closed
opened 2022-01-14 09:43:58 +00:00 by Jef Roosens · 1 comment

Would be nice to publish releases that have both a tarball of the source code & a statically compiled binary, both for development & actual releases.

Considering the prod build already creates a static binary, we could use this to package everything into a release.

We can use the Gitea Release Plugin from Drone for this purpose. The idea would be to create a release that only contains the source code, & then add the static binaries for the various platforms to the release as they come in, using the Gitea API. Development releases could be of the form x.y.z-n.hash where x.y.z is the last created tag (or 0.0.0 if none is present yet), n is the amount of commits since this tag, & hash the hash of the commit.

git rev-list --count HEAD ^main gives the amount commits made to the current branch since the last merge with main.
git describe --tags --abbrev=0 2> /dev/null || echo '0.0.0' returns the newest tag, or 0.0.0 if none is present.

Would be nice to publish releases that have both a tarball of the source code & a statically compiled binary, both for development & actual releases. Considering the prod build already creates a static binary, we could use this to package everything into a release. We can use the [Gitea Release Plugin](https://plugins.drone.io/drone-plugins/drone-gitea-release/) from Drone for this purpose. The idea would be to create a release that only contains the source code, & then add the static binaries for the various platforms to the release as they come in, using the Gitea API. Development releases could be of the form `x.y.z-n.hash` where `x.y.z` is the last created tag (or 0.0.0 if none is present yet), n is the amount of commits since this tag, & hash the hash of the commit. `git rev-list --count HEAD ^main` gives the amount commits made to the current branch since the last merge with main. `git describe --tags --abbrev=0 2> /dev/null || echo '0.0.0'` returns the newest tag, or `0.0.0` if none is present.
Jef Roosens added this to the (deleted) milestone 2022-01-14 09:43:58 +00:00
Jef Roosens added the
enhancement
label 2022-01-14 09:43:58 +00:00
Jef Roosens added a new dependency 2022-01-14 09:44:02 +00:00
Jef Roosens modified the milestone from 0.1.0 to 0.1.0 2022-01-16 08:29:01 +00:00
Jef Roosens removed this from the 0.1.0 milestone 2022-01-27 21:36:42 +00:00

The idea of publishing a release for every push to dev doesn't work, so we'll have to settle for just publishing releases when we create a new tag.

The idea of publishing a release for every push to dev doesn't work, so we'll have to settle for just publishing releases when we create a new tag.
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: vieter-v/vieter#22
There is no content yet.