Anyone have experience with Azure Continuous Integration?
-
So I'm experimenting with Azure and CI, and I'm getting failing builds for things that build just fine locally.
The error message is:
Error : Assets file 'd:\a\1\s\CampaignCore\obj\project.assets.json' not found. Run a NuGet package restore to generate this file.
But I can't find any way of doing that through the TFS web portal.
The repo is a public GitHub repo, available here.
What do I need to do? Is there a switch I'm missing? It says it's doing a package restore before building, so is going wrong?
-
@benjamin-hall said in Anyone have experience with Azure Continuous Integration?:
TFS web portal
What version of TFS are you running, or did you mean Visual Studio Team Services?
Is this a Visual Studio 2017 project? Admittedly I don't have much experience with those kinds of project setup.
EDIT: Oh wait, Github. Seems it is a VS 2017 project.
-
@jbert said in Anyone have experience with Azure Continuous Integration?:
@benjamin-hall said in Anyone have experience with Azure Continuous Integration?:
TFS web portal
What version of TFS are you running, or did you mean Visual Studio Team Services?
Is this a Visual Studio 2017 project? Admittedly I don't have much experience with those kinds of project setup.
I'm doing it through the website, so whatever the azure portal links to.
Yes, it's VS2017 and .NET core 2.0. it locally builds fine, and manual deployment (pushing the deploy button in visual studio) works fine. Just the builds triggered by a commit don't work.
-
I'm afraid I won't be able to do much then, I'm not a fan of those Azure / Kudu scm-build-and-deploy things. Visual Studio Team Services makes things more predictable because it's a real cloud-hosted TFS, but then it might cost you when you run out of the free amount of build minutes (my employer pays for an enterprise account, so that's nice I guess).
A quick Google search seems to indicate that there are others having the same error while building.
Would it be an option to build locally, then creating an msdeploy package and deploying that?
-
So I'm making progress. Turns out you have to use completely different tasks for .NET Core than are setup by default. Now trying to get it to actually publish correctly. Bah. Uploading zip files is so much easier...