Hi Quickbuild support
There has been a weird bug I encountered and I couldn't figure out why it occurs.
It's a Windows agent, a physical laptop used for this project.
The steps are two batch steps:
- covxml (which is a bullseye coverage command line)
The thing is, if I use a standalone config to run these two steps only, the build will pass. But when I do the same in our production configuration, it reports weird outputs:
step 1 output doesn't show the same agent username, it shows "encrypted" values:
14:57:13,376 INFO - Running step... 14:57:13,400 INFO - 14:57:13,401 INFO - C:\buildagent\buildagent\workspace\root\Products\Our_Products\One_Product\per_check-in\trunk>whoami 14:57:13,413 INFO - ***** 14:57:13,416 INFO - Executing post-execute action...
Why does it output secret value?
And in step two it will report
14:57:14,286 INFO - Running step... 14:57:14,312 INFO - 14:57:14,312 INFO - C:\buildagent\buildagent\workspace\root\Products\Our_Products\One_Product\per_check-in\trunk>covxml -f test.cov -o cov_result.xml -q 14:57:14,318 WARN - 'covxml' is not recognized as an internal or external command, 14:57:14,318 WARN - operable program or batch file. 14:57:14,322 INFO - Executing post-execute action...
And the bullseye command line ARE in system PATH, it works with a standalone config.
About the production config setup, it starts off with a Linux agent, the step structure is about this:
-- Linux sequential starts (here it sets environment variables)
---- compile code on Linux
---- send file to a specific Windows agent
------ run the two steps
I made sure the steps ARE running on the correct Windows agent. Is it possible you could provide some insights based on my description?
I'm guessing the top level Linux environment variable setup has impacts on the child steps that are on Windows.