Skip to content

AGENTS.md

Latest commit

 

History

History
49 lines (37 loc) · 1.49 KB

AGENTS.md

File metadata and controls

49 lines (37 loc) · 1.49 KB
Raw

AGENTS.md

Run the checks locally

The checks need an engine at this SDK's floor, v1.0.0-beta.18, or later. The CLI runs on the engine it ships with; --engine or DAGGER_ENGINE selects another (dagger help engine):

export DAGGER_ENGINE=container://<running-engine>

Run the e2e checks from the root of this checkout, by name or all of them:

dagger check -m .dagger/modules/e2e -l
dagger check -m .dagger/modules/e2e find-client-root-check generate-scope-init-check
dagger check -m .dagger/modules/e2e 'e2e:*'

Run the SDK library's unit tests and the staleness checks of the committed assets:

dagger check packager:unit-tests
dagger check packager:generate:stale templates:generate:stale

Without a pattern, dagger check also selects the engine-e2e checks, which build engines from dagger/dagger commits:

dagger check engine-e2e:floor-check
dagger check engine-e2e:below-floor-check
dagger check engine-e2e:dev-sdk-check

floor-check runs every e2e check on the floor engine, built from its commit. below-floor-check checks that v1.0.0-beta.17 is refused. dev-sdk-check initializes a Java module through the CLI on the floor engine and calls it. To run e2e checks on the floor's released engine instead:

dagger check --engine=image://registry.dagger.io/engine:v1.0.0-beta.18 \
  -m .dagger/modules/e2e find-client-root-check

Judge a check by dagger check, never by dagger call <check>: on v1.0.0-beta.18, dagger call exits 0 when the check fails.