Installation

Leeway is a heavily caching build system for Go, Yarn and Docker projects. Its features are:

source dependent versions: leeway computes the version of a package based on the sources, dependencies and configuration that make up this package. There's no need (or means) to manually version packages.
two-level package cache: leeway caches its build results locally and remotely. The remote cache (a Google Cloud Storage bucket) means builds can share their results and thus become drastically faster.
parallel builds: because leeway understands the dependencies of your packages it can build them as parallel as possible.
built-in support for Yarn and Go: leeway knows how to link, build and test Yarn and Go packages and applications. This makes building software written in those languages straight forward.
build arguments: leeway supports build arguments which can parametrize packages at build time. We support version dependent arguments (where the version depends on the argument value), component-wide constants and workspace-level defaults.
rich CLI: leeways CLI supports deep inspection of the workspace and its structure. Its output is easy to understand and looks good.

Leeway structures a repository in three levels:

The workspace is the root of all operations. All component names are relative to this path. No relevant file must be placed outside the workspace. The workspace root is marked with a WORKSPACE.yaml file.
A components is single piece of standalone software. Every folder in the workspace which contains a BUILD.yaml file is a component. Components are identifed by their path relative to the workspace root.
Packages are the buildable unit in leeway. Every component can define multiple packages in its build file. Packages are identified by their name prefixed with the component name, e.g. some-component:pkg.

Installation

Leeway assumes its running on Linux or macOS. It is very very unlikely that this runs on Windows out-of-the-box. To install, just download and unpack a release.

Build setup

Workspace

Place a file named WORKSPACE.yaml in the root of your workspace. For convenience sake you should set the LEEWAY_WORKSPACE_ROOT env var to the path of that workspace. For example:

touch WORKSPACE.yaml
export LEEWAY_WORKSPACE_ROOT=$PWD

The WORKSPACE.yaml may contain some default settings for the workspace:

# defaultTarget is package we build when just running `leeway build`
defaultTarget: some/package:name
#defaultArgs are key=value pairs setting default values for build arguments
defaultArgs:
  key: value

Users can override, and provide additional default arguments using a WORKSPACE.args.yaml file in the workspace root. This is useful for providing local overrides which you might not want to commit to Git. The WORKSPACE.args.yaml takes key value pairs which become available as build arguments. The values herein take precedence over the default arguments in the WORKSPACE.yaml.

foo: bar
key: value

Component

Place a BUILD.yaml in a folder somewhere in the workspace to make that folder a component. A BUILD.yaml primarily contains the packages of that components, but can also contain constant values (think of them as metadata). For example:

# const defines component-wide constants which can be used much like build arguments. Only string keys and values are supported.
const:
  internalName: example
  someRandomProperty: value
packages:
- ...
scripts:
- ...

Script

Scripts are a great way to automate tasks during development time (think yarn scripts). Unlike packages they do not run in isolation by default, but have access to the original workspace. What makes scripts special is that they can dependent on packages which become available to a script in the PATH and as environment variables.

Under the scripts key in the component's BUILD.yaml add:

# name is the component-wide unique name of script. Packages and scripts do NOT share a namespace.
# You can have a package called foo and a script called foo within the same component.
name: some-script-name
# description provides a short synopsis of the script. Shown when running `leeway collect scripts`.
description: A sentence describing what the script is good for.
# Deps list dependencies to packages (NOT scripts) which must be built prior to running this script.
# All built dependencies get added to the PATH environment variable. This is handy if your workspace
# contains tools you want to use in a script.
deps:
- some/other:package
# Env sets environment variables which are present during script execution.
env:
- MESSAGE=hello
# Workdir changes the workdir location/layout of working dir of the script. The following choices are available:
# - origin (default): execute the script in the directory of the containing component in the original workspace.
#                     This is the default mode and handy if one wants to automate tasks in the development workspace.
# - packages:         produces a filesystem layout much like during a generic package build where all deps are
#                     found by their name in a temporary directory. This provides some isolation from the original
#                     workspace, while giving full access to the built dependencies.
workdir: origin
# The actual script. For now, only bash scripts are supported. The shebang is added automatically.
script: |
  echo $MESSAGE, this is where the script goes
  if [ "A$(ps -o comm= -p $$)" = "Abash" ]; then
    echo "it's the bash alright"
  fi
  echo "build args work to: ${myBuildArg}"

