-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
dotnet publish fails with MSB3030 #10598
Comments
@nguerrera can you help here |
If possible, can you provide a binary log. Make note that this shares environment variables and project file contents before sharing. |
Here you go. |
I applied the 3.1.102 update yesterday to my Jenkins slave. Now I am hitting this issue again:
By rebuilding the slave EC2 instance from scratch (with the current dotnet version), everything works fine. I hope we can identify the source of the problem and correct it before the next dotnet sdk update... @nguerrera, did the binary log give you any insight into the cause of the problem? |
I have the same issue. Just note, the (Sorry, I'm from my phone now) |
I'm here cause I'm experiencing a similar error on my CI/CD pipelines |
I have the same problem. |
Same issue here too. |
This seems to be related to long path names... It occurred for me too on a path with 262 character. If I shorten it to stay below 260, the error is gone... |
Same problem here. I upgraded project from .netcore 2.2 to .netcore 3.1 and this occurs regularly. |
dotnet publish fails with MSB3030
We have been using the dotnet core sdk on Amazon Linux 2 for our Jenkins builds for 6 months now. We upgraded from dotnet core 2.2 to dotnet core 3.1 recently and everything has been working fine. For some unknown reason, all of our builds that use dotnet publish started failing today with an error that looks like the one shown here:
As you will notice, the publish command is internally trying to copy the file "data-sync-service", which doesn't exist. The "data-sync-service" name is the name of the project, so the source directory is full of files that start with "data-sync-service":
We are using the following command being executed by Jenkins:
I compared the CurrentVersions.target file with those on other machines and they are identical. The same builds work fine on other machines but are failing on our Jenkins slave.
General
dotnet core sdk version: 3.1.101
OS: Amazon Linux 2 (4.14.133-113.112.amzn2.x86_64 dotnet/core#1 SMP Tue Jul 30 18:29:50 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux)
The text was updated successfully, but these errors were encountered: