Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Introduction to Buildmaster
-
As my introduction to Buildmaster I want to publish an ASP.NET solution to azurewebsites.net. This is a trivial use of your product but a good learning experience. All I want to do is have Buildmaster mimic the three steps I normally do manually:
- Build the Visual Studio project, 2) test by viewing the web page, 3) Publish to azurewebsites
Here is my build script:
#Compile Project { DotNet::Build E:\VS\Resume\Resume\Resume\Resume.csproj; } # Run Tests { Perform-ManualOperation ( AssignedTo: Jim, Name: View the Web Page ); } # Capture Artifact { DotNet::Publish E:\VS\Resume\Resume\Resume\bin\Release\net6.0 ( SelfContained: false, DotNetPath: E:\VS\Resume\Resume\Resume\bin\Release\net6.0 ); }
The build results in this message:
Error: Pipeline stage "Build" target #0 does not specify a target, and cannot be executed.FIRST QUESTION:
What should target #0 be? (Deployment Target currently says 'Build to localhost', is that what target #0 refers to?)SECOND QUESTION:
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?(The web page is currently published at https://resumejimthomas.azurewebsites.net.)THIRD QUESTION:
Your web site says "Documentation Renovation in Progress" and "This [video] tutorial should not be followed if you're using BuildMaster 2022" and "Application Templates are Deprecated". While those comments say to contact you for assistance I would like to be more self-sufficient. Which, if any, of the documentation can I rely on for help?
-
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 todotnet 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 todotnet publish
, using theAdditionalArguments
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.