You are not logged in.

#1 2012-11-02 13:17:31

userabc123
Guest

Copy Job conductor

Hi,

After some help, we have completed Talend development on our dev server and have created 10 Talend job conductors jobs to run our flow in the TAC.

We use the studio to export the Talend jobs into an archive to migrate the code to our test server. How do we export the 10 jobs setup in the job conductor so we do not have to recreate them all from scratch in the Test TAC?

This seems a simple request but I can't figure it out, please help anyone.

#2 2012-11-02 13:35:48

shong
Talend Team


Re: Copy Job conductor

Hi
Follows these steps migrate your projects from dev server to test server:
1. Export svn repository and tac database from dev server,  backup them.
2. Import svn repository and tac database to test server.
3. Install test tac, point the tac database to the database which you have migrated from dev server.


Email:shong@talend.com
Choose Talend, Enjoy Talend!
New & Event: Talend Help Center
Talend-->the global leader of open source data management and application integration solutions!

Offline

#3 2012-11-02 14:17:46

userabc123
Guest

Re: Copy Job conductor

Thanks for the prompt reply, this works in the case of the first ever release, however without replacing the entire production repository in say 6 months time how do I simply release 1 new job conductor job into Production. Client release policy would never allow you to wipe out production and simple replease.

So question still stands how do I take a job conductor job from dev export it and into into test/production, knowing no client would allow a complete svn repleace?

#4 2012-11-07 03:31:57

shong
Talend Team


Re: Copy Job conductor

Hi
It depends on what situation you are,  if you want to migrate jobs to a completely new environment, new TAC, new database and new SVN server, you have to follows the step I suggested in previous post.  If you just install one TAC instance for dev/test/prod, you can just define context with different environments in the job, and select corresponding context while executing the job.


Email:shong@talend.com
Choose Talend, Enjoy Talend!
New & Event: Talend Help Center
Talend-->the global leader of open source data management and application integration solutions!

Offline

#5 2012-11-07 15:47:13

nicolasdiogo
Member
460 posts

Re: Copy Job conductor

that is a good question

having different environments - DEV, TEST, PROD

we would like to find a simple - *wish* - single (few) click (s) to move a solution/project between these environments.

this requirement would seem like a basic feature - or maybe not!? :@

exporting the whole DEV database over to TEST would not do as there will be job that may be edited but not fully.
i suppose we are looking for some sort of chain that would allow for all the jobs, triggers, and ... to be copied over to this new environment.

shong - i do not think your suggestion really answers the question in a feasible manner.  maybe you could raise this internally and see if there is an alternative?

regards,

smile

Offline

#6 2012-11-13 16:04:02

userabc123
Guest

Re: Copy Job conductor

Keen to see an answer to this.

I don't see how you could use Talend in a real client world without the ability to export/import job conductors jobs in the same manner you can the code. No real world client with any real form of change control is going to allow anyone to replace SVN in Production for any code release. Take a bank for example tight change control would never allow this. Maybe a slight chance for the first ever release, never for subsequent releases. The answer cant be to setup all the jobs by hand in the Production TAC, we would get escorted out the building.

For migration projects you might get away with this since it's a one off move to run. For real integration/daily running projects requiriing bug fixes, regression testing etc this makes no sense.

This is basic requirements for an ETL ability to do code deployments (code & TAC jobs). Can anyone adivse I can't believe we are the first to hit this.

#7 2012-11-23 15:38:48

nicolasdiogo
Member
460 posts

Re: Copy Job conductor

i suppose that an alternative would be to create a set of queries that collect the necessary data from TEST Job Conductor and insert this into PROD Job Conductor.

but *should* i really be doing this HACK?

Offline

#8 2012-11-23 15:42:41

nicolasdiogo
Member
460 posts

Re: Copy Job conductor

requested this feature here:
https://jira.talendforge.org/browse/TDI-23905

Offline

#9 2013-07-08 16:45:09

ratneshsing
Member
25 posts

Re: Copy Job conductor

Hi,
I think this is a very valid request, we are facing lot of rework and it takes a huge effort for us when we have to migrate project /job and right-now we are migrating from 5.0 to 5.2 and have to move each project and job one at a time, we use SVN but that's of no use since DEV and PROD TAC are different and cant see jobs from same SVN.

There should be a feature to deploy in fewer click to any environment. Is there any development going on ?

Offline

#10 2013-07-11 15:00:02

esabot
Talend Team


Re: Copy Job conductor

What about Talend Repository Manager?
This is a standalone Talend product that used to be only delivered on demand, but since 5.3 we deliver it along with all platform subscriptions: https://help.talend.com/display/TalendR … e14EN/Home
I'm not sure it addresses all the needs but check it out, maybe this would help.
I'm not saying TDI-23905 isn't a valid request, just presenting one potential option.


Talend - Global leader in Open Source Integration

Offline

Board footer

Talend Contributor Agreement - Talend Website Privacy Policy