Package

A package is an entry in a BUILD.yaml in the packages section. All packages share the following fields:

# name is the component-wide unique name of this package
name: must-not-contain-spaces
# Package type must be one of: go, yarn, docker, generic
type: generic
# Sources list all sources of this package. Entries can be double-star globs and are relative to the component root.
# Avoid listing sources outside the component folder.
srcs:
- "**/*.yaml"
- "glob/**/path"
# Deps list dependencies to other packages which must be built prior to building this package. How these dependencies are made
# available during build depends on the package type.
deps:
- some/other:package
# Argdeps makes build arguments version relevant. I.e. if the value of a build arg listed here changes, so does the package version.
argdeps:
- someBuildArg
# Env is a list of key=value pair environment variables available during package build
env:
- CGO_ENABLED=0
# Config configures the package build depending on the package type. See below for details
config:
  ...

Go packages

config:
  # Packaging method. See https://godoc.org/github.com/gitpod-io/leeway/pkg/leeway#GoPackaging for details. Defaults to library.
  packaging: library
  # If true leeway runs `go generate -v ./...` prior to testing/building. Defaults to false.
  generate: false
  # If true disables `go test -v ./...`
  dontTest: false
  # If true disables the enforcement of `go fmt`. By default, if the code is not gofmt'ed the build fails.
  dontCheckGoFmt: false
  # If true disables the linting stage.
  dontLint: false
  # Overrides the `go build .` command. Supersedes buildFlags.
  buildCommand: []
  # [DEPRECATED: use buildCommand instead] A list of flags passed to `go build`. Useful for passing `ldflags`.
  buildFlags: []
  # Command that's executed to lint the code
  lintCommand: ["golangci-lint", "run"]
  # GoMod can point to a go.mod file outside the component root. Leeway expects a go.sum alongside the go.mod.
  goMod: "../go.mod"

Yarn packages

config:
  # yarnlock is the path to the yarn.lock used to build this package. Defaults to `yarn.lock`. Useful when building packages in a Yarn workspace setup.
  # Automatically added to the package sources.
  yarnlock: "yarn.lock"
  # tsconfig is the path to the tsconfig.json used to build this package. Detauls to `tsconfig.json`
  # Automatically added to the package sources.
  tsconfig: "tsconfig.json"
  # packaging method. See https://godoc.org/github.com/gitpod/leeway/pkg/leeway#YarnPackaging for details.
  # Defaults to library
  packaging: library
  # If true disables `yarn test`
  dontTest: false
  # commands overrides the default commands executed during build
  commands:
    install: ["yarn", "install"]
    build: ["yarn", "build"]
    test: ["yarn", "test"]

Docker packages

config:
  # Dockerfile is the name of the Dockerfile to build. Automatically added to the package sources.
  dockerfile: "Dockerfile"
  # exportToCache controls whether images are pushed directly or exported to cache
  # - false (default): push directly to registry (legacy behavior)
  # - true: export to cache for signing (enables SLSA L3 compliance)
  # Can be overridden via --docker-export-to-cache flag or LEEWAY_DOCKER_EXPORT_TO_CACHE env var
  exportToCache: false
  # Metadata produces a metadata.yaml file in the resulting package tarball.
  metadata:
    foo: bar
  # build args are Docker build arguments. Often we just pass leeway build arguments along here.
  buildArgs:
  - arg=value
  - other=${someBuildArg}
  # image lists the Docker tags leeway will use and push to
  image:
  - gitpod/leeway:latest
  - gitpod/leeway:${__pkg_version}

The first image name of each Docker dependency which pushed an image will result in a build argument. This mechanism enables a package to build the base image for another one, by using the build argument as FROM value. The name of this build argument is the package name of the dependency, transformed as follows:

/ is replaced with _
: is replaced with __
all uppercase.

E.g. component/nested:docker becomes COMPONENT_NESTED__DOCKER.

For SLSA Level 3 compliance: Set exportToCache: true to enable cache-based Docker image distribution with cryptographic signing. This can be overridden globally using:

CLI flag: leeway build --docker-export-to-cache
Environment variable: LEEWAY_DOCKER_EXPORT_TO_CACHE=true

See leeway build --help for more details.

Generic packages

