Investigate automatic triggering of pages 'deploy' stage after a 'test' stage is reran
It's plausible that a specific pipeline test job could fail due to transient reasons, as such it's common for it to then pass on a rerun. However this doesn't re-trigger the pages deployment/artifact stage, as such the pipeline snapshot as displayed in the compatibility matrix does not reflect reality and can 'wrongly' highlight incompatibility.
As it stands the deploy stage can be rerun manually as to update the matrix with the latest results for a given pipeline, but it would be beneficial if this action was automatic.
Edited by Tom Pollard