forgejo/runner
31
87
Fork 91
Code Issues 38 Pull requests 9 Releases 81 Packages 1 Activity Actions

chore: build unsupported platforms #1295

Merged
mfenniak merged 1 commit from aahlenst/runner:cross-compile into main 2026-01-15 22:43:01 +00:00
Conversation 6 Commits 1 Files changed 1 +59
aahlenst commented 2026-01-14 21:28:12 +00:00
Member
Copy link

Cross-compile Forgejo Runner for the most common platforms that are not officially supported during CI. The purpose is preventing the accidental introduction of code that breaks compilation on any of those platforms, and nothing more. It is not a goal to perform any testing on those platforms or release Forgejo Runner for them.

  • other
    • PR: chore: build unsupported platforms
Cross-compile Forgejo Runner for the most common platforms that are not officially supported during CI. The purpose is preventing the accidental introduction of code that breaks compilation on any of those platforms, and nothing more. It is not a goal to perform any testing on those platforms or release Forgejo Runner for them. <!--start release-notes-assistant--> <!--URL:https://code.forgejo.org/forgejo/runner--> - other - [PR](https://code.forgejo.org/forgejo/runner/pulls/1295): <!--number 1295 --><!--line 0 --><!--description Y2hvcmU6IGJ1aWxkIHVuc3VwcG9ydGVkIHBsYXRmb3Jtcw==-->chore: build unsupported platforms<!--description--> <!--end release-notes-assistant-->
❤️ 1
aahlenst commented 2026-01-14 21:30:28 +00:00
Author
Member
Copy link

I considered invoking make build in a for loop. But identifying the failed platform is much easier with separate steps. I hope I used the word "unsupported" enough.

I considered invoking `make build` in a for loop. But identifying the failed platform is much easier with separate steps. I hope I used the word "unsupported" enough.
mfenniak reviewed 2026-01-15 01:54:31 +00:00
.forgejo/workflows/test.yml Outdated
@ -43,0 +96,4 @@
- name: Build for macOS/arm64
run: |
GOARCH="arm64" GOOS=darwin make build
mfenniak commented 2026-01-15 01:51:50 +00:00
Owner
Copy link

Some of these steps at the end are missing make clean, and likely related, the logs indicate that nothing is being built.

Some of these steps at the end are missing `make clean`, and likely related, the logs indicate that nothing is being built.
aahlenst commented 2026-01-15 12:40:38 +00:00
Author
Member
Copy link

What happens when the attention collapses in the midst of a task. Sigh. Should be fixed.

What happens when the attention collapses in the midst of a task. Sigh. Should be fixed.
alexrp commented 2026-01-15 10:07:16 +00:00
Contributor
Copy link

I don't think you actually need to build every architecture; just an amd64 build for each OS should be plenty. I don't believe there's any architecture-specific code in the runner. (And the full matrix of arch/OS combinations is quite large.)

I don't think you actually need to build every *architecture*; just an `amd64` build for each OS should be plenty. I don't believe there's any architecture-specific code in the runner. (And the full matrix of arch/OS combinations is quite large.)
alexrp commented 2026-01-15 10:08:54 +00:00
Contributor
Copy link

Would suggest also adding dragonfly and illumos.

Would suggest also adding `dragonfly` and `illumos`.
aahlenst force-pushed cross-compile from 57884ec74b
All checks were successful
issue-labels / release-notes (pull_request_target) Successful in 5s
Details
checks / Build Forgejo Runner (pull_request) Successful in 19s
Details
checks / validate mocks (pull_request) Successful in 21s
Details
checks / validate pre-commit-hooks file (pull_request) Successful in 28s
Details
checks / runner exec tests (pull_request) Successful in 44s
Details
checks / Build unsupported platforms (pull_request) Successful in 53s
Details
checks / integration tests (docker-latest) (pull_request) Successful in 8m10s
Details
checks / integration tests (docker-stable) (pull_request) Successful in 10m25s
Details
to cb26c6f373
All checks were successful
issue-labels / release-notes (pull_request_target) Successful in 5s
Details
Integration tests for the release process / release-simulation (pull_request) Successful in 4m24s
Details
checks / Build Forgejo Runner (pull_request) Successful in 26s
Details
checks / validate mocks (pull_request) Successful in 31s
Details
checks / validate pre-commit-hooks file (pull_request) Successful in 32s
Details
checks / Build unsupported platforms (pull_request) Successful in 22s
Details
checks / runner exec tests (pull_request) Successful in 39s
Details
checks / integration tests (docker-latest) (pull_request) Successful in 8m44s
Details
checks / integration tests (docker-stable) (pull_request) Successful in 11m15s
Details
cascade / debug (pull_request_target) Has been skipped
Details
cascade / end-to-end (pull_request_target) Successful in 6s
Details
cascade / forgejo (pull_request_target) Successful in 28s
Details
2026-01-15 12:24:54 +00:00 Compare
aahlenst commented 2026-01-15 12:34:53 +00:00
Author
Member
Copy link

@alexrp I trust your judgement. @alexrp wrote in #1295 (comment):

I don't think you actually need to build every architecture; just an amd64 build for each OS should be plenty.

Sure. And if it's not, you know where to find us 😁

Would suggest also adding dragonfly and illumos.

But I won't add Solaris!

@alexrp I trust your judgement. @alexrp wrote in https://code.forgejo.org/forgejo/runner/pulls/1295#issuecomment-73499: > I don't think you actually need to build every _architecture_; just an `amd64` build for each OS should be plenty. Sure. And if it's not, you know where to find us 😁 > Would suggest also adding `dragonfly` and `illumos`. But I won't add Solaris!
mfenniak approved these changes 2026-01-15 22:42:48 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
mfenniak
Labels
Clear labels   
FreeBSD

   
Kind/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Chore

It is no fun but it needs to be done, this is a chore.

  
Kind/DependencyUpdate

for pull requests that are created by renovate when updating a dependency

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

  
Windows

Windows ports is an independent project, see https://github.com/Crown0815/Forgejo-runner-windows-builder

  
linux-powerpc64le

powerpc64le

  
linux-riscv64

   
linux-s390x

   
run-end-to-end-tests

Run https://code.forgejo.org/forgejo/end-to-end with a runner compiled from this pull request

  
run-forgejo-tests

Run https://codeberg.org/forgejo/forgejo tests importing the runner from this pull request

No labels
FreeBSD
Kind/Breaking
Kind/Bug
Kind/Chore
Kind/DependencyUpdate
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Windows
linux-powerpc64le
linux-riscv64
linux-s390x
run-end-to-end-tests
run-forgejo-tests
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
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
forgejo/runner!1295
No description provided.