config:
  # A list of commands to execute. Beware that the commands are not executed in a shell. If you need shell features (e.g. wildcards or pipes),
  # wrap your command in `sh -c`. Generic packages without commands result in an empty tar file.
  commands:
  - ["echo", "hello world"]
  - ["sh", "-c", "ls *"]

Dynaimc package scripts

Packages can be dynamically produced within a component using a dynamic package script named BUILD.js. This ECMAScript 5.1 file is executed using Goja and produces a packages array which contains the package struct much like they'd exist within the BUILD.yaml. For example:

Leeway interacts with the script using global variables, specifically:

args [input] a JavaScript object containing the build arguments which have explicitely been passed to leeway.
packages [output] where the script produces an array of package structures akin to those found in a BUILD.yaml file.

BUILD.js file

let packages = [];

let deps = [];
for(let i = 0; i < 5; i++) {
  const name = "hello-"+i;
  deps.push(name);
  packages.push({
    name: name,
    type: "generic",
    config: {
      commands: [
        ["echo", args.msg + ": hello from "+i]
      ]
    }
  });
}

packages.push({
  name: "all",
  type: "generic",
  deps: deps.map(d => ":" + d),
})

Equivalent BUILD.yaml

pacakages:
- name: all
  type: generic
  deps:
    - hello-1
    - hello-2
    - hello-3
    - hello-4
    - hello-5
- name: hello-1
  type: generic
  config:
    commands:
      - ["echo", "${msg}: hello from 1"]
- name: hello-2
  type: generic
  config:
    commands:
      - ["echo", "${msg}: hello from 2"]
- name: hello-3
  type: generic
  config:
    commands:
      - ["echo", "${msg}: hello from 3"]
...

Note that for a BUILD.js to become effective/be recodnized there needs to a (possibly empty) BUILD.yaml in the same directory.

Build arguments

In a package definition one can use build arguments. Build args have the form of ${argumentName} and are string-replaced when the package is loaded. It's advisable to use build args only within the config section of packages. Constants and built-in build args do not even work outside of the config section.

Leeway supports built-in build arguments:

__pkg_version resolves to the leeway version hash of a component.
__git_commit contains the current Git commit if the build is executed from within a Git working copy. If this variable is used and the build is not executed from within a Git working copy the variable resolution will fail. If the package sources contain uncommitted files/directories, then __pkg_version will be appended to __git_commit
__git_commit_short shortened version of __git_commit to the first 7 characters.

Package Variants

Leeway supports build-time variance through "package variants". Those variants are defined on the workspace level and can modify the list of sources, environment variables and config of packages. For example consider a WORKSPACE.YAML with this variants section:

variants:
- name: nogo
  srcs:
    exclude:
    - "**/*.go"
  config:
    go:
      buildFlags:
        - tags: foo

This workspace has a (nonsensical) nogo variant that, when enabled, excludes all go source files from all packages. It also changes the config of all Go packages to include the -tags foo flag. You can explore the effects of a variant using collect and describe, e.g. leeway --variant nogo collect files vs leeway collect files. You can list all variants in a workspace using leeway collect variants.

Environment Manifest

Leeway does not control the environment in which it builds the packages, but assumes that all required tools are available already (e.g. go or yarn). This however can lead to subtle failure modes where a package built in one enviroment ends up being used in another, because no matter of the environment they were built in, they get the same version.

To prevent such issues, leeway computes an environment manifest which contains the versions of the tools used, as well as some platform information. The entries in that manifest depend on the package types used by that workspace, e.g. if only Go packages exist in the workspace, only go version, GOOS and GOARCH will be part of the manifest. You can inspect a workspace's environment manifest using leeway describe environment-manifest.

You can add your own entries to a workspace's environment manifest in the WORKSPACE.yaml like so:

environmentManifest:
  - name: gcc
    command: ["gcc", "--version"]

Using this mechanism you can also overwrite the default manifest entries, e.g. "go" or "yarn".

SBOM and Vulnerability Scanning

Leeway includes built-in support for Software Bill of Materials (SBOM) generation and vulnerability scanning. This feature helps you identify and manage security vulnerabilities in your software supply chain.

Enabling SBOM Generation

SBOM generation is configured in your WORKSPACE.yaml file:

