ROX-30960: add container start time as a column#16933
Conversation
|
This change is part of the following stack: Change managed by git-spice. |
|
Skipping CI for Draft Pull Request. |
|
Images are ready for the commit at 92c8cbc. To use with deploy scripts, first |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #16933 +/- ##
=======================================
Coverage 48.82% 48.82%
=======================================
Files 2693 2693
Lines 201342 201345 +3
=======================================
+ Hits 98310 98312 +2
+ Misses 95275 95274 -1
- Partials 7757 7759 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
43b8187 to
95eab27
Compare
6f0c461 to
92c8cbc
Compare
|
/retest |
|
Caution There are some errors in your PipelineRun template.
|
Description
When we evaluate the process indicators against the baseline we pull the entire indicator for the deployment. The indicator can be quite large. We are only looking at 6 fields. To improve our memory footprint as part of epic ROX-30958 we are going to only pull the fields we need. Container start time was the only field that was not already a column. So this PR adds it as a column. Subsequent PRs will add the migration and use the new column.
User-facing documentation
Testing and quality
Automated testing
How I validated my change
Simply promoting a field to be a column. CI is sufficient here.