Using Github for SVN repository, what to do about empty directories?

One Star

Using Github for SVN repository, what to do about empty directories?

I'm attempting to use a Github repository for the SVN integration. The connection works properly but Talend throws errors when it tries to commit because git repositories don't support empty files. Is there any standard way to address this? I'm hoping there's some option available to make it so that Talend won't create empty directories. I imagine I might be able to make it work with .gitignore in most of the directories but it's not a particularly flexible solution. Below is one of the errors that appears at startup.
org.tigris.subversion.javahl.ClientException: svn: E160024: Commit failed (details follow):
svn: E160024: Empty directories are not supported: trunk/businessProcess, trunk/businessProcessSVG, trunk/code/jobscripts, trunk/code/snippets, trunk/components, trunk/context, trunk/documentations/generated/joblets, trunk/documentations/generated/jobs, trunk/images/job_outlines, trunk/images/joblet_outlines, trunk/joblets, trunk/libs, trunk/metadata/BRMSconnections, trunk/metadata/EDISchema, trunk/metadata/FTPconnections, trunk/metadata/LDAPSchema, trunk/metadata/MDMconnections, trunk/metadata/SalesforceSchema, trunk/metadata/WSDLSchema, trunk/metadata/connections, trunk/metadata/fileDelimited, trunk/metadata/fileEBCDIC, trunk/metadata/fileExcel, trunk/metadata/fileHL7, trunk/metadata/fileLdif, trunk/metadata/filePositional, trunk/metadata/fileRegex, trunk/metadata/fileXml, trunk/metadata/genericSchema, trunk/metadata/header_footer, trunk/metadata/json, trunk/metadata/rules, trunk/metadata/sapconnections, trunk/metadata/validationRules, trunk/sqlPatterns/Generic/UserDefined, trunk/sqlPatterns/Hive/UserDefined, trunk/sqlPatterns/MySQL/UserDefined, trunk/sqlPatterns/Netezza/UserDefined, trunk/sqlPatterns/Oracle/UserDefined, trunk/sqlPatterns/ParAccel/UserDefined, trunk/sqlPatterns/Teradata/UserDefined


This is so close!
Thanks!
Moderator

Re: Using Github for SVN repository, what to do about empty directories?

Hi,
So far, talend don't support for git repository feature.
Please take a look at a related jira issue:https://jira.talendforge.org/browse/TUP-3308.
Best regards
Sabrina
--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.
One Star

Re: Using Github for SVN repository, what to do about empty directories?

Github allows using SVN clients to interact with the repository with the only caveat being that you can't store empty directories. I'm not asking for 'git support' in particular; if we were able to simply tell Talend to not generate empty folders (or some other solution) then this would be usable. Please don't write off this issue as "git is not supported" so quickly.
Moderator

Re: Using Github for SVN repository, what to do about empty directories?

Hi,
if we were able to simply tell Talend to not generate empty folders (or some other solution) then this would be usable.

The empty folder in project is standard. We will modify it after git remote project feature is available.
This feature https://jira.talendforge.org/browse/TUP-3308 is in process. Feel free to let us know if there is any help we can give.
Best regards
Sabrina
--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.
One Star

Re: Using Github for SVN repository, what to do about empty directories?

I posted on the issue, hopefully it helps out somehow.
Sixteen Stars

Re: Using Github for SVN repository, what to do about empty directories?

The problem is Jason, that Talend does not work with SVN as a simple client. As far as a Talend developer/administrator is concerned, SVN is a black box that you MUST leave alone to let Talend control. There is no merging of code at all and any branching (which is possible) is controlled by TAC (Talend Administration Center). As such, it is actually fair to say that GIT is not supported. If I were you I would forget using GIT and use SVN until it is supported. It will only end in problems. 
This opinion does not come from being scared to try things out and bend the rules by the way, it comes from having tried them out and having seen the consequences :-)
One Star

Re: Using Github for SVN repository, what to do about empty directories?

I (think I) understand your viewpoint, but my point is that GitHub treats their repositories as an SVN repo (from the SVN client's point of view), with the exception that it can't store empty directories. I'm not asking for GIT support in particular. From Talend's perspective a repository on GitHub IS (or can be?  not sure if it depends on the directory structures of the respository) an SVN repository.
I'm sorry for being stubborn but at this point I sincerely believe that it's nearly possible as-is. Maybe I'm not explaining it clearly enough, or maybe I'm not understanding it clearly.
Sixteen Stars

Re: Using Github for SVN repository, what to do about empty directories?

I get what you are saying and you are right. It is nearly supported in that all it sounds like it needs to do is get rid of empty folders. But the application is built expecting to build the folder structure regardless of whether it is populated. Easy to fix I would have thought, but it depends on how high on the road map supporting GIT is. 
With regard to my point about just using SVN instead of GIT, this is what I meant. There is absolutely no advantage to using a repository "known" by developers because you really won't be using it for anything other than allowing developers to share code (handled entirely by the TAC and Studio) and as a backup of your work (again, handled by the TAC). You would only ever go in and retrieve an old version of code if your system has had serious issues and there is no other solution. Doing this can break a project. 
On another note, your system will not be supported if you do not use supported components. As with any software company, if you have any issues (any at all) with the stack, your code, your drive home from work,..., it will not be supported and Talend will be under no obligation to sort it for you. Since the support is a key thing you are paying for, you are wiping out a significant part of the value by doing this.
I do agree with your thinking, but suggest you stick with SVN until GIT is supported.
One Star

Re: Using Github for SVN repository, what to do about empty directories?

Richard, I agree that there's no 'real' advantage considering that it would be unsupported. Also, nobody will be wanting to manually affect anything via git, so the only actual advantage to it is some case where you're creating a minor (unsupported) project and want to use hosting that you already have available, and possibly the fact that you could use your git repo credentials instead of having a different account to manage.  I suppose if for some reason you were using enterprise for creating an open source project it would be beneficial but the likelihood of that is practically nothing.
That said, I did create a couple of feature requests (https://jira.talendforge.org/browse/TUP-3454 and https://jira.talendforge.org/browse/TUP-3453) that I am interested in just for the sake of experimentation.  I think TUP-3454 would open up some possibilities that open studio could take advantage of as well.  It's my impression that it would be sort of low hanging fruit but of course I have no actual idea how it is on the Talend Studio developer's side.