Carry over Artifact/STO/Unit Test reports from retries if stages are not re-run
long-term
P
Psychological Firefly
If a pipeline is retried, the results panes, (unit tests, artifacts, security tests, etc), are wiped. This makes sense if the stage that produces these reports is retried. If the stage that produced the report has not been retried in this execution, its report should carry over to that retry. This can help teams use those reports without needing to dig through execution retries.
Log In
Canny AI
Merged in a post:
Stage retry pipeline job doesn't carry the Tests Results from Previous Successful Stage
L
Likely Nightingale
When the First Stage was successful with all tests result and Tests tab report, but Second stage Failed. So, when retrying the second stage, it should maintain the Tests result from the First Stage, just like logs n other.
If it's maintaining the logs and results from the previous tests which were successful, then it should maintain the Tests tab result too for consistency.
Otherwise, developer needs to find the original build to see the Tests Tab for first stage and recent one to find the results of current stage... which is a cumbersome process
related ticket: https://support.harness.io/hc/en-us/requests/82199
Rohan Gupta
long-term
P
Psychological Firefly
Gotcha, so anything coming from drone would need to use this new API to be carried over? Does that include other functions like Chaos or IaCM?
Rohan Gupta
Psychological Firefly: it would be on a case by case basis. Basically the objects would need to be stored in the pipeline context how we do that would need to be consistent across the products.
Rohan Gupta
pending feedback
Unfortunately our current system cannot support this capability as CI and CD do not operate the same way. The artifact or files stored in the build pod are not being carried over to CD. As we do not store artifacts on the delegate or transfer context from build pod to delegate.
We are looking at a mechanism where you can upload evidence ie security reports and unit tests that you can access via an api in a separate step.
Pritesh Chandaliya
under review