sbom:
  enabled: true                # Enable SBOM generation
  scanVulnerabilities: true    # Enable vulnerability scanning
  failOn: ["critical", "high"] # Fail builds with vulnerabilities of these severities (default: build does not fail)
  parallelism: 8               # Number of parallel workers for SBOM generation (default: CPU cores)
  ignoreVulnerabilities:       # Workspace-level ignore rules
    - vulnerability: "CVE-2023-1234"
      reason: "Not exploitable in our context"

When enabled, Leeway automatically generates SBOMs for each package during the build process in multiple formats (CycloneDX, SPDX, and Syft JSON) using Syft. These SBOMs are included in the package's build artifacts.

Performance Configuration

The parallelism setting controls how many parallel workers are used for SBOM generation. By default, Leeway uses the number of CPU cores available for optimal performance. You can override this setting:

Default behavior: Uses runtime.NumCPU() (number of CPU cores)
Custom value: Set to any positive integer (e.g., parallelism: 4)
Sequential processing: Set to 1 for single-threaded operation

Based on performance benchmarking, the default CPU core count provides significant performance improvements (up to 16% faster) for larger repositories while having minimal impact on smaller ones.

SBOM Commands

Leeway provides two commands for working with SBOMs:

sbom export

The sbom export command allows you to export the SBOM of a previously built package:

# Export SBOM in CycloneDX format (default) to stdout
leeway sbom export some/component:package

# Export SBOM in a specific format to a file
leeway sbom export --format spdx --output sbom.spdx.json some/component:package

# Export SBOMs for a package and all its dependencies to a directory
leeway sbom export --with-dependencies --output-dir sboms/ some/component:package

Options:

--format: SBOM format to export (cyclonedx, spdx, syft). Default is cyclonedx.
--output, -o: Output file (defaults to stdout).
--with-dependencies: Export SBOMs for the package and all its dependencies.
--output-dir: Output directory for exporting multiple SBOMs (required with --with-dependencies).

This command uses existing SBOM files from previously built packages and requires SBOM generation to be enabled in the workspace settings.

sbom scan

The sbom scan command scans a package's SBOM for vulnerabilities and exports the results:

# Scan a package for vulnerabilities
leeway sbom scan --output-dir vuln-reports/ some/component:package

# Scan a package and all its dependencies for vulnerabilities
leeway sbom scan --with-dependencies --output-dir vuln-reports/ some/component:package

Options:

--output-dir: Directory to export scan results (required).
--with-dependencies: Scan the package and all its dependencies.

This command uses existing SBOM files from previously built packages and requires SBOM generation to be enabled in the workspace settings (vulnerability scanning does not need to be enabled).

Vulnerability Scanning

When scanVulnerabilities is enabled, Leeway scans the generated SBOMs for vulnerabilities using Grype. The scan results are written to the build directory in multiple formats:

vulnerabilities.txt - Human-readable table format
vulnerabilities.json - Detailed JSON format
vulnerabilities.cdx.json - CycloneDX format
vulnerabilities.sarif - SARIF format for integration with code analysis tools

Configuring Build Failure Thresholds

The failOn setting determines which vulnerability severity levels will cause a build to fail. Omit this configuration to generate only the reports without causing the build to fail. For example:

failOn: ["critical", "high"]  # Fail on critical and high vulnerabilities

Supported severity levels are: critical, high, medium, low, negligible, and unknown.

Ignoring Vulnerabilities

Leeway provides a flexible system for ignoring specific vulnerabilities. Ignore rules can be defined at both the workspace level (in WORKSPACE.yaml) and the package level (in BUILD.yaml). For detailed documentation on ignore rules, see Grype's documentation on specifying matches to ignore.

Ignore Rule Configuration

Ignore rules use Grype's powerful filtering capabilities:

# In WORKSPACE.yaml (workspace-level rules)
sbom:
  ignoreVulnerabilities:
    # Basic usage - ignore a specific CVE
    - vulnerability: "CVE-2023-1234"
      reason: "Not exploitable in our context"
      
    # Advanced usage - ignore a vulnerability only for a specific package
    - vulnerability: "GHSA-abcd-1234-efgh"
      reason: "Mitigated by our application architecture"
      package:
        name: "vulnerable-pkg"
        version: "1.2.3"
        
    # Using fix state
    - vulnerability: "CVE-2023-5678"
      reason: "Will be fixed in next dependency update"
      fix-state: "fixed"
      
    # Using VEX status
    - vulnerability: "CVE-2023-9012"
      reason: "Not affected as we don't use the vulnerable component"
      vex-status: "not_affected"
      vex-justification: "vulnerable_code_not_in_execute_path"

