Hi - +1

I thought I was the only one having this problem. I too encountered some very long build times in the near past (up to 10 minutes). When I check in Salesforce during waiting for the build to finish, I can see that the changes have already arrived. It seems to be a local issue while processing the response or updating the local git repository. I can say that I have a comparably large project with ~50 complex apex classes and a lot of Aura bundles.

Regards, Joachim

Hi guys,

Thank you for contacting us on this.

In general, currently, the build process consists of 2 steps in the IDE: 

the IDE sends your changes to your Salesforce organization and then retrieves back an information about these updates from an org (hash sum of files, date&time of the last change, etc.).

The process of updating files itself is pretty fast, however, getting the response from the organization can take some time. 

So, since your updates are already present in your organization, we can see that a long time for a building process is caused by getting a response from the org about applied changes. Until the IDE doesn't get this response, the build process is in progress.

At the same time, I'm happy to let you know that we have worked on this approach and have made the necessary changes to avoid this issue that you are faced with, and we are going to release this changes in the next TWS version.

Also, you can find more details about the upcoming changes related to the build functionality here. I hope you would like them.

Best Regards,

Kate

Curious, when will the next release with the fix occur? I am losing development time waiting for a build to save, even when I do something as small as uncomment some code.

Hi Derrick,

Thank you for your question.

We are going to release this next TWS version (with the necessary changes to handle such case) already the next week. 

Regards,

Kate