How are you getting the run id and what version of bsa ?
BSA version 8.2.01
Commands run are
blcli_execute DeployJob getDBKeyByGroupAndName $JOB_GROUP $JOB_NAME
blcli_execute DeployJobRun findLastRunIdByJobKey $JOB_KEY
blcli_execute Utility exportDeployRun $JOB_GROUP $JOB_NAME $RUN_ID "c:\joblog.csv"
A slight amendment to the original description of the issue.
It looks like WARNING messages that are output by the rscd agent are exported to the file.
The package that is being deployed is executing a shell script (which in turn executes some other commands), and the console output of the shell script/those commands is picked up by the agent and displayed in the Bladelogic Console as WARNINGS in the Commit results. It is these WARNING log entries that are not being exported to csv
can you show a screenshot of the warning messages in the gui ?
We're on version 8.2.01.273
In your screenshot that output generated looks like its by an echo directly in an external command?
The only difference i can see is that we're running a .sh script from the external command, and its the output from the sh script that is being logged as warning messages and not exporting. I wouldn't have though this should be treated any differently from your example though?
I'll try replicating your example next week
I’m not sure – I just did a loop where I redirected stdout to stderr from my echo. I’ll try your thing and see.