05 Apr 2023 10:24 AM - last edited on 06 Apr 2023 12:05 AM by MaciejNeumann
Monaco seems to send execution results to the stderror stream. It causes a problem when executing the pipeline.
##[error]Bash wrote one or more lines to the standard error stream.
##[error]2023/04/05 16:07:00 INFO Projects to be deployed:
2023/04/05 16:07:00 INFO - test
2023/04/05 16:07:00 INFO Environments to deploy to:
2023/04/05 16:07:00 INFO - env
2023/04/05 16:07:00 INFO Deploying configurations to environment `env`...
##[error]2023/04/05 16:07:00 INFO Deploying config global:builtin:management-zones:mz1
##[error]2023/04/05 16:07:00 INFO Deployment finished without errors
Indeed, logs are directed to the std::err stream.
Moncao is built using the Go programming language, and the default behavior of the standard Go library for logging is to print logs to std::err. It is quite common for CLI tools to use std:err for printing diagnostic output such as log messages, while std::out is typically used for regular program output.
May I ask you what kind of CI tooling you are currently using? Please also check the way you are handling error/exit codes in your CI script(s). If an actual error happens, Monaco will exit with a non-zero exit code which is picked up by common CI tools as a failure.