Use debug bundle upload in premerge CI#1018
Conversation
Signed-off-by: Peixin Li <pxLi@nyu.edu>
|
I will run a validation test w/ test-only commit first |
Signed-off-by: Peixin Li <pxLi@nyu.edu>
Signed-off-by: Peixin Li <pxLi@nyu.edu>
|
build |
This reverts commit 37cfae9.
|
build |
Greptile SummaryThis PR migrates the premerge CI pipeline away from a Persistent Volume Claim (PVC) for inter-stage workspace sharing, relying instead on Jenkins' stash/unstash mechanism (already in use for the
Confidence Score: 4/5The change is safe to merge; the stash/unstash swap for PVC is straightforward and test.sh does not rely on git history, so the default stash exclusions are harmless. The migration from PVC to stash/unstash is mechanically correct, and the debug-bundle upload on failure is a useful addition. The one concern is that if ci/Jenkinsfile.premerge — specifically the catch block around the debug bundle upload. Important Files Changed
Sequence DiagramsequenceDiagram
participant BD as Build Docker Stage (cpu pod)
participant JS as Jenkins Stash
participant GT as Premerge Test Stage (gpu pod)
participant AF as Artifactory
BD->>BD: git checkout (source)
BD->>JS: "stash("source_tree", "**")"
BD->>BD: "build & push Docker image"
GT->>JS: unstash("source_tree")
GT->>GT: resolveIncompatibleDriverIssue()
GT->>GT: bash ci/test.sh pre-merge
alt test fails
GT->>AF: uploadDebugBundle()
GT->>GT: throw original exception
end
Reviews (1): Last reviewed commit: "Revert "TEMP: Force premerge debug bundl..." | Re-trigger Greptile |
Remove PVC usage, use artifactory to persist build info of failure runs.