Five Stars

Source Code Control within Git Best Practices

I'm looking for some advice on best practices for doing source code control with DI projects using git.  We want to:


  1. Manage/version/tag our Talend projects in our git repo
  2. We want to not only include the generated Talend code but also include external scripts/code that we make calls to from our mappings/projects.
  3. We want to include database DDL/build scripts that must be run as part of the mapping/project release
  4. We want to be able to bundle and deploy our projects to different physical environment containing their own TAC/job server/etc.

We want to be able to tag and version all of these files within a single git repository.  Is there any sort of best practices document to which I can refer to do this?



Re: Source Code Control within Git Best Practices


Please have a look at this topic: documents about:TalendHelpCenter:General Git Best Practices ,TalendHelpCenter:Best Practices: Using Git with Talend

Let us know if it is OK with you.

Best regards


Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.