topic Re: Cannot create an execution task from TAC in Talend Studio

Cannot create an execution task from TAC

navds — Sat, 16 Nov 2024 05:33:55 GMT

Here is what I've done so far.

Create a project in TAC, associated a git repository, give the user read-write permission on the project authorization menu
Open the remote project in the Studio, created a simple job (tRowgenerator -- tLogRow). Boom, it is committed in the git repo.
Publish the job from Studio to Nexus at the 'release' repository.job in nexus
Now, I tried the two following options in jobCondutor. (1) Add artifact task. The job is not shown when I browse from the artifact repository to select it. (2) Add normal task. The uploaded zip (built from the Studio) could not be imported with the error "This job was created by an unsupported version of Talend Studio"

Re: Cannot create an execution task from TAC

Anonymous — Wed, 19 Jun 2019 08:35:03 GMT

Hello,

When you build or publish a Job, you must select the Items check box to include the Job items file with the Job build. To do this, open the Studio Job and republish the Job with the Items check box selected, then add the task to Job Conductor.

Let us know if it fix your issue.

Best regards

Sabrina

Re: Cannot create an execution task from TAC

navds — Mon, 24 Jun 2019 11:59:01 GMT

In case some will encounter this on the first launch of TAC, please edit your configuration so that jobConductor > Generated jobs folder is existing and writable. Then, do not rely on the green status of artifactory repository parameters, you have to set in the password for the first time, the default value is apparently not working (maybe it is empty but it shows green).

Re: Cannot create an execution task from TAC

naveenkumarbv — Sun, 19 Apr 2020 01:56:12 GMT

Is anyone experiencing this issue anytime other than launching TAC for the first time? Also, looks like we are encountering this problem when we publish an artifact to Nexus and try to "Save" the artifact in Job Conductor and not from Talend studio.

All the folder permissions for generatedJobs or executionLogs look good.