'Classic pipeline' And Testing for Web Application

Step 1: Create New Project

• prj-web-classic-pipeline-devOps

Step 2: Create Repo, Branch and Push Web Application

Step 3: Activate Classic Pipeline
 

Step 4: Create Classic Pipe Line-  inside above project
Pipeline > Create Pipeline
Click last link ‘Use the classic editor to create a pipeline without YAML.’

Pipeline ‘’Azure Repo Git' Settings

• Core Settings
  • 
    • Project Name
    • Repository Name
    • Branch Name on which pipe line will be created
  • Click Continue

Pipeline ‘’Template' Settings

• Choose Template of web application, going to deploy this pipeline
  • 

Pipeline Agent Pool Information

Next Give Pipeline related information

• 
  • Pipeline Name (We can change this)
  • Our Agent Pool (using MS Azure Pipe line)
  • Agent Specification - OS of VM used by above agent
  • Path to solution
  • Artifact directory name

NuGet tool installer TAB

• Change Nuget to 6.0
  • 

NuGet restore TAB

• NuGet restore command- basically restores. So in the restoration process what it does, it will go to the public library, get those public library and download that to on my agent pool. And once those files are available it will it will let it will help my build to run.

Build TAB

• Build - So the build tool what we use for dotnet related application it is vs build. That's what Visual Studio build or Ms. build. These are the two build tools which you can use for running ASP.Net build.
  • 
  • Package given in MSBuid string
    • Once these arguments are basically deploy on build web publish method a package. This is this line will create a package a zip file for you okay. So all your application will be built compiled restored and a package will be created.
    • The package will be a deployable package wherein you can deploy that to a VM to a web app. 

Test Assemblies TAB

• Remove “Test Assemblies" & Publish symbol path

Public Artifact TAB

• 
  • The artifact will be copied to drop.  And drop is the folder we will have access to. My release pipeline will have access to this drop folder.

Save and Run Pipeline

• Click save & Queue
  • 

Manually Run Pipeline

• Then click RUN

Result

• run successfully 
  • 

Artifact is created at location

From above  path, Artifact is uploaded at following location

you can check your artifact and drop location from 

Check drop location

What we can do with Artifact

• Now I can download this zip file.
• Or I can create a release pipeline from where I can release this, deploy this application onto a VM
• or onto a web app wherever you want.