ci: match the Blossom template form for blackduck properties - #1057
Conversation
The step was written with an inline run: instead of the block scalar the template and NVFlare both use, and Blossom rejected the file with "workflow file does not match any supported template version". Use the snippet exactly as given, including the PIP,POETRY,CONDA list. Refs: HPCINFRA-4862 Signed-off-by: Or Balayla <obalayla@nvidia.com>
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: NVIDIA/cloudai/.coderabbit.yaml Review profile: ASSERTIVE Plan: Enterprise Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review. 📝 WalkthroughWalkthroughThe CI workflow now excludes Black Duck detector types ChangesCI scan configuration
Priority: ➖ Normal Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Bug fix Suggested reviewers: 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Comment |
|
/build |
After #1056 merged, Blossom rejects the workflow before it starts:
The step content was right but the form was not. I wrote it with an inline
run:; both the snippet Blossom gave us and NVFlare use a block scalar, which produces a different string for that step.This uses the snippet exactly as supplied, including the full
PIP,POETRY,CONDAlist and the template comment line, so nothing is left deviating.Refs: HPCINFRA-4862