Reputation
Badges 1
90 × Eureka!AgitatedDove14 it’s pretty much similar to your proposal but with pipelines instead of tasks, right?
So “The” pipeline Engineer A creates, once updated with the latest code, and perhaps ran once as test by CI CD, should be “tainted” as “The production” version of that pipeline, so that Engineer B’s code always uses the latest released pipeline code
CostlyOstrich36 If I delete the origin and all other info and set it to tag_name=‘xxx’ then it is able to work
CostlyOstrich36 from what I gather the UI creates a task in the background, in status “hidden”, and it has like 10 fields of json configurations…
It’s more like this:
I have a pipeline, ran on all data.
Now I change/add a sub-dag to the pipeline
I want to run only that sub-dag on all historical data in ad-hoc manner
And then next runs will run the full dag (e.g. only on new data)
AgitatedDove14 thanks, it was late and I wasn’t sure if I needed to use one of clearml “certified” AMI’s or just a vanilla one.
which configuration are you passing? are you using any framework for configuration?