DeployFailed - Push Failed
Hi Scott.
Keep getting an error when I do a push:
DeployFailed - Push Failed.
When I do it via CLI I receive more informative errors so I can resolve them from there. Any ideas?
2019-06-18 14:39:21,414 [1860963] INFO - j.builder.ForceComSfdxDeployer - Push completed in 2 m 0 s 44 ms.
2019-06-18 14:39:21,414 [1860963] INFO - .IlluminatedCloudExceptionUtil - Pushed 0/1 components to DEV-LSX-RES in 2 m 0 s 44 ms with status 1.
2019-06-18 14:39:21,414 [1860963] INFO - .IlluminatedCloudExceptionUtil - Push details:
{
"successes": [],
"failures": [
"DeployFailed - Push failed."
],
"numSuccesses": 0,
"numFailures": 1
}
Comments (5)
-
reporter -
repo owner This seems to be a recent regression in the Salesforce CLI. I've just let the CLI team know about it. Basically when
force:source:push
fails now--at least in certain cases--the details are omitted for the JSON output. I purposefully introduced a syntax error into an Apex class and ran force:source:push without and with the--json
flag:$ sfdx force:source:push -u ebikes PROJECT PATH ERROR ─────────────────────────────────────────────────────────── ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── force-app\main\default\classes\ChangePasswordController.cls Invalid type: StringX (5:20) force-app\main\default\classes\ChangePasswordController.cls Method does not exist or incorrect signature: void changePassword(String, String, StringX) from the type System.Site (10:21) force-app\main\default\classes\ChangePasswordController.cls Invalid type: StringX (5:20) ERROR running force:source:push: Push failed.
$ sfdx force:source:push -u ebikes --json { "status": 1, "name": "DeployFailed", "message": "Push failed.", "exitCode": 1, "commandName": "SourcePushCommand", "stack": "DeployFailed: Push failed.\n at MetadataRegistry.initializeMetadataTypeInfos.then.catch.e (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.11.2-4a5bf6aa97\\node_modules\\salesforce-alm\\dist\\lib\\source\\sourceApiCommand.js:63:31)\n at tryCat cher (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.11.2-4a5bf6aa97\\node_modules\\salesforce-alm\\node_modules\\bluebird\\js\\release\\util.js:16:23)\n at Promise._settlePromiseFromHandler (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.11.2-4a5bf6aa97\\ node_modules\\salesforce-alm\\node_modules\\bluebird\\js\\release\\promise.js:510:31)\n at Promise._settlePromise (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.11.2-4a5bf6aa97\\node_modules\\salesforce-alm\\node_modules\\bluebird\\js\\release\\promise.js:56 7:18)\n at Promise._settlePromise0 (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.11.2-4a5bf6aa97\\node_modules\\salesforce-alm\\node_modules\\bluebird\\js\\release\\promise.js:612:10)\n at Promise._settlePromises (C:\\Users\\Scott\\AppData\\Local\\sfdx\\ client\\7.11.2-4a5bf6aa97\\node_modules\\salesforce-alm\\node_modules\\bluebird\\js\\release\\promise.js:687:18)\n at Async._drainQueue (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.11.2-4a5bf6aa97\\node_modules\\salesforce-alm\\node_modules\\bluebird\\js\\ release\\async.js:138:16)\n at Async._drainQueues (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.11.2-4a5bf6aa97\\node_modules\\salesforce-alm\\node_modules\\bluebird\\js\\release\\async.js:148:10)\n at Immediate.Async.drainQueues [as _onImmediate] (C:\\U sers\\Scott\\AppData\\Local\\sfdx\\client\\7.11.2-4a5bf6aa97\\node_modules\\salesforce-alm\\node_modules\\bluebird\\js\\release\\async.js:17:14)\n at runCallback (timers.js:705:18)\n at tryOnImmediate (timers.js:676:5)\n at processImmediate (timers.js:658: 5)", "warnings": [] }
As you can see, the standard output includes detailed error messages, but the JSON output only says "Push failed". Unfortunately there's nothing I can do about this in IC, but hopefully Salesforce will issue a quick patch for it.
-
repo owner - changed status to resolved
Resolving this as it's reproducible via just the CLI. Hopefully Salesforce will issue a fix for it quickly.
-
repo owner Oh, and the Illuminated Cloud window is added the first time an error is added to it, and that doesn't occur until the first time an error is reported that includes enough information to resolve to a local file. That's why you don't see it at first.
-
repo owner Issue
#1321was marked as a duplicate of this issue. - Log in to comment
Realised that the Illuminated Cloud tool window is missing. Not sure if the errors would appear in there but I’m having trouble finding out how to add it into the set of tabs. Does this from time to time for some reason.