Continuous Integration using Azure Build Pipelines (Part 4- Azure Function CI/CD)

 1.      Clone Repository –

Login to Azure Devops, open Project, go to Repos and click on “Clone”

Note – Here we are using the repository already created in the previous post

Pop up appears, select Visual Studio in IDE and it will auto redirect to visual studio proctor and opens Visual Studio where you can provide the local repo path and proceed with clone action.

2. Verify Repository Connection

After we clone the repository, we can see project connected to Azure Devops Git Repo under Team Explorer.

3. Add new Function App to the solution

Go to Add new Project, enter name of the project, select location and click “Ok”

4.      Check-in to Repo 

Once we create new project, we can see following files. Put comment and click “Commit All and sync”

Because of last step, following files pushed to remote master branch of the repository.

As we had configured Build Pipeline to trigger on master branch check-in, it will automatically trigger our Build Pipeline. To verify lets navigate to Pipelines from left menu and we see pipeline run is in progress.

Refer [Setup CI using Build Pipelines for Azure Function]

Click on the Pipeline to see the details, here we can see our last commit to the repository which triggered this pipeline.

To see further details, click on the commit record, here we can find details like

• Repository
• Branch
• Start Time
• Time Elapsed
• Published Files – This is the Azure Function Zip File published to drop location.

To see further details, click on Agent Job, here we can find each step performed by the Agent.

Once all the steps executed successfully, we get a link to artifact, which contains our Function App in a zip format.

Note - Name of the file is 2.zip because we configured the Name using build Id and we initiated second build. You can give any name of your choice with unique build identifier.

With this, we completed Continuous Integration using Build Pipelines, in the next post we will see about Continuous Deployment using Release Pipelines. Lets move to Step 5.

Happy Learning, LET'S SHARE !