The Wercker can not run the build azk due to the prompt that asks if you want to start the agent (azk agent start). The question occurs whenever the need to run something that depends on the agent.
cd $WERCKER_SOURCE_DIR
$ export WERCKER_STEP_ROOT="/wercker/steps/wercker/script/0.0.0"
$ export WERCKER_STEP_ID="fbbd30ec-e048-46cc-a142-7599dcf54a21"
$ export WERCKER_STEP_NAME="script"
$ export WERCKER_REPORT_NUMBERS_FILE="$WERCKER_REPORT_DIR/$WERCKER_STEP_ID/numbers.ini"
$ export WERCKER_REPORT_MESSAGE_FILE="$WERCKER_REPORT_DIR/$WERCKER_STEP_ID/message.txt"
$ export WERCKER_REPORT_ARTIFACTS_DIR="$WERCKER_REPORT_DIR/$WERCKER_STEP_ID/artifacts"
$ mkdir -p $WERCKER_REPORT_ARTIFACTS_DIR
$ export WERCKER_STEP_TEMP="/tmp/$WERCKER_STEP_ID"
$ source '/wercker/wercker-build-essentials/init.sh'
$ mkdir -p $WERCKER_STEP_TEMP
$ until bin/azk status; do sleep 1; done
? The agent is not running, would you like to start it now? (Y/n)
Your script doesn't seem to be responding for 5 minutes. Please update and run again.
I propose adding the --quiet option to commands azk (globally) that will define the command as non-interactive.
ex:
Turning the option --quiet the azk not asks whether to start the agent.
gullitmiranda
commented
9 years ago
The Wercker can not run the build azk due to the prompt that asks if you want to start the agent (
azk agent start). The question occurs whenever the need to run something that depends on the agent.I propose adding the
--quietoption to commands azk (globally) that will define the command as non-interactive.ex: Turning the option --quiet the azk not asks whether to start the agent.