Let's say I have a job at version 7.4 (M.m) in Talend Studio. I publish it on Talend Cloud with version 7.4.0 (x.y.z).
I find out it's not working and I quickly need to republish and older version, for example 7.3 from a GIT tag, to the cloud.
When I click publish on my 7.3 job, the popup shows the latest cloud version is still 7.4.0 (even though I deleted the artifact from the cloud) and therefore it doesn't let me publish anything inferior to 7.4.0... I don't want to publish my older 7.3 as 7.4.1, it doesn't make any sense!
Please could someone explain how are you supposed to publish an older version of an artifact to the cloud?
Thank you very much
The Karaf container has cached the previous version of the task, so Karaf is running the version that was executed earlier.
Could you please try these two possible solutions:
Clear the Remote Engine cache for the task, by performing the following steps:
\Talend-RemoteEngine-version\data\m2\actions\Task Name \Talend-RemoteEngine-version\data\m2\flows\Task ID \Talend-RemoteEngine-version\TalendJobServersFiles\archiveJobs\Task Name.zip \Talend-RemoteEngine-version\TalendJobServersFiles\repository\Task Name
To prevent this, Talend recommends that instead of deleting the artifacts/tasks, keep publishing them to create a new version, then Karaf will download and run the newer version.
Let us know if it works.
Talend named a Leader.
Kickstart your first data integration and ETL projects.
Watch the recorded webinar!
This video will show you how to add context parameters to a job in Talend Cloud
This video will show you how to run a job in Studio and then publish that job to Talend Cloud
This video will help someone new to using Talend Studio get started by connecting to Talend Cloud and fetching the Studio License