Testing the Pipeline
Checking the endpoint
Finally, let’s check if the application is running.
Go back to the EC2 console and then click on Load balancer.
Select the load balancer awsbuilders-alb and copy the DNS name.
Open your browser and try to access the URL copied from the ALB.
Congratulations, the page below confirms that your .NET application is now containerized!
New Commit
Github is your code repository and any changes made to the master branch of the repository will trigger your CodePipeline to redeploy your application. The steps below will change an html file to trigger the pipeline that will automatically redeploy your application.
For a real environment, we recommend that you use pull requests to review changes before merging into the base branch.
Click here to learn about pull-requests.
Before we start, ensure that your terminal is pointing to the right folder.
cd ~/environment/demo-containerise-dotnet/aspnetapp/Pages
Open the Index.cshtml that contains the html used to generate the webpage above.
nano Index.cshtml
Add the html <br><h2>That is my update.</h2><br> below the Welcome to .NET Core line in the Index.cshtml file.
<br><h2>That is my update.</h2><br>
Save the file by pressing
1. CONTROL + X
2. Y
3. Enter
Add the html change to the git staging area.
git add *
Record the changes to the repository, so we can push to the server.
git commit -m "New Index file"
Push all committed changes to the server.
git push origin master
Open the CodePipeline and click on awsbuilders-codepipeline.
Wait the pipeline to deploy your application.
The process may take up to 15 minutes to go from Source to Deploy.
Get back to your application and refresh the page to see the change That is my update.
Click here to learn about CodePipeline notifications.