CI-CD Pipeline in Azure | Customization basics

CI-CD Pipeline in Azure

 After successfully configured CI/CD default pipeline in my last article
https://sharjeelswork.blogspot.com/2019/01/cicd-pipeline-for-dot-net-core-and.html

I am moving towards customization of CI/CD pipeline. Take the following steps to familiarize yourself with the Azure DevOps build and release pipelines.


l At the top of the DevOps Projects dashboard, select Build Pipelines. This link opens a browser tab and the Azure DevOps build pipeline for your new project.






l Select the ellipsis (...). This action opens a menu where you can start several activities such as queuing a new build, pausing a build, and editing the build pipeline.





l Select Edit.





Triggers
DevOps Projects automatically created a CI trigger, and every commit to the repository starts a new build. You can optionally choose to include or exclude branches from the CI process.






Retention
Depending on your scenario, you can specify policies to keep or remove a certain number of builds.





Releases
DevOps Projects creates a release pipeline to manage deployments to Azure.






On the left, select the ellipsis (...) next to your release pipeline, and then select Edit.
The release pipeline contains a pipeline, which defines the release process.

Under Artifacts, select Drop. The build pipeline you examined in the previous steps produces the output used for the artifact.





Next to the Drop icon, select the Continuous deployment trigger.
This release pipeline has an enabled CD trigger, which runs a deployment every time there is a new build artifact available. Optionally, you can disable the trigger so that your deployments require manual execution.





Tasks
The tasks are the activities that your deployment process performs. In this example, a task was created to deploy to Azure App Service.





On the right, select View releases. This view shows a history of releases.






Select the ellipsis (...) next to one of your releases, and then select Open.
There are several menus to explore, such as a release summary, associated work items, and tests.





Commits
This view shows code commits that are associated with the specific deployment.

Logs
The logs contain useful information about the deployment process. They can be viewed both during and after deployments.





These are the basics to modify CI-CD pipeline in Azure. In next article I will share more information in detail for customizing CD process.


Happy Learning !!!


Comments

Post a Comment

Popular posts from this blog

Error : DependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: com.adobe.aem:uber-jar:jar:apis -> version 6.3.0 vs 6.4.0

Image
I got above error after adding dependency in Maven POM xml file placed under newly created AEM arch type and running command  mvn -PautoInstallPackage clean install . Error : DependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: com.adobe.aem:uber-jar:jar:apis -> version 6.3.0 vs 6.4.0 After google and gone through few article I got command ( mvn -PautoInstallPackage -Padobe-public clean install) . Once I run this command this issue with jar compatibility was resolved. Happy Learning!!!
Read more

ERROR Exception while handling event Sitecore.Eventing.Remote.PublishEndRemoteEventException: System.AggregateExceptionMessage: One or more exceptions occurred while processing the subscribers to the 'publish:end:remote'

I was getting below error while working with cache management on CM and CD server. Actually my code was working fine on CM server but I was not able to access or clear cache object on CD server because of wrong event selection.  PID[18108] Error       ManagedPoolThread #3 16:24:16 ERROR Exception while handling event Sitecore.Eventing.Remote.PublishEndRemoteEventException: System.AggregateExceptionMessage: One or more exceptions occurred while processing the subscribers to the 'publish:end:remote' event.Source: Sitecore.Kernelat Sitecore.Events.Event.EventSubscribers.RaiseEvent(String eventName, Object[] parameters, EventResult result)at Sitecore.Events.Event.RaiseEvent(String eventName, Object[] parameters)at Sitecore.Eventing.Subscription`1.Invoke(Object instance, EventContext context)at Sitecore.Eventing.EventProvider.RaiseEvent(Object event, Type eventType, EventContext context) Above error comes due to wrong event args access in CD server. T...
Read more

Error : Sorry, there was an error : unauthorized_client in Sitecore 9.1 login

Image
After adding a new binding from IIS on my sitecore 9.1 instance I was getting unauthorized client error while login with newly added binding URL. To fix this issue I added AllowedCorsOriginsGroup in xml file placed at File Name :  Sitecore.IdentityServer.Host.xml Location : C:\inetpub\wwwroot\9Dot1.identityserver\Config\production After adding field tag AllowedCorsOriginsGroup in  Sitecore.IdentityServer.Host.xml file I was able to login properly with newly added URL. Also you can fix this issue by placing a pipe operator beside of old AllowedCorsOriginsGroup as below. <AllowedCorsOriginsGroup1>http://9Dot1.sc | http://jss.9Dot1.sc</AllowedCorsOriginsGroup1 Happy Learning!!!
Read more