Disable auto-deploy in the backgroung

[Vishal Shah]

Is there a way to enable a Manual deploy option only? i.e. I do not want Illuminated Cloud to automatically deploy my local files on each save. 

[Scott]

Hi, Vishal.  You can absolutely disable deploy-on-save behavior.  Go into Settings>Illuminated Cloud>Validation and Deployment and all of the event handlers to Do Nothing.  Please let me know if this doesn't give you the behavior you're wanting.

Regards,

Scott

[Vishal Shah]

I'm trying to access this in IntelliJ on Mac. I do not have access to Validation and Deployment. I'm looking at Preferences. 

Clearly, I'm missing it. 

[Scott]

No problem, Vishal.  Here's a screenshot of the configuration on my Mac:

I went into IntelliJ IDEA>Preferences (Cmd+,) and then into Languages & Frameworks>Illuminated Cloud, and finally selected the Validation and Deployment tab.  Please let me know if you're not finding it there.

Regards,

Scott

[Vishal Shah]

Thanks. 

[Bob H.]

Hi Scott, to bring up this old thread, is it possible to block deployment on save by project?

I want deploy on save for my development projects, but don't want it on the project I have set up that points to production, which I use to review production code and use the SOQL editor. Or is it safer to just not have a production project?

[sc...@illuminatedcloud.com]

Bob, this setting is currently at the application-level and not the project-level. There's an open enhancement request to allow you to specify some connections as "sacred" which would mean that making changes against those connections would be MUCH more difficult. Things like deploy-on-save would not be available against those connections, and things like bulk deploy/delete, anonymous Apex execution, etc., would require explicit user confirmation. I'm planning to address that pretty soon in a metadata deployment/retrieval improvement-themed release. Until then if you're nervous about accidentally doing something to production, I'd recommend either not having that as a configured connection or perhaps "neutering" it by changing the username slightly to ensure that login fails until/unless you want to use that connection explicitly. That certainly falls under the category of "heinous workaround", but there's a real improvement in this area coming soon.

Regards,

Scott

[bob.h...@gmail.com]

Thank you for the quick reply.

What I did was to implement a background so that when I am in my production project the background is red. It's purposefully "heinous".

https://www.jetbrains.com/help/idea/2016.2/setting-background-image.html

I think this will do for now.

Thanks again!