You give with one hand but take away with another... what is the point of this feature if it now removes deployment tracking?
But what I really don't understand is why... I guess the confusion is on which pipeline would participate in the deployment racking, the parent or the child. Why don't you let us decide that?
I effectively cannot use this feature because I have to give up deployment tracking. But pipeline invocation (which is what I was using) is just terribly slow.
We ran into an issue today while attempting to implement this feature. It turns out that pipeline names cannot have spaces in them. Even when wrapped in quotes. There's a reason the sample code from the blog works, and that's because the pipeline names are slugified. If you change the pipeline names to be "A Parent Pipeline," for example, the pipeline will fail.
This confounded us because we didn't see it documented in the notes. Perhaps you could ask your team to either update the docs with the requirement, or fix it if it's a bug.
27 comments