I am currently trying to figure out how to register the unit tests, run by a Finalbuilder script, at the Continua build.
The easiest solution for me was to pass the workspace path down to the Finalbuilder script and make it copy the .trx files to the workspace. After the Finalbuilder script has finished, the tests are being registered by the Import MSTest action.
This solution works great so far. But in order to implement it with all our projects, we would need to adjust every configuration in Continua which is less than ideal.
I read about the latest changes in version 184.108.40.2062, installed it right away and tried to assemble the command to import the test results with the help of custom log messages.
But Continua does not seem to care about the log message. Do I have to use a special Action inside Finalbuilder to actually make use of this feature?
Usually it does note that the import is successful, or if there were some errors, it would log that too. I feel like Continua simply does not register the command.
How des the Custom Log Message work? Will it execute after the Finalbuilder Script has finished? Or does it execute in the meantime.
Right now, the Finalbuilder Script is configured to run in a temporary directory which gets deleted when the build process itself has completed.
In your build log, it shows the
type parameter for your custom log message as
'msbuild'. This is not a supported type. In your case this should be
Note also, that we would recommend locating your test result files within the build workspace so that you don’t get conflicts if running more than one build concurrently.
Hey thanks for your quick response!
Damn a typo… Well now that its fixed, the tests still wont get registered. I tried running the command right after each test library with the exact filename. Still no unit tests registered inside the build. Any clue what could be the error?
@@continua[importUnitTestResults type='mstest' filePatterns='C:\Temp\fbbuild\license_hive\132\WC\CES.LicenseHive.Core.Tests\TestResults\maintadmin_CI01_2022-03-29_08_34_54.trx' failIfTestFails='false' failIfTestErrors='false' quiet='false' verbose='false']
Yes, I’ve wanted to move all the builds inside the workspace for a long time now. But it would require me to modify all the Finalbuilder Scripts for all our projects which is quite scary for now :S
Additionally, the way the builds run right now usually don’t produce any conflicts. We are generating a directory for each run with the revision number.
Can you try setting the
verbose parameter to ‘true’ and then post the build log output?
I attached the build log as requested. I cut out some parts and added comments in these places.
build log.txt (8.7 KB)
One additional note: When using Finalbuilders Action dotnet Test, I can not set the logger field without the program writing the same value into the Configuration field after clicking OK. When I open the dialog again, the value is set in both fields which is not ideal. Thats why im calling the dotnet command manually.
Same goes for the Publish command. Maybe updating to the newest version will help. I’m currently running 220.127.116.1140.
What FinalBuilder action are you using to send the log message. You can’t use the “Continua CI - Log Message” action as this is specifically for logging the message verbatim. e.g. it outputs a
@@continua[message value='...'] message to Continua CI.
We don’t yet have a FinalBuilder action specifically for sending any custom log messages but we plan to add this for the next version. Meanwhile your best bet is to choose a scripting or batch execution action with a command that outputs text. You can, for example, enter an
echo command as the Command for a Run DOS Command / Batch File action.
I can confirm that the issue with the Dotnet Test action exists in the latest version - we’ll look into that further tomorrow. The Dotnet Publish action does not have a Logger - maybe it’s happening with another field?
This was the action I was using. I switched as you recommended and now it works as expected - nice
I’ll create a new Post in the Finalbuilder / Bugs Topic for the bugs I have encountered for the dotnet Finalbuilder Action.