Deployment fails, no error message

[Jeremy Ross]

I'm trying to deploy a single class to a production org. This is in the event log:

Deployment Complete: Deployed 0/0 components to Production in 5s 918ms with status FAILED.

This is in idea.log:

2016-08-25 22:05:13,534 [2614854]   WARN - ConfigurableExtensionPointUtil - ignore deprecated groupId: editor for id: editor.preferences.import 

2016-08-25 22:06:00,879 [2662199]   INFO - der.ForceComToolingApiDeployer - Starting deployment with a polling interval of 5000 milliseconds. 

2016-08-25 22:06:06,480 [2667800]   WARN - der.ForceComToolingApiDeployer - No component successes or failures found in deployment result. Processing based on request state. 

The deployment doesn't show up at all in setup > deploy > deploy status. 

Any ideas why this is failing?

[Scott]

You can add these to Help>Debug Log Settings to get debug logging for the deployment:

#com.illuminatedcloud.intellij.builder.ForceComBuilder

#com.illuminatedcloud.intellij.builder.ForceComToolingApiDeployer

I think the reason it's not showing up in deploy status is that it's being deployed using the tooling API vs. the metadata API.  Let's see what the more verbose logs say.

[Jeremy Ross]

Doesn't seem too helpful:

2016-08-25 22:19:57,722 [ 511778]  DEBUG - der.ForceComToolingApiDeployer - Found one. Deleting it. 

2016-08-25 22:19:57,961 [ 512017]  DEBUG - der.ForceComToolingApiDeployer - Creating a new metadata container with name IC-Production 

2016-08-25 22:19:58,148 [ 512204]  DEBUG - der.ForceComToolingApiDeployer - Populating the metadata container. 

2016-08-25 22:19:58,149 [ 512205]  DEBUG - der.ForceComToolingApiDeployer -   Adding Apex class ApplicationManager 

2016-08-25 22:19:58,150 [ 512206]  DEBUG - der.ForceComToolingApiDeployer - Adding members to the metadata container. 

2016-08-25 22:19:58,504 [ 512560]  DEBUG - der.ForceComToolingApiDeployer - Creating a container async request for metadata container 1dc36000000AbL6AAK with checkOnly = false. 

2016-08-25 22:19:58,746 [ 512802]   INFO - der.ForceComToolingApiDeployer - Starting deployment with a polling interval of 5000 milliseconds. 

2016-08-25 22:19:58,746 [ 512802]  DEBUG - der.ForceComToolingApiDeployer - Polling the status of the ContainerAsyncRequest. 

2016-08-25 22:19:58,911 [ 512967]  DEBUG - der.ForceComToolingApiDeployer - ContainerAsyncRequest is still processing. Waiting 5000 milliseconds and trying again. 

2016-08-25 22:20:03,914 [ 517970]  DEBUG - der.ForceComToolingApiDeployer - Polling the status of the ContainerAsyncRequest. 

2016-08-25 22:20:04,331 [ 518387]  DEBUG - der.ForceComToolingApiDeployer - ContainerAsyncRequest is complete. 

2016-08-25 22:20:04,331 [ 518387]  DEBUG - der.ForceComToolingApiDeployer - Compiled all metadata container members in 5827 ms. 

2016-08-25 22:20:04,332 [ 518388]  DEBUG - der.ForceComToolingApiDeployer - ContainerAsyncRequest state = FAILED 

2016-08-25 22:20:04,332 [ 518388]  DEBUG - der.ForceComToolingApiDeployer - Processing deployment result. 

2016-08-25 22:20:04,332 [ 518388]   WARN - der.ForceComToolingApiDeployer - No component successes or failures found in deployment result. Processing based on request state. 

2016-08-25 22:20:04,332 [ 518388]  DEBUG - der.ForceComToolingApiDeployer -   Successfully deployed 0 components. 

[Scott]

Okay, that's actually helpful to me.  So the commit of the tooling API metadata container failed outright, not because there was a compile error or anything.  It looks like I'm not showing the actual container-level error.  I'll add that for the next build, but for the moment would you mind switching to the metadata API to deploy this file to see if it gives a more useful error?  I know the metadata API is running slowly for you now in some orgs, but hopefully that will yield more useful info.  I'll go ahead and make sure that the container-level error is reported properly as well.  Let me know what you find.

Oh, and if you're not sure how to switch to the metadata API, it's under Settings>Illuminated Cloud>Validation & Deployment.  Just uncheck Prefer Tooling API for>Apex.

Regards,

Scott

[Scott]

Also, if you want to live on the edge a bit, I'm creating a build right now that should properly report the container-level failure (I actually had a TODO in there for myself to do exactly that...sigh...).  I can post it for you to try out.  Aside from capturing this particular situation, it's the exact build I posted earlier today officially.  It should allow you to see the error while still using the faster tooling API for Apex.  Just let me know and I'll post it for you to download and install.

[Jeremy Ross]

The deployment succeeded with the metadata API. I switched it back to tooling api, made a minor change to the class file and tried again. Failed with the same info in the log. I'll keep it on metadata API for now. 

And yeah, I'll give the experimental build a shot. Thanks.

[Scott]

Okay.  I'll be curious to see what happens when you use the tooling API again with the test build.  The build is attached to this issue that I logged:

https://bitbucket.org/RoseSilverSoftware/illuminatedcloud/issues/377

and you can install it using Settings>Plugins>Install plugin from disk.  I'm going to be crashing for the evening soon since I have to get up early with the kids, but I'll take a look at any new information you can provide from the test build tomorrow.  Hopefully once we have better information the root cause will be obvious.

Regards,

Scott

[Scott]

FYI, I included a fix for this in 1.7.3.6.

Regards,

Scott

[Jeremy Ross]

I'm noticing now that if a sandbox tooling api deploy fails, instead of getting a fail message in the status bar, it's blank. The log shows this:

2016-09-02 10:16:45,353 [  42377]   INFO - der.ForceComToolingApiDeployer - Starting deployment with a polling interval of 1000 milliseconds. 

2016-09-02 10:16:46,550 [  43574]   WARN - der.ForceComToolingApiDeployer - No deployment result found. 

I'm guessing the reason it's failing is that there are tests currently running in the org, but that's probably beside the point.

[Scott]

Jeremy, are you on 1.7.3.6?  I added reporting of container-level failures in that build.  If not, do you mind upgrading and see if it still fails silently?  If so, do you mind enabling debug logging in that area so I can see what all is going on?  Same instructions as in the second post of this thread.

Thanks!

Scott