Deployment Error: 'ComponentName of type ComponentType was named in package.xml, but was not found in zipped directory'

When deploying a Git Promotion step, you may encounter the error below for one or several components: ‘ComponentName of type ComponentType was named in package.xml, but was not found in zipped directory.’

In order to understand where this error comes from, we need first to understand what would be the normal process to deploy metadata without using Copado. This is how you would deploy with Workbench or ANT Migration Tool.

  1. A package.xml file is created with a list of the components you want to deploy.
  2. Using that package.xml file, a retrieve is performed from the source organization.
  3. With the files retrieved from the source organization, a zip file is created. This .zip file contains the package.xml and the files retrieved from the source org.
  4. The .zip file with the components that were retrieved is deployed to the destination organization org.
The error above would be displayed when a component that was included in the package.xml file to be retrieved and deployed, was not found in the files to be deployed.

If the component is listed in the package.xml file, this component should have been retrieved and a file for the component should have been included in the zip file so, why a component that was included in the package.xml was not included in the zipped directory?

When working with Copado, the process of deploying a Git Promotion step is similar to the described above. The package.xml with the components is created from the selections in the deployment, which are usually the components committed in the user stories, and the files in the zipped directory are created from the promotion branch in Git.

If you are getting this error when deploying, make sure the component returning the error exists in the promotion branch in Git, since we are creating the files that are deployed out of the promotion branch. You might see the components included in the deployment selections in the Git Promotion step, but the components may not exist in the promotion branch created for that deployment. 

If the component doesn't exist in the promotion branch for that deployment, that explains the error you are getting. You can follow the article below to figure out the reason why the component doesn't exist in the promotion branch.

How to troubleshoot an incorrect Deployment

If the information in the article doesn't help you solve the issue, please log a case on the Success Community at https://success.copa.do and provide us with all the relevant information.


How did we do?