Tracking issue for Gitea CI bugs/limitations

[dboreham]

• Task .yaml files must be stand-alone, can't reference other sibling files.
• Runner container entrypoint is overridden by Gitea, precluding automatic environment initialization.
• Some actions are unavailable / unsupported (actions must be hosted on gitea, not github?) (Solved by forking or writing our own actions as needed)
• No way to download a release attachment with a static "latest" url (we use this at GitHub for Stack Orchestrator) Offer a download link to specific release file go-gitea/gitea#3712 (should be fixed in 1.20)
• On a mirrored repository, syncing deletes any existing releases even when releases are not configured to be mirrored. Releases are deleted when mirror repository is synchronized go-gitea/gitea#22066
• Cron-style action triggers are not supported (yet) WIP: chore(actions): support cron schedule task go-gitea/gitea#22751
• Actions tasks can't be manually triggered (see workaround to "re-run" an old one though) Actions - Manually trigger a workflow/action go-gitea/gitea#23668

[telackey]

• Something about tasks having the same name (forget the details, please fill in).

This is a bug in act itself, but I haven't run into it yet in Gitea+actions. Basically, if you specify a job name when running act manually, it will try to execute that job in any workflow where it is found. That should be OK if not ideal, but it bases its container names off the job name, and so it attempts to create multiple containers with the same name.

This doesn't seem to be an issue with the way Gitea is using workflows, because it only handles one workflow file at a time.

[telackey]

The laconicd "Gosec security scanner" task fails because it cannot checkout the repo the action technote-space/[email protected]:

cloning https://gitea.com/technote-space/get-diff-action to /root/.cache/act/[email protected]
Unable to clone https://gitea.com/technote-space/get-diff-action refs/heads/v6.1.2: repository not found

It never gets far enough to try it, but I suspect it would fail getting cosmos/gosec@master as well.

It appears these GitHub URLs are being re-written to gitea, where these not standard actions do not exist. If that is all there is to it, we could always migrate/fork them to gitea.com under our own organization, but there may be additional problems lurking.

[dboreham]

Note on stable release url:

In the 1.20 release things get better. The URL now looks like:

https://host/cerc-io/stack-orchestrator2/releases/download/v1.1.0-db4728a-202306201516/laconic-so

We really want it to look something like:

https://host/cerc-io/stack-orchestrator2/releases/download-latest/laconic-so

Gitea does support this:

https://host/cerc-io/stack-orchestrator2/releases/latest

but it redirects to a tag-specific landing page

[dboreham]

This PR: go-gitea/gitea#25429 addresses our immediate needs to have a stable URL to get the latest version of a release file, like we do from GitHub.

[telackey]

https://git.vdb.to/cerc-io/hosting/issues/25