Package-Level Ignore Rules

You can also specify ignore rules for specific packages in their BUILD.yaml file:

# In package BUILD.yaml
packages:
  - name: my-package
    type: go
    # ... other package configuration ...
    sbom:
      ignoreVulnerabilities:
        - vulnerability: "GHSA-abcd-1234-efgh"
          reason: "Mitigated by our application architecture"

Package-level rules are combined with workspace-level rules during vulnerability scanning.

Available Ignore Rule Fields

Leeway's ignore rules support all of Grype's filtering capabilities:

vulnerability: The vulnerability ID to ignore (e.g., "CVE-2023-1234")
reason: The reason for ignoring this vulnerability (required)
namespace: The vulnerability namespace (e.g., "github:golang")
fix-state: The fix state to match (e.g., "fixed", "not-fixed", "unknown")
package: Package-specific criteria (see below)
vex-status: VEX status (e.g., "affected", "fixed", "not_affected")
vex-justification: Justification for the VEX status
match-type: The type of match to ignore (e.g., "exact-direct-dependency")

The package field can contain:

name: Package name (supports regex)
version: Package version
language: Package language
type: Package type
location: Package location (supports glob patterns)
upstream-name: Upstream package name (supports regex)

Configuration

Leeway is configured exclusively through the WORKSPACE.yaml/BUILD.yaml files and environment variables. The following environment variables have an effect on leeway:

LEEWAY_WORKSPACE_ROOT: Contains the path where to look for a WORKSPACE file. Can also be set using --workspace.
LEEWAY_REMOTE_CACHE_STORAGE: Defines the remote caching storage provider. Valid values are "GCP" and "AWS". Defaults to "GCP".
LEEWAY_REMOTE_CACHE_BUCKET: Enables remote caching using GCP or S3 buckets. Required credentials depend on the storage provider:
- "GCP": leeway expects "gsutil" in the path configured and authenticated so that it can work with the bucket.
- "AWS": leeway expects that AWS credentials have been provided and with read/write access to the S3 bucket. For details on configuring AWS credentials see https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html
LEEWAY_CACHE_DIR: Location of the local build cache. The directory does not have to exist yet.
LEEWAY_BUILD_DIR: Working location of leeway (i.e. where the actual builds happen). This location will see heavy I/O which makes it advisable to place this on a fast SSD or in RAM.
LEEWAY_YARN_MUTEX: Configures the mutex flag leeway will pass to yarn. Defaults to "network". See https://yarnpkg.com/lang/en/docs/cli/#toc-concurrency-and-mutex for possible values.
LEEWAY_EXPERIMENTAL: Enables exprimental features

Provenance (SLSA) - EXPERIMENTAL

leeway can produce provenance information as part of a build. At the moment only SLSA Provenance v0.2 is supported. This support is experimental.

Provenance generation is enabled in the WORKSPACE.YAML file.

provenance:
  enabled: true
  slsa: true

Once enabled, all packages carry an attestation bundle which is compliant to the SLSA v0.2 spec in their cached archive. The bundle is complete, i.e. not only contains the attestation for the package build, but also those of its dependencies.

Automatic SLSA L3 Feature Activation

When provenance.slsa: true is set, Leeway automatically enables all SLSA L3 runtime features to ensure build integrity and artifact distinguishability:

✅ Cache verification: Downloads are verified against Sigstore attestations
✅ In-flight checksums: Build artifacts are checksummed during the build to prevent tampering
✅ Docker export mode: Docker images go through the cache and signing flow (workspace default)

These features are automatically enabled by setting environment variables:

LEEWAY_SLSA_CACHE_VERIFICATION=true
LEEWAY_ENABLE_IN_FLIGHT_CHECKSUMS=true
LEEWAY_DOCKER_EXPORT_TO_CACHE=true
LEEWAY_SLSA_SOURCE_URI (set from Git origin)

Configuration Precedence

The Docker export mode follows a clear precedence hierarchy (highest to lowest):

