sourcehut#

The sourcehut provider submits jobs to a builds.sr.ht instance. Each Tangled workflow becomes one job: tack submits the job via GraphQL, polls it until terminal, and publishes sh.tangled.pipeline.status records on each transition.

Configure tack#

Generate a token at https://meta.sr.ht/oauth2/personal-token with builds.sr.ht/JOBS:RW access, set the TACK_SOURCEHUT_TOKEN=$token env var, then start tack.

Workflow YAML#

Your sourcehut build manifest is defined via tangled workflow inline - see tack.sourcehut.manifest. It is submitted to builds.sr.ht verbatim, with a few TACK_* environment variables merged into its top-level environment: map.

when:
  - event: ["push"]
    branch: ["main"]

engine: tack

tack:
  sourcehut:
    manifest: |
      image: alpine/edge
      sources:
        - https://tangled.org/j3s.sh/testy
      tasks:
        - test: |
            ls -l testy

Optional fields:

tack:
  sourcehut:
    instance: https://selfhosted.sr.ht.example.org
    tags: ["tack", "ci"]
    note: "manual note for the job list"
    secrets: true

• instance: full URL (with scheme) of an alternate builds.sr.ht deployment. Defaults to the provider's configured instance.
• tags: passed through to the submit API. Defaults to ["tack"] so jobs are filterable in the builds.sr.ht UI.
• note: passed through to the submit API. Defaults to tangled: <workflow> @ <short-commit>.
• secrets: opt in to sourcehut secret injection. Default false.

Injected environment#

Tack merges the following into the manifest's environment: map before submitting. These can be overridden via user definition.

Status mapping#

Unknown upstream statuses are logged.