bug: CI does not work self-hosted nor outside of GitHub #753
Labels
No labels
Bug
Cherry-picking
Database
Dependencies
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/Federation
Matrix/MSC
Matrix/Media
Meta
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Wont fix
old/ci/cd
old/rust
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: continuwuation/continuwuity#753
Loading…
Add table
Add a link
Reference in a new issue
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?
The CI workflows are currently dependent on Strawberry's self-hosted runner, and don't work outside of a GitHub worker environment. This will need fixing before we can use CI.
The org now has a (low performance) forgejo worker provided by myself, so hopefully getting CI into a fixed state shouldn't take too long and can work without me.
this commit diff may be relevant to see if we can reverse the self-hosted exclusiveness.
As for removing the GitHub dependency, we may need to get creative.
Is this waiting on anything? I know we've got docker builds working (for the most part), did the nix build CI get anywhere?
#761 still in progress AFACT.
What we're missing for parity right now off the top of my head:
We also don't produce debug and haswell optimised binaries, but that's just a matter of the CI taking too long right now.