Under v7.0.1 we were able to use a relative path to a context file. This still works when we deploy a job but v7.1.1 can't find the file when we run the job from within the studio.It appears that the jobs are now built and run from a different folder under v7.1.1. I can place the file so that the job can find it but this needs to be done for each job. Can I create a relative path to the context that is always seen from the test jobs? Or can I tell Talend to always run the test from the same location and place the file relative to it? Thanks.
Unfortunately this is a classic issue when relative path is used for file path of an important file. My recommendation will to be change the path to absolute path since you need to make some changes. This will make sure that any future upgrades will not create any issue for your job flow.
Please appreciate our Talend community members by giving Kudos for sharing their time for your query. If your query is answered, please mark the topic as resolved :-)
A nice workaround to your problem may be found in these blogs I put together....
Did you know that you can use routines in the Implicit Content Load parameters? The blogs should probably be read in sequence, but jump to blog 3 to see how you can use routines with the Implicit Context Load. What I have described there is much more complicated than you need, but it might give you some ideas
Talend named a Leader.
Kickstart your first data integration and ETL projects.
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