Hello Team - I am new to Talend and looking for your help here on code migration. I am using Talend 5.4.2 version and have 4 environment - Dev, Test , Acceptance and Production. I am looking for best approach for release and deployment process Also include version control. Is there any document available or please explain here.
1. use in your jobs so called Implicit Context Load. This way you can read all necessary credentials or whate ever values from a file depending on which environment the job runs - without changing the job itself.
2. For development create a GIT or SVN repository using the head/master and for test and production use branches.
3. Transport the jobs from one environment to the next with the Item Export/Import.
4. Use the versioning of the job and define how to use the major/minor versions
Hi Jloling - Thanks for your reply. but I want to restrict studio in other environment. so that Tester and Production user can not see job. So I would prefer with binary job deployment via go with Build job.
but the problem here is if we have 10 subjob in master job and if we build master job and we can integrate in TAC. its good. but now the problem arise here when Tester raise two defect in Testing and once Development team start fix, he has fix one job and second is in progress. but I need to send the release to Test environment. In this case If I build job again of master then one job of work in progress also go and it fail. also this is not a good practice to send master job in each release. and if I have around 30 jobs then scheduling them in Job conductor and then create execution plan also make it difficult. Please suggest.
Regards,
Vicki.
so by importing and exporting needs studio in other environment that I want to restrict. This is the reason I want to prefer binary job. In my case I have parent job having 20 jobs and if there is any fix i one job even though I need to send parent job. and if I sent all 20 jobs then all of those job needs to be schedule and then create execution plan. so I am confused how to proceed?
Indeed it is your decision how fine grained you deploy jobs as task in the TAC. I usually try to separate thinks when it makes sense to restart a process at this point. You can also deploy the whole process as one huge single job - but you will lose control.
Deploying different jobs has the advantage to be more stable and erroneous handling have less negative impact.
There is also a good alternative to a execution plan, especially if jobs need context variables from the previous job.
I have developed a component tRunTask to allow a job to start task in the TAC with using context variables and retrieving the job exit code - just like tRunJob does.
https://exchange.talend.com/#marketplacesearch:gallery=marketplace%252F1&ob=releaseDate&o=0&c=20&d=t... With this component you can design complex processes and deploy the parts of the process separately in the TAC as task.
Hi - I have added tRuntask zip file in studio (version 5.4.2) by Windows --> Preference -->Talend -Component -even I am not able to find tRuntask in pallet. not sure what is the issue.
