We are trying to run dotnet publish on our integration-test project to run artifact on other "machine", but get no output #6748
Unanswered
ThomasCronholm
asked this question in
Q&A
Replies: 1 comment
-
Does #1819 answer your question? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We have a scenario where we want to build a integration-test project and then move it to the "machine" where the tests should run
The issue we are seeing is that if we build and try
dotnet publish integration-test-project-path --no-build -c Release /p:Version=0.2.0-init-repo0021 -v m
we get no publish output.If we build and try
-> copy the build output to folder
-> zip the folder
-> upload it to build artifacts
-> download and extract it on the test-machine and run our tests
We get
System.IO.DirectoryNotFoundException : E:\home\vsts\work\1\s\Source\OurApplication.AppHost\
when we have/TestAdapterPath:"E:\AzureAgents\nameofmachine_192.168.0.0.1.1\_work\52\s
.We have seen that a reference to the aspire AppHost project disallows the publish.
The question is how can we accomplish this?
Beta Was this translation helpful? Give feedback.
All reactions