CLI flag - leeway build --docker-export-to-cache=false
Explicit environment variable - Set before workspace loading
Package config - exportToCache: false in BUILD.yaml (Docker packages only)
Workspace default - Auto-set by provenance.slsa: true
Global default - false (legacy behavior)

Examples

Scenario 1: SLSA enabled, all Docker packages export by default

# WORKSPACE.yaml
provenance:
  enabled: true
  slsa: true

# backend/BUILD.yaml
packages:
  - name: backend
    type: docker
    config:
      dockerfile: Dockerfile
      image:
        - registry.example.com/backend:latest
    # No exportToCache specified → inherits workspace default (export enabled)

Scenario 2: SLSA enabled, but one package opts out

# WORKSPACE.yaml  
provenance:
  enabled: true
  slsa: true

# backend/BUILD.yaml
packages:
  - name: backend
    type: docker
    config:
      dockerfile: Dockerfile
      image:
        - registry.example.com/backend:latest
      exportToCache: false  # Explicit opt-out - push directly

Scenario 3: Force export OFF for testing

# Set before running leeway - overrides package config and workspace default
export LEEWAY_DOCKER_EXPORT_TO_CACHE=false
leeway build :backend
# User override wins over package config and workspace default

Scenario 4: CLI flag for one-off override

# Override everything for this build only
leeway build :backend --docker-export-to-cache=true
# CLI flag has highest priority

Artifact Distinguishability

When SLSA provenance is enabled, the package manifest includes provenance: version=3 slsa, which changes the artifact version hash. This ensures artifacts built with SLSA L3 features are automatically distinguishable from legacy artifacts in the cache.

# With SLSA enabled:
buildProcessVersion: 1
provenance: version=3 slsa    # ← N.B.
sbom: version=1
environment: f92ccd7479251ffa...

# Without SLSA:
buildProcessVersion: 1
sbom: version=1
environment: f92ccd7479251ffa...

Dirty vs clean Git working copy

When building from a clean Git working copy, leeway will use a reference to the Git remote origin as material (part of the SLSA link).

Signing attestations

To support SLSA level 2, leeway can sign the attestations it produces. To this end, you can provide the filepath to a key either as part of the WORKSPACE.yaml or through the LEEWAY_PROVENANCE_KEYPATH environment variable.

Inspecting provenance

You can inspect the generated attestation bundle by extracting it from the built and cached archive. For example:

# run a build
leeway build //:app

# export the attestation bundle
leeway provenance export //:app

# export the decoded attestation bundle
leeway provenance export --decode //:app

# verify that all material came from a Git repo
leeway provenance assert --git-only //:app

# verify that all subjects were built using leeway
leeway provenance asert --built-with-leeway //:app

# decode an attestation bundle from a file (also works for assertions)
leeway provenance export --decode file://some-bundle.jsonl

Caveats

provenance is part of the leeway package version, i.e. when you enable provenance that will naturally invalidate previously built packages.
if attestation bundle entries grow too large this can break the build process. Use LEEWAY_MAX_PROVENANCE_BUNDLE_SIZE to set the buffer size in bytes. This defaults to 2MiB. The larger this buffer is, the larger bundle entries can be used, but the more memory the build process will consume. If you exceed the default, inspect the bundles first (especially the one that fails to load) and see if the produced subjects make sense.

Troubleshooting SLSA L3 Features

Features not activating?

Check if SLSA is properly enabled in your workspace:

# Verify workspace config
cat WORKSPACE.yaml | grep -A2 provenance

# Check environment variables are set
env | grep LEEWAY_

# Enable verbose logging to see activation
leeway build -v :package 2>&1 | grep "SLSA\|provenance"

Docker export not working as expected?

Verify the precedence hierarchy:

# Check if CLI flag is set
leeway build :package --docker-export-to-cache=true -v

# Check if environment variable is set
echo $LEEWAY_DOCKER_EXPORT_TO_CACHE

# Check package config in BUILD.yaml
grep -A5 "exportToCache" BUILD.yaml

Environment variables set before workspace loading?

User environment variables must be set BEFORE running leeway:

# Correct: set before running leeway
export LEEWAY_DOCKER_EXPORT_TO_CACHE=false
leeway build :package

# Incorrect: too late, workspace already loaded
leeway build :package
export LEEWAY_DOCKER_EXPORT_TO_CACHE=false

Debugging

