MSBuild projects are not instrumented under Jenkins
Last edited on
This problem occurs when a project has build without problems under a
user account, but the compilation fails when it is run under Jenkins
CI. It manifests in compiler errors like this one:
Here MSBuild has called the compiler directly, instead of calling
the wrapper, and the compiler did not understand the CoverageScanner
options.
To correct this, it is necessary to set the environment variable
LOCALAPPDATA at the beginning of the Jenkins build script. Its value
must be the path to the AppData directory of another user, i.e.
something like C:\Users\SomeUser\AppData\Local. The build script will
then look like this:
We would like to use Google Analytics to get a better understanding of how
you use the website.
By agreeing to this, your usage data will be stored in the USA and processed
by Google LLC. Both Google as well as federal US agencies can access this data
and combine it with any other data about you, such as your search history,
personal accounts or any other data known to Google.