Release Publication Automation #1308

Open
opened 2024-08-13 08:43:40 +00:00 by achuprov · 0 comments
Member

After the frostfs-node release, binaries must be manually compiled, published, and uploaded to t5.fs.neo.org. This requires access to someone with release publishing rights on t5.fs.neo.org, which is not always possible.

However, Forgejo enables automatic publication of a full release via action.
https://codeberg.org/forgejo/forgejo/src/branch/forgejo/.forgejo/workflows/build-release.yml

After the `frostfs-node` release, binaries must be manually compiled, published, and uploaded to` t5.fs.neo.org`. This requires access to someone with release publishing rights on `t5.fs.neo.org`, which is not always possible. However, Forgejo enables automatic publication of a full release via action. https://codeberg.org/forgejo/forgejo/src/branch/forgejo/.forgejo/workflows/build-release.yml
achuprov added the
triage
label 2024-08-13 08:43:40 +00:00
achuprov added the
internal
label 2024-08-13 09:16:32 +00:00
fyrchik added this to the vNext milestone 2024-08-13 13:21:01 +00:00
fyrchik added the
Infrastructure
label 2024-08-13 13:21:05 +00:00
potyarkin was assigned by realloc 2024-09-09 08:53:55 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: TrueCloudLab/frostfs-node#1308
No description provided.