-
Notifications
You must be signed in to change notification settings - Fork 99
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
SCANDOCKER-27 Move sonar.working.directory outside of the project basedir #249
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
We have tested together. With the change, we could mount the user's folder and execute analysis without the scanner-cli user having write access to the user-mounted folder.
cd851c3
to
d70d9bb
Compare
|
Hi, we are getting the following error, which seems to be due to this change:
Feel free to let me know if you need any other info. |
The error you get is not about the working directory, but the cache directory. It has been discussed on our community forum. If you don't find the solution in the thread, please add (in the forum) some details about your use case:
|
Hi, We are having the same issue after the update. We are using Gitlab runners. On the latest version, the pipeline fails to create cache files.
Down grading form lastest to 5.0.1 seems to resolve the error.
We made no changes between updates, and only changing version number from "latest" to "5.0.1" resolved the issue. If this is a config error from our side, could you please explain what needs to be changed so we can resolve the issues. Thanks in advance |
Thank you @henryju. FYI, we use Buildkite for CI. We don't map
As @Paul-Zensoftware mentioned above, the error started a few days ago with no changes on our end, apart from using the |
@vladimirjaric I think the issue is coming from:
It was okay before because our image relied only on the root account. In the latest release, we changed to having a non-root user run the analysis. I can't find a lot of documentation on this parameter, but what happen if you remove it? |
Please see the explanation in the forum. Basically, you have to clear the pipeline cache, since files cached by the previous version of the image cannot be read (due to the use of a non-root user for security reasons). |
Hi, Thank you for the quick response! Clearing the build cache resolved the issues I was having. I should have tried running without cache before asking for help. Again, Thank you for the quick response and help resolving the issue! |
Many thanks @henryju. Removing |
No description provided.