It would be very useful to be able to add an SVN material to a downstream pipeline and have it checkout the same SVN revision as its upstream pipeline.
As an example
CI Pipeline => Test Environment Deployment Pipeline
The CI Pipeline has an SVN material. Go today allows the Test Environment Deployment Pipeline to share the same SVN material as the CI Pipeline, however there is no way to force the Test Environment Deployment Pipeline to checkout the same SVN revision as the CI Pipeline build that triggered it.
The lack of this features means that today I have to put everything needed for a deployment into a build artifact and pass that from the CI Pipeline to the Test Environment Deployment Pipeline. This is proving far to complex and cumbersome. I'd rather just put the build output (e.g. compiled code) in the artifact passed from pipeline to pipeline and then get everything else from SVN.
Please ask if you need any more info or clarification
Please sign in to leave a comment.