sfdx force:mdapi:deploy deployments not starting, exiting with no exit code #1802
Comments
|
Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support. |
|
I've seen reports of 2 people with something similar. Thanks for the tip about the metadata type, that helps a LOT! Also, they both had a --checkonly flag. Is the behavior the same without that? |
|
Error while creating work item! |
All attempts were with the check only flag but I've tested and fails without the flag too. |
|
Can you look at some of the sample metadata that we use for testing and see if there's anything obviously different between it and yours?
We use this repo https://github.com/mshanemc/nestedFolders |
|
I've cut the package right down to one email-meta.xml file and still get the error. The difference between mine and yours is that mine has an attachment. If I remove the attachments tag it works. The file size of the example I've been playing around with is 4MB, that's a lot for an XML file - wonder if it's causing issues. Or perhaps there is something wrong with the content line, note the syntax highlighting: |
mshanemc
added
bug
|
Error while creating work item! |
|
I've got a replication! Thanks for the help about file size. Next up, figuring out what's causing it and how to fix |
|
@W-12050345@ |
|
Thanks for the updates! |
from the CLI team
there's a fix for this coming in the next release. Workarounds:
force:source:deploy. Years ago, you used to have tosource:convertfiles to mdapi format, and thenmdapi:deploythat. Some people never changed their ways when that option came out since CI was working fine. It definitely does save you some time!original issue below ⬇️
Summary
Since version 7.176.1 we have builds failing across multiple projects. When running the
sfdx force:mdapi:deploycommand there is no output, the deployment doesn't start and there is no exit code.We've reverted our build infrastructure back to 7.175.0 and builds are back up and running.
I've investigated further and found the issue comes and goes depending on package contents. I started with our full package and deleted metadata types until the error went away. The folder causing the issue is email - delete the folder the error goes away, restore it the error comes back. The exact same package contents works fine on the previous SFDX version.
Have there been changes in the latest version that would cause this?
There have been similar issues to this one in the past where commands fail but there is no output and no exit code - this is quite dangerous as build automation continues as it thinks the deployment has been successful. Luckily, our build calls out for a build status report to check coverage and that failed but if it didn't, the build would have proceeded to run scripts, etc against the environment.
Debug logs as follows:
The text was updated successfully, but these errors were encountered: