----- Original Message -----
From: RamCharan Vemulakonda
To: Git for human beings
Sent: Friday, February 12, 2016 2:19 AM
Subject: [git-users] GIT as an SCM for DataStage Code Artifacts
There is no easy answer to the question "Which is the most preferred Source
Control Management System for storing, versioning and maintaining DataStage
Artifacts?"; not because there are a variety of options but because there are
The first question would be, "What, exactly, are DataStage Artifacts?". (a
reference to a description would be handy)
Are they large Mb, Gb; Are they binary or ascii/unicode/etc. text ?
What are the important factors to you within the data - do you need to look at
changes, have multiple lines of development, diverse user groups going of in
their own deirections. Is it source code ?
I hear that Rational Clear Case, CVS and SVN are viable options but I would
like to know if any of you have used GIT as a Source Control for DataStage
artifacts. If yes, did it pose any problems to Deployment Automation?
Git is designed for the storage of text based computer source code where there
are disparate contributors, it distributes the control from 'management' to
users and it maintains a verification structure, so that management can get
some authority back.
It can, but is not great at, managing large discrete binary artefacts. Other
horses are better for that course...
To add more to the context, my aim is to integrate GIT with Atlassian Bamboo
and Artifactory for Build & Deployment Automation.
Please share your expert advise and ideas on going about this.
Many thanks in advance.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.