Going to have to go back to Eclipse if Welkin doesn't immediately fix this:
Posted Dec 11, 2015
Posted Dec 14, 2015
We are sorry that you are experiencing this issue.
Our team will work on fixing this issue asap and we hope to get back to you with the fix within several days.
We will appreciate if you can reproduce this issue and send us a bug report with log.
In order to send a log you can navigate to "Report a Bug" from Main menu -> Help -> Report a Bug, write us a couple of words and ensure that "Attach Log file" checkbox is checked.
Head of Product
The Welkin Suite
skype id: vladimir.gubanovich
Posted Dec 25, 2015
I want to inform you that we have released the 0.25.3 version of The Welkin Suite.
The fix of the current issue is included to this version.
I kindly ask you to write us if this issue is reproduced for you.
Posted Jan 14, 2016
I am having the same issue on my project. If another person creates the project, puts it on git, and I pull and try to build it on my computer, the build fails with no errors. I can pull changes, but building fails every time unless I create the project myself. Is this due to the credentials being encrypted and shared? Updating the password does not fix the issue.
Posted Jan 15, 2016
Thank you for you describing your case.
Since you can pull this Project, the credentials are not the reason for your issue.
I kindly ask you to answer several questions:
Was this project built by your colleague before they put it to the Git repository?
Have you made any changes in this project in TWS locally before you pulled it from the Git repository?
Are there any files in the Pending changes panel?
Your answer will help us to understand the reason for this issue with failed built.
Posted Jan 19, 2016
Here is a more detailed explanation that should answer your questions:
- Person A pulls the project from Salesforce, builds it (successfully, with no errors), and puts it in the Git repository.
- Person B pulls the project from Git and opens it in Welkin Studio. There are no pending changes. Person B pulls from Salesforce to ensure that everything is current.
- In the "pending changes" folder, it shows many pending changes, but when attempting to compare or discard them, a window says that "file 'x' is already of this version".
- Person B attempts to build, and it fails with no errors.
Posted Jan 20, 2016
Thank you for these details.
I have added this issue to our Backlog.
Our team will investigate it in one of the nearest sprints.
May I please contact you for an additional information if it is necessary?
Posted Feb 5, 2016
Our team has found the reason for your issue with the failed Build after the pulling a project from a Git repository.
Some of the files can have Windows line-endings on Salesforce. At the same time, project files which are saved in a Git repository have Unix line-endings.
When you download or pull your project in TWS the IDE calculates the remote and local hashes for each file. After you open your project from a Git repository and then pull it from Salesforce, probably, all files are now changed due to the diffs of hashes. As a result, the Build process fails because the records limit is reached. This limit is 200 records.
Our team will work on finding the solution to the Build process failures related to this restriction.
Currently you can use the next workaround to continue your working process:
person A should open his .git/config file and specify the â€˜inputâ€™ value for the autocrlf property (add autocrlf=â€™inputâ€™) in the [Core] section, and only after this they can push all files into the Git repository;
person B should make sure that autocrlf property in their repository has â€˜inputâ€™ value too and only after this they can make the Git pull and get the project from the Git repository;
person B opens the project in TWS and can pull new changes from Salesforce.
After all these actions to avoid the same issue for person A you and your colleague should do the next:
person B should build all pending changes (some project files which were pulled from Salesforce can still have the Windows line-endings);
after the successful build person B should push all project files to the Git repository;
person A should make the Git pull; after this they should open the TWS project and pull changes from Salesforce.
As a result both of you will have all the files with the same hashes.
I kindly ask you to keep us informed if these steps solve your issue.