| << Back to previous view |
|
[QB-3363] Container path not considered in MSBuild step
|
|
| Status: | Closed |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 9.0.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Martin Falkner | Assigned To: | Steve Luo |
| Resolution: | Won't Fix | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Environment: | Windows 7 64-bit on VM | ||
| Description |
|
I'm using Bullseye coverage report within QuickBuild.
To avoid any accidental influence on other builds, I set up the computer environment NOT to include the Bullseye path and COVFILE environment variable. When using Bullseye build, I add the path to Bullseye executable and COVFILE environment variable to the Master Steps Environment Variables: Path = ${node.getAttribute("ProgramFiles(x86)").toString()}\BullseyeCoverage\bin;${node.getAttribute("Path").toString()} COVFILE = ${vars.get("WorkingFolder")}\DailyBuild\Coverage.cov as required by Bullseye. If I understand it correctly, this definitions will be used to call any script or MSBuild. This path and variable is available in most of the steps, but somehow seems not to be considered in Build > MSBuild. I'm not able to check/verify this, as I do not know how, but Bullseye report is not produced (COV file is not created) in this setup. In case the Path and COVFILE is defined on the computer level, it works. I also tried to set the Environment Variable in the MSBuild step itself, but it did not help. |
| Comments |
| Comment by Martin Falkner [ 11/Mar/19 12:41 PM ] |
| Please close this case, it turned out that I tested with VS2005 first when it worked. The tests with the problems were done with VS2017, therefore the problem is not within QB but Bullseye setup. |