Skip to main content

Error: No package found with specified pattern: D:\a\r1\a\**\*.zip for Angular Azure DevOps pipeline release.

How to easily deploy the Angular app to Azure by configuring build and release pipelines in Azure DevOps

Create build pipeline definition

To create a build pipeline that will create the optimized version of the app. Start with creating a new build pipeline from Pipelines >> Build on your team project in the browser.

In this pipeline, you will add following tasks:

Once this build pipeline is defined, you can queue the build. The created artifact should contain a file named dest.zip which will be used to do the deployment.

Release & Deploy
To do the deployment of the app, we will create a Release Pipeline.

Under the Pipeline tab, select the build pipeline that you have created earlier as the artifact source to be deployed. Let the default version be the “Latest”.

Under the Tasks tab, Select your Azure Account and authorize Azure DevOps to access resources from that Azure account when prompted.

Now, select the task that is automatically added, named Deploy to Azure App Service. In the parameter Package or Folder, select the .ZIP file from the artifact. Ensure that File Transforms & Variable Substitution and App Settings section are empty.



Now we can create a release and proceed with the deployment.

Since I forgot to publish my artifacts on my pipeline build, got an error during my release execution that zip file could not found.


No package found with specified pattern: D:\a\r1\a\**\*.zip

After publish my artifacts, my release executed successfully.

Labels:

Comments

  1. UnknownNovember 23, 2019 at 6:11 AM

    Thanks a lot it worked for me :)

    ReplyDelete
  2. NethiJanuary 7, 2021 at 11:47 AM

    In my case, i am using the classic editor as it is my first time learning Devops. The publish artifact task was already added but I still see the error, "Container path not found". Can someone let me know what am i missing here?

    My release pipeline is looking for "D:\a\r1\a.." path whereas artifacts were copied to "D:\a\1\a.." in the build pipeline.

    ReplyDelete
  3. UnknownApril 21, 2022 at 11:23 PM

    Not use full

    ReplyDelete

Post a Comment

Popular posts from this blog

How to get SPUser or SPGroup from Person or Group field

You have person or group field in SharePoint list and you want to programmatically get the user or person. The below code to gets SPUser from User or Group field in the list when multiple choice and Groups are not allowed in the field: //get SPUser SPFieldUser userField = (SPFieldUser)item.Fields.GetField("Users"); SPFieldUserValue userFieldValue = (SPFieldUserValue)userField.GetFieldValue(item["Users"].ToString()); SPUser user = userFieldValue.User; This part of code would help you to get SPUser when multiple choice is allowed and groups are not allowed: //Multiple choices are allowed SPFieldUser userField = (SPFieldUser)item.Fields.GetField("Users"); SPFieldUserValueCollection userFieldValueCollection = (SPFieldUserValueCollection)userField.GetFieldValue(item["Users"].ToString()); foreach (SPFieldUserValue userFieldValue in userFieldValueCollection) {     Console.WriteLine("     " + userFieldValue.User.LoginName); } And when group
1 comment
Read more

SharePoint publishing page scheduling

In SharePoint 2010 publishing enabled team site collection is not showing schedule button in publish ribbon. Solution: Here is how to enable it  though the UI: Locate the SharePoint Server Web site on which you want to enable content approval and item scheduling. Click  Site Actions , click  Site Settings , and then click  Modify Pages Library Settings . Under  General Settings , click  Versioning Settings . Click  Yes  next to  Content Approval , and then click  OK . Click  Manage item scheduling .   Click to enable the  Enable scheduling of items in this list  check box, and then click  OK .
2 comments
Read more

Changing Content Type Hub URL

Change the Hub URL through powershell by using: Set-SPMetadataServiceApplication -Identity " " -HubURI " " For Ex: Set-SPMetadataServiceApplication -Identity "Managed Metadata Service" -HubURI "http://contenttype.Domain.Com" When you try to do this you get this rather scary message: This is SharePoint telling you that this is a major thing so be careful! Essentially all your content types that you have published out will be removed if they can, and you have to republish all of your content types out again which can cause some issue.
2 comments
Read more