logo

Build actions troubleshooting

Find the message from your build log in the first column. Script errors of your own, such as a Python traceback, appear in full under the build action <hook> step; see Where the failure shows.

Messages and fixes

Build actions messages
You seeWhyDo this
build actions are not enabled for this projectThe commit has scripts in .dsl/build_actions/, but build actions are not turned on for the organization or the project. The build stops rather than ship without them.Email support@devstreamlabs.com to turn build actions on for your organization and project, or remove .dsl/build_actions/ from the branch.
build actions: noneNo script in the commit matched a hook name.Check the folder is .dsl/build_actions/ at the repository root and the file name is exactly a hook name. The log warns about near misses such as prebuild.py. See How scripts are named.
two scripts for hook pre_buildMore than one file claims the same hook, for example pre_build.py and pre_build.js.Keep one of pre_build.py / pre_build.js.
KeyError: 'MY_TOKEN'The script asked for a secret that is not set.Set it in Build Action Secrets for this branch, project or organization. See Secrets in build actions.
killed after 1800 s wall clockThe script ran past the 30-minute per-script limit.Split the work across hooks, or make the script faster.
pre_checkout is not supported for DiversionThe repository is a Diversion repository and the commit contains pre_checkout.Move that work to post_checkout.
BUILD ACTION COULD NOT RUN (platform fault)The problem is on our side, not in your script. We are alerted automatically.Retry the build. If it happens again, email support@devstreamlabs.com with the DSL_JOB_UUID from the log.

Still stuck? Email support@devstreamlabs.com with the DSL_BUILD_UUID and DSL_JOB_UUID from the build log. Problems with the build itself, outside your scripts, are covered in Build Stream troubleshooting.

Something out of date or unclear? Email support@devstreamlabs.com.