Build Hooks¶

Both pre and post hooks are run for each build target, regardless of whether these targets are generated via a matrix of OSes and architectures or defined explicitly in targets, regardless of builder.

In addition to simple declarations as shown above multiple hooks can be declared to help retaining reusability of configuration between different build environments.

builds:
  - id: "with-hooks"
    builder: go
    targets:
      - "darwin_amd64"
      - "windows_amd64"
    hooks:
      pre:
        - first-script.sh
        - second-script.sh
      post:
        - upx "{{ .Path }}"
        - codesign -project="{{ .ProjectName }}" "{{ .Path }}"

Each hook can also have its own work directory and environment variables:

builds:
  - id: "with-hooks"
    builder: go
    targets:
      - "darwin_amd64"
      - "windows_amd64"
    hooks:
      pre:
        - cmd: first-script.sh
          dir:
            "{{ dir .Dist}}"
            # Always print command output, otherwise only visible in debug mode.
          output: true
          env:
            - HOOK_SPECIFIC_VAR={{ .Env.GLOBAL_VAR }}
        - second-script.sh

All properties of a hook (cmd, dir and env) support templating with post hooks having binary artifact available (as these run after the build). Additionally the following build details are exposed to both pre and post hooks:

Environment variables are inherited and overridden in the following order:

• global (env)
• build (builds[].env)
• hook (builds[].hooks.pre[].env and builds[].hooks.post[].env)