Chain calls to the jobs can be made by importing the call_job function from a package provided by the job type plugin
from job_wrapper.call import call_job.
Keeping this chain call function inside this plugin makes sure it will always be up-to-date with the job type.
No additional step for updating this function. Job developers update job type version occasionally, then it will get updated too automatically.
It is Python-related, so it makes sense to keep it not in the Racetrack core, but inside plugin-python-job-type.
No additional PyPI libs to import
Drawback: Job developers will have to import from job_wrapper library that doesn't exist locally. (Is it really a drawback? It was never available to make chain calls locally)
racetrack-client tool is no good place for it as it's supposed to be language-agnostic core of the Racetrack
Chain calls to the jobs can be made by importing the
call_jobfunction from a package provided by the job type pluginfrom job_wrapper.call import call_job.job_wrapperlibrary that doesn't exist locally. (Is it really a drawback? It was never available to make chain calls locally)