Persistent job log button after hard refresh or route change
-
ensure Log button is enabled if a log exists even after hard refresh (vs just right after validating in memory after a run) - There are a few approaches here. Two that first come to mind are:
- brittle but quicker assumption of
job_
+name-of-pipeline
being a job id and looking this up increated
forPipelineSchedules
- add, persist, and overwrite a
lastJobId
identifier whenever a pipeline runs so the UI has thejobId
it
- brittle but quicker assumption of
- There are a few approaches here. Two that first come to mind are:
Edited by Derek Knox