Fjord

Replace upload-artifact in Forgejo Actions

Artifacts are part of the deployment and debugging story, so validate them before migration day.

Actions

What this solves

You need to move GitHub artifact steps into Forgejo Actions.

Best fit

  • Build outputs
  • Test reports
  • Release assets
  • Deployment handoff

How to think about it

Artifacts connect build, test, release, and deployment jobs. A successful migration proves that upload, download, retention, size limits, and permissions all match the way your team debugs failed runs and promotes release assets.

Artifact inventory

steps:
  - run: npm test -- --reporter=junit
  - run: mkdir -p artifacts && cp junit.xml artifacts/
  - uses: actions/upload-artifact@v4
    with:
      name: test-report
      path: artifacts/

Practical path

  1. 01 List every workflow that uploads or downloads artifacts.
  2. 02 Replace GitHub-specific artifact actions with Forgejo-compatible steps.
  3. 03 Confirm retention, size, and access expectations with a real failed build.

When to choose another path

Confirm artifact retention before relying on logs for audits.

Keep deployment artifacts distinct from diagnostic artifacts.

Test a failed run so reviewers know where reports appear.

Next resources

Actions docs

Forgejo Actions on Fjord.

CI migration guide

Port workflows from GitHub or GitLab.

Runner sizing

Check operational readiness.

Managed hosting

Dedicated Forgejo with operated runners.

Related reading

GitHub Actions compatibility in Forgejo

Understand what usually ports from GitHub Actions to Forgejo Actions and what needs testing.

Cache dependencies in Forgejo Actions

Use dependency caches deliberately when porting Node, Python, Go, Rust, and Docker workflows to Forgejo Actions.

Docker builds in Forgejo Actions

Plan Docker image builds on Forgejo Actions runners, including cache, registry, and secret handling.