forge/ayaports
1
0
Fork 0
Code Issues 14 Pull requests 8 Projects Releases Packages Wiki Activity Actions

infra: generate tarballs on new tag #595

New issue
Closed
opened 2024-09-09 20:12:35 +00:00 by forge · 2 comments
forge commented 2024-09-09 20:12:35 +00:00
Owner
Copy link

Some aports require pre-processed tarballs (i.e. zotero), which is handled by CI on this platform, but with one caveat: on a new release the workflow needs to be manually triggered. This is because, while we have workflows to automatically mirror the repos for those aports, new tags can't trigger any workflows since we cannot inject our custom CI.

Some aports require pre-processed tarballs (i.e. zotero), which is handled by CI on this platform, but with one caveat: on a new release the workflow needs to be manually triggered. This is because, while we have workflows to automatically mirror the repos for those aports, new tags can't trigger any workflows since we cannot inject our custom CI.
forge commented 2024-09-09 20:13:47 +00:00
Author
Owner
Copy link

To workaround this issue, we have a few possible approaches:

  1. inject workflows on new tag creation
  2. find a way for the mirror-repository.yml to trigger generate-tarbal.yml when pushing new tags
To workaround this issue, we have a few possible approaches: 1) inject workflows on new tag creation 2) find a way for the mirror-repository.yml to trigger generate-tarbal.yml when pushing new tags
forge commented 2024-09-10 12:23:48 +00:00
Author
Owner
Copy link

The first approach is working. There's still some cleaning-up to do but workflows are now injected when updating the mirror. Closing.

The first approach is working. There's still some cleaning-up to do but workflows are now injected when updating the mirror. Closing.
forge closed this issue 2024-09-10 12:23:48 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
edge
v3.20
v3.19
rstudio/upgrade-2023.9.1
zotero/minimal
papermc/update-1.21.0
codeberg-pages-server/initial
forgejo-aneksajo/upgrade-8.0.1-320
v3.16
v3.17
v3.18
freecad/upgrade-0.20.2
py3-qt6
gitlab-foss/clean-up-319
rcu/initial
py3-svgpath/rebuild
electron/upgrade-29.3.0
authentik/upgrade-2024.2.1-319
onlyoffice/initial
gitlab-foss/attempt-parallel-bundle
icedtea-web/fix-desktop
openwebstart/initial
dotnet8/diff
dotnet8/mono-319
wallabag/upgrade-2.6.7
firely/upgrade-6.0.30
openssl1.1/backport-318
caprine/upgrade-2.59.1
gitlab-foss/upgrade-16.2.7
dotnet6/upgrade-6.0.122
dotnet6/test-aspnetcore-fix
onlyoffice/initial-316
qt6-qtwebengine/initial
oxide/initial
wallabag/ldap-support
xochitl/downgrade-2.9.1
joplin/initial
trilium/initial
electron/upgrade-25.3.2
powershell/mono
git-annex/upgrade-10.20230626
gitlab-foss/15.16.0
php8-inotify/backport-316
authentik/upgrade-2023.5.0
py3-structlog/rebuild
zotero/enable-armv7
hsxkpasswd/email-valid
mastodon/unmaintain
u-boot-rm/fix-updater
remarkable/initial-dev
dotnet7/build-with-linux-rid
firefox-esr/backport-60
check-lint
airsonic-adv/upgrade-2020227
No results found.
Labels
Clear labels   
Backport

   
Enhancement

   
Fix

   
Maintenance

   
Needs action

   
New aport

   
Security

   
Upstreamed
No labels
Backport
Enhancement
Fix
Maintenance
Needs action
New aport
Security
Upstreamed
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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: forge/ayaports#595
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?