You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The UI needs to know where is the pipeline run "up to":
which revision is running through the pipeline
which environments have reached a ready state with the revision
in each environment, which targets are healthy and which not
for targets that are not ready, why are they not ready (to the detail that the application object status allows)
is a promotion waiting to succeed for some environment
should it show an approval button for a particular environment
This should probably be done in concert with showing these things in the UI, so we can be sure it has all the things needed. NB some items can be aggregated in the WGE API, or calculated by the UI itself. But, for integration with other systems (e.g., Backstage plugins), we should try to make the pipeline object status useful on its own.
The text was updated successfully, but these errors were encountered:
squaremo
changed the title
Record the state of a promotion run in status, so the UI can see it
Ensure the state of a pipeline run reflected in the status, so the UI can see it
Sep 21, 2023
squaremo
changed the title
Ensure the state of a pipeline run reflected in the status, so the UI can see it
Ensure the state of a pipeline run reflected in the status, for the UI to interpret
Sep 21, 2023
squaremo
transferred this issue from weaveworks/pipeline-controller
Nov 14, 2023
squaremo
changed the title
Ensure the state of a pipeline run reflected in the status, for the UI to interpret
Interpret the state of a pipeline run for the UI, in the API
Nov 14, 2023
The UI needs to know where is the pipeline run "up to":
This should probably be done in concert with showing these things in the UI, so we can be sure it has all the things needed. NB some items can be aggregated in the WGE API, or calculated by the UI itself. But, for integration with other systems (e.g., Backstage plugins), we should try to make the pipeline object status useful on its own.
The text was updated successfully, but these errors were encountered: