Hitachi Vantara Pentaho Customer Portal

Best Practices - Working with Git and Pentaho Enterprise Repository

Your feedback is important to us!  Email us how we can improve these documents.

Software

Version

Pentaho Data Integration

7.x

Overview

This document covers best practices to work with revision control system different than default provides DI repository and how to work/interact between local developments revisions and deploy repository environments to be consumed by DI.

The Pentaho Data Integration repository offers a basic revision control system which is not intended to replace most common market tools, such as GIT. The repository is characterized by having a variety of options and features that are very mature and normally present in most IT departments, but offers a simpler possibility for those who do not have any.

The main reason to establish the use of a specific revision control system as a best practice in your development environment is house policies and experience around using those systems, or if you want to use some advanced futures, such as fork, tag, etc.

Some of the things covered here include repository structures, working with GIT patterns, methodological guidelines, migration, and a step-by-step best practice example. 

pdf.png - Best Practices - Working with Git and Pentaho Enterprise Repository

Have more questions? Submit a request

Comments

Powered by Zendesk