When a build fails, or to get an idea of how leeway assembles dependencies, run your build with leeway build -c local (local cache only) and inspect your $LEEWAY_BUILD_DIR.

CLI tips

How can I build a package in the current component/folder?

leeway build .:package-name

Is there bash autocompletion?

Yes, run . <(leeway bash-completion) to enable it. If you place this line in .bashrc you'll have autocompletion every time.

How can I find all packages in a workspace?

# list all packages in the workspace
leeway collect
# list all package names using Go templates
leeway collect -t '{{ range $n := . }}{{ $n.Metadata.FullName }}{{"\n"}}{{end}}'
# list all package names using jq
leeway collect -o json | jq -r '.[].metadata.name'

How can I find out more about a package?

# print package description on the console
leeway describe some/components:package
# dump package description as json
leeway describe some/components:package -o json

How can I inspect a packages depdencies?

# print the dependency tree on the console
leeway describe dependencies some/components:package
# print the denendency graph as Graphviz dot
leeway describe dependencies --dot some/components:package
# serve an interactive version of the dependency graph
leeway describe dependencies --serve=:8080 some/components:package

How can I print a component constant?

# print all constants of the component in the current working directory
leeway describe const .
# print all constants of a component
leeway describe const some/component/name
# print the value of the `someName` constant of `some/component/name`
leeway describe const some/component/name -o json | jq -r '.[] | select(.name=="foo").value'

How can I find all components with a particular constant?

leeway collect components -l someConstant

How can I export only a workspace the way leeway sees it, i.e. based on the packages?

LEEWAY_EXPERIMENTAL=true leeway export --strict /some/destination

macOS: leeway fails with "cp --parents" not being a valid command

The way depends on GNU utilities. Install them and make sure they're in your path.

brew install coreutils

Contributing

Creating a new release

Releases of Leeway are created by the release workflow which uses goreleaser/goreleaser-action.

To create a new release create a new Git tag and push it:

git tag vX.X.X
git push origin vX.X.X

This will trigger the workflow which you can find here. Once it's done a new release will show up in GitHub here.

Name		Name	Last commit message	Last commit date
Latest commit History 462 Commits
.devcontainer		.devcontainer
.githooks		.githooks
.github/workflows		.github/workflows
.gitpod		.gitpod
.theia		.theia
.vscode		.vscode
cmd		cmd
pkg		pkg
.gitignore		.gitignore
.goreleaser.yaml		.goreleaser.yaml
BUILD.yaml		BUILD.yaml
LICENSE		LICENSE
README.md		README.md
WORKSPACE.yaml		WORKSPACE.yaml
codecov.yml		codecov.yml
go.mod		go.mod
go.sum		go.sum
logo.png		logo.png
main.go		main.go

License

gitpod-io/leeway

Folders and files

Latest commit

History

Repository files navigation

Installation

Build setup

Workspace

Component

Script

Package

Go packages

Yarn packages

Docker packages

Generic packages

Dynaimc package scripts

Build arguments

Package Variants

Environment Manifest

SBOM and Vulnerability Scanning

Enabling SBOM Generation

Performance Configuration

SBOM Commands

sbom export

sbom scan

Vulnerability Scanning

Configuring Build Failure Thresholds

Ignoring Vulnerabilities

Ignore Rule Configuration

Package-Level Ignore Rules

Available Ignore Rule Fields

Configuration

Provenance (SLSA) - EXPERIMENTAL

Automatic SLSA L3 Feature Activation

Configuration Precedence

Examples

Artifact Distinguishability

Dirty vs clean Git working copy

Signing attestations

Inspecting provenance

Caveats

Troubleshooting SLSA L3 Features

Debugging

CLI tips

How can I build a package in the current component/folder?

Is there bash autocompletion?

How can I find all packages in a workspace?

How can I find out more about a package?

How can I inspect a packages depdencies?

How can I print a component constant?

How can I find all components with a particular constant?

How can I export only a workspace the way leeway sees it, i.e. based on the packages?

macOS: leeway fails with "cp --parents" not being a valid command

Contributing

Creating a new release

About

Resources

License

Code of conduct

Contributing

Security policy

Uh oh!

Stars

Watchers

Forks

Releases 75

Packages 0

Uh oh!

Contributors 20

Uh oh!

Languages

Packages