Source Code Control within Git Best Practices

Highlighted
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?

 

Moderator

Re: Source Code Control within Git Best Practices

Hello,

Please have a look at this topic:https://community.talend.com/t5/Architecture-Best-Practices-and/Connecting-Talend-with-Git-SSH/ta-p/...and 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

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.

2019 GARNER MAGIC QUADRANT FOR DATA INTEGRATION TOOL

Talend named a Leader.

Get your copy

OPEN STUDIO FOR DATA INTEGRATION

Kickstart your first data integration and ETL projects.

Download now

What’s New for Talend Summer ’19

Watch the recorded webinar!

Watch Now

The Forrester Wave: Strategic iPaaS and Hybrid Integration Platforms, Q1 2019

Find out how Forrester rate different iPaaS and Hybrid Integration Platforms

Read

How Media Organizations Achieved Success with Data Integration

Learn how media organizations have achieved success with Data Integration

Read