topic Re: Talend SMALL Reference Architecture - Shared Dev and Test Implementation in Talend Studio

Talend SMALL Reference Architecture - Shared Dev and Test Implementation

borrisbeck — Tue, 25 Jul 2017 19:46:41 GMT

In this talend documentation, under "Typical SMALL Reference Architecture" its mentioned as, a single environment can be used for both Development and Testing, Can someone please explain how it can be done in practice?

https://help.talend.com/reader/t2d9W5LwjZdETEJJST~2Jg/RXPt2lH4tzUZNcQNolWxIQ

My assumption is creating two projects one as "Dev_Env" and other as "QA_Env" on the same environment and deploy the developed code from "Dev_Env" in to "QA_Env" project and do the testing there? is this possible or is there any other way? thanks

Re: Talend SMALL Reference Architecture - Shared Dev and Test Implementation

Anonymous — Wed, 26 Jul 2017 00:00:00 GMT

You need to separate the concept of Talend Design code vs binaries generated after a build.

The TAC is use for many things:

- Managing Users

- Managing Projects

- Managing Servers

- Managing and Scheduling Tasks.

You just need 1 project, and use tagging functionality to tag your projects. Once tag, you can open the tagged version in Studio and build a job from the tagged version. You can also automate that build using CI or CommandLine. Once a binary is build, an operation manager who is looking after the test environment, will deploy it in TAC, target the Test JobServer, if you have a different one, set the parameters and schedule it.

Hence you use the project management part for DEV environment and Scheduler part for Test environment.

You do not need to create 2 projects. Your SVN or Git already provides the capability of tagging the project so that it cannot be altered. So, your code is baselined if you tag it with the right label.

Re: Talend SMALL Reference Architecture - Shared Dev and Test Implementation

borrisbeck — Wed, 26 Jul 2017 20:02:06 GMT

Thanks for the response, apart from having a ready only version of the project, In what ways tagging is advantageous when compared with a separate project for test environment? if i'm not wrong a project can also be made ready only for some users isn't it?