Presets run Bun lint, test or build commands. The repository must provide the scripts expected by the selected preset.
Technical type : ci_verify. Runtime : docker.
Credentials and prerequisites
This node defines no dedicated external credential. Remote sources or execution targets may still need their own access credentials.
See the credentials guide if a remote source or execution target requires access.
Parameters
Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.
Installs dependencies with bun install --frozen-lockfile, then runs bun run check, bun run test or bun run build. Use Custom for another script.
workingDir Working directory (relative)
Workspace subdirectory where commands run (e.g. apps/backend).
image Container image (shell)
Image containing the tools your commands need. Defaults: oven/bun:1 for Shell and Verify; node:22-bookworm for Release.
secretCredentialIds Secrets
Secrets connections injected as environment variables of the script (process.env, os.environ...). The file carrying them is deleted as soon as the container starts.
Initial configuration
Initial catalog configuration example, to adapt before running. Keep secrets in credentials.
Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.
Lint, test, or build presets (bun)
Usage and specifics
Presets run Bun lint, test or build commands. The repository must provide the scripts expected by the selected preset.
Technical type :
ci_verify. Runtime :docker.Credentials and prerequisites
This node defines no dedicated external credential. Remote sources or execution targets may still need their own access credentials.
See the credentials guide if a remote source or execution target requires access.
Parameters
Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.
presetenum"check"check,test,build,customcommandsarrayworkingDirstringimagestringsecretCredentialIdsarray[]secretFilesarray[]secretFiles[].pathstringsecretFiles[].contentstringworkspaceSourceunion{"kind":"upstream"}workspaceSource.kindliteral"upstream"upstream,nodeworkspaceSource.keystringexecutionTargetunion{"kind":"host"}executionTarget.kindliteral"host"host,remote_server,kube,swarmexecutionTarget.serverIdstringexecutionTarget.providerenumaws,gcp,scaleway,ovh,azure,digitalocean,hetznerexecutionTarget.clusterIdstringexecutionTarget.namespacestringConfiguration help
commandsCommands
presetPreset
workingDirWorking directory (relative)
imageContainer image (shell)
secretCredentialIdsSecrets
Initial configuration
Initial catalog configuration example, to adapt before running. Keep secrets in credentials.
{ "preset": "check", "workspaceSource": { "kind": "upstream" }, "executionTarget": { "kind": "host" } }Verification
Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.
See also : Expressions and data, Executions, Node catalog.