Once we have scaffolding for seeing the state of application objects used by a pipeline (#194), we can implement the promotion algorithm as given in the RFC
the aim is to test that the algorithm has the expected behaviour, and get the information needed for the new UI to work
this does not need to open PRs or whatever else promotions involve; it can assume success (or as needed for testing)
this does not need to make promotions reliable (there will be another issue for that)
it may need to record to the pipeline status for the purpose of testing, but it doesn't need to record everything in anticipation of UI requirements
[ ] tests that demonstrate the success and failure modes of the algorithm (e.g., by manipulating individual application objects)
Once we have scaffolding for seeing the state of application objects used by a pipeline (#194), we can implement the promotion algorithm as given in the RFC
the aim is to test that the algorithm has the expected behaviour, and get the information needed for the new UI to work
this does not need to open PRs or whatever else promotions involve; it can assume success (or as needed for testing)
this does not need to make promotions reliable (there will be another issue for that)
it may need to record to the pipeline status for the purpose of testing, but it doesn't need to record everything in anticipation of UI requirements
[ ] tests that demonstrate the success and failure modes of the algorithm (e.g., by manipulating individual application objects)