-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need explanation for "Base dir" with MSBuild Runner. #59
Comments
When you have several VCS roots in one configuration then they all are checked out to one directory according to checkout rules. Then by default all steps are executed in this shared checkout directory. Most of the runners have If you need to access the directory from the script it's better to avoid using relative paths ( But for report files I can recommend you using another directory - there's a temporary directory accessible by parameter In the same way you can pass this report to other runners (eg to the SonarQube Runner). Your first step can generate a report in some well-known location ( |
I've tried to using teamcity parameters already. But it's unsuccessful because it's not work with dependency-check plugin or may be with any sonarqube plugin at general. I will use '..\' for now. |
Could you describe how did you specify this path? In TeamCity UI or in some scripts? |
Update.. Report files was placed by script. |
Upd: At first I'd created build pipeline and got this:
Then I added unit tests steps, and suddenly Base dir was changed!
|
You cannot use TeamCity parameters ( If you want to use SonarQube UI to configure analysis then perhaps relative paths are a good chose. |
Hi. Some plugins for SonarCube works with previously prepared reports.
'SonarQube Runner' step doesn't define any base directory in its output. And we can put reports to root of working dir and set this value in plugin configuration.
Unlike this 'msbuild runner' steps define base dir accodingly to VSC checkout rules and we got dependence on checkout rules for plugin configs.
[09:45:12][Step 6/9] INFO: Base dir: C:\TeamCity\buildAgent\work\c740ee6f41af4f14\MonitoringService2
If it has only one repo it's not a problem, we can set config like '..\dependency-check-report.html'.
But what a behavior do we can expect if we have few git repos in build?
How is base dir defining?
The text was updated successfully, but these errors were encountered: