Org to Org deployment does not work properly for Aura Components
2018-09-21 12:29:55,693 [193739177] DEBUG - er.ForceComMetadataApiDeployer - Adding files to the archive:
2018-09-21 12:29:55,693 [193739177] DEBUG - er.ForceComMetadataApiDeployer - svg.cmp
2018-09-21 12:29:55,693 [193739177] DEBUG - er.ForceComMetadataApiDeployer - svg.cmp-meta.xml
2018-09-21 12:29:55,693 [193739177] DEBUG - er.ForceComMetadataApiDeployer - svgHelper.js
2018-09-21 12:29:55,693 [193739177] DEBUG - er.ForceComMetadataApiDeployer - svgRenderer.js
2018-09-21 12:29:55,712 [193739196] DEBUG - er.ForceComMetadataApiDeployer - Using the following package.xml for deployment:
2018-09-21 12:29:55,712 [193739196] DEBUG - er.ForceComMetadataApiDeployer - <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
<types>
<members>*</members>
<name>AuraDefinitionBundle</name>
</types>
<version>43.0</version>
</Package>
When trying to deploy one helper js "svgHelper.js" , I selected that "js" and deployed it from IlluminatedCloud -> Deploy Modified Metadata. and selected my target org, now this is what I saw in logs. It tries to deploy the full bundle and not the only JS file which got changed.
Is this expected?
Shouldn't it deploy only the JS file, I know that it wont be possible via package.xml though, but that would be great if you can.
Comments (9)
-
repo owner -
reporter destination and source both are developer orgs, (Developer Edition).
-
repo owner Can you provide the full
idea.log
(or at least everything around this deployment)? That will clarify why IC is choosing the Metadata API over the Tooling API. -
reporter - attached idea.log
Starts from this line : 2018-09-21 12:29:55,693 [193739177] DEBUG - er.ForceComMetadataApiDeployer - svg.cmp
-
reporter I have attached the logs.
-
repo owner Thanks. Unfortunately that log doesn't show the full operation. I will need to see more of the log before that to see the logic IC applies to determine which deployment path to use. Please send me all logs from the full time span of the total operation. Thanks!
-
reporter I have reattached the logs.
-
reporter - attached idea.log
-
repo owner - changed status to resolved
Issue tracker grooming. If this is still an issue, please feel free to reopen, ideally with a concrete reproduction scenario.
- Log in to comment
What type of org is the destination? If it's production, by default IC will only use the Metadata API when deploying. You would see a debug message to this effect a little higher in the log where IC determines which API to use when deploying.