Publish to CTI validation stage in Staging pipeline publishes the signed bits to a staging location. Repo propagation stage in Release pipeline is dependent on this stage, cos this stage has access to that staging location where signed bits are published during staging pipeline.
Historically, we have seen failures Repo propagation stage in Release pipeline, cos the assets failed to publish in the Publish to CTI validation stage. When this error occurs, Rahul manually used to copy the files to the desired location and rerun the stage. We need a better mechanism to
- Detect this error faster
- Make sure we can avoid human intervention as much as possible
For Eg:
Add a validation that will confirm that the assets were published to CTI validation stage so that manual coping of assets can be avoided. (main pain point - assets are huge and manual copying takes forever)
Publish to CTI validation stage in Staging pipeline publishes the signed bits to a staging location. Repo propagation stage in Release pipeline is dependent on this stage, cos this stage has access to that staging location where signed bits are published during staging pipeline.
Historically, we have seen failures Repo propagation stage in Release pipeline, cos the assets failed to publish in the Publish to CTI validation stage. When this error occurs, Rahul manually used to copy the files to the desired location and rerun the stage. We need a better mechanism to
For Eg:
Add a validation that will confirm that the assets were published to CTI validation stage so that manual coping of assets can be avoided. (main pain point - assets are huge and manual copying takes forever)