Would this then be possible by cloning the task (which is a pipeline) and accessing the right subtask (the component which should be changed)?

I think I got it! I found that the branch for the component is specified in the UI in the component’s configuration object under the pipeline’s configuration tab. In theory I should be able to clone the pipeline task, use the get_configuration_object method, change the branch, set it using the set_configuration_object , and finally enqueue! Going to test this out

Hi Chingiz! Is the LIBRARY_IN_REPO in the root of the repo? How do you run this pipeline (with run_locally, debug_pipeline or with an agent)? And lastly, have you checked the clearml logs to see if the repo was correctly pulled?
I ask these questions because the pythonpath is the root of the repo and the repo can only be used when running the pipeline with an agent, IIRC

Hi Mark! Do you set any of the decorator parameters using variables? That was my issue, and instead of using python variables, I hardcoded one potential value, and then used the get and set methods to change them when cloning programatically, which should be the same as changing them in the configuration tab when cloning with the UI. Hope this helps 🙂

I’m also not sure but it seems like the slack trial renews from time to time in this workspace, which eventually gives access to those older threads

Awesome! Really simple and clever, love it. Thanks Eugen!

Reporting back: this example worked, but unfortunately did not run successfully when cloned in the UI, with an error of base_task_id is empty akin to https://clearml.slack.com/archives/CTK20V944/p1662954750025219 previous slack thread. By editing the configuration object as mentioned above (programmatically also possible with the get and set configuration objects), the pipeline also worked when cloned 🙂