Hi @jimthomas1_7698 ,
What should target #0 be? (Deployment Target currently says 'Build to localhost', is that what target #0 refers to?)
This message could definitely be clarified; but it basically means that Deployment Target isn't set for the first stage. If you see "Build to localhost" on the pipeline overview page, I'm guessing you didn't "Commit" the changes (save) -- it's at the top of the page. You have to explicitly save the pipeline that you're editing.
Where in the Publish command do I specify the Resource Group, Resource Name and Subscription? Or will BuildMaster pull those azurewebsite publish parameters from the project's Properties/PublishProfiles .pubxml file?
I'm not familiar enough with azurewebsite publish to be honest... but under the hood, the DotNet::Publish operation calls to dotnet publish. So if your project is configured to use the PublishProfiles... then maybe it will work?
You can pass additional arguments into DotNet::Publish (which will get directly passed to dotnet publish, using the AdditionalArguments parameter)
FYI: Deploying to Azure Websites is a Deployment Script Template we intend to create later. It's unfortunately a little complicated to do, since it primarily reles on a
Which, if any, of the documentation can I rely on for help?
We put that "Documentation Renovation in Progress" warning on the pages that are outdated; there's not too many of them with that warning... and we're making our way through them one page at a time
In any case, don't hesitate to ask questions - it is often an opportunity for us to improve our software or documentation.
