macOS build still fetches the source from GitLab #390

Open
opened 2026-11-18 13:44:15 +00:00 by jonasled · 0 comments
Owner

The macOS build runs in the GitHub repo jonasled/sfptool-macos (workflow build-macos.yml) because it needs a macOS runner. The build-app-macos job of the Forgejo CI (.forgejo/workflows/ci.yml, tags only) dispatches it and downloads the artifact macos-universal.

After the migration to Forgejo this is broken:

  • The GitHub workflow fetches the source from the GitLab repo (https://jonasled.dev/jonasled/sfp-tool.git) by commit SHA using the secret GITLAB_TOKEN. New commits and tags only exist on Forgejo (https://forgejo.jonasled.dev/jonasled/sfp-tool), so the checkout fails.
  • The workflow inputs are still called gitlab_sha and gitlab_job_id (the Forgejo job dispatches with these names and matches the run by gitlab-job <run id> in the run name).
  • upload-to-s3 waits for build-app-macos, so tagged releases are blocked until this is fixed.

To do:

  • Change the fetch step in sfptool-macos to Forgejo and add a Forgejo token secret (read access) there; remove GITLAB_TOKEN
  • Optionally rename the inputs (and adjust ci.yml to match)
  • Test with a tag build
The macOS build runs in the GitHub repo `jonasled/sfptool-macos` (workflow `build-macos.yml`) because it needs a macOS runner. The `build-app-macos` job of the Forgejo CI (`.forgejo/workflows/ci.yml`, tags only) dispatches it and downloads the artifact `macos-universal`. After the migration to Forgejo this is broken: - The GitHub workflow fetches the source from the GitLab repo (`https://jonasled.dev/jonasled/sfp-tool.git`) by commit SHA using the secret `GITLAB_TOKEN`. New commits and tags only exist on Forgejo (https://forgejo.jonasled.dev/jonasled/sfp-tool), so the checkout fails. - The workflow inputs are still called `gitlab_sha` and `gitlab_job_id` (the Forgejo job dispatches with these names and matches the run by `gitlab-job <run id>` in the run name). - `upload-to-s3` waits for `build-app-macos`, so tagged releases are blocked until this is fixed. To do: - [ ] Change the fetch step in `sfptool-macos` to Forgejo and add a Forgejo token secret (read access) there; remove `GITLAB_TOKEN` - [ ] Optionally rename the inputs (and adjust `ci.yml` to match) - [ ] Test with a tag build
Sign in to join this conversation.
No labels
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
jonasled/sfp-tool#390
No description provided.