You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are building the SBOM manually in our Jenkins pipeline with cdxgen and then using the plugin to upload to Dependency Track. It is working successfully in another job, for some reason we are getting this error:
Earlier in the pipeline we can see bom.json is generated, is a non-zero file size and sitting in the same directory referenced above:
Can you provide guidance on troubleshooting this error?
Environment
Plugin Version: 4.3.1
Type of Jenkins Job: pipeline
The text was updated successfully, but these errors were encountered:
Describe the bug
We are building the SBOM manually in our Jenkins pipeline with cdxgen and then using the plugin to upload to Dependency Track. It is working successfully in another job, for some reason we are getting this error:
Earlier in the pipeline we can see bom.json is generated, is a non-zero file size and sitting in the same directory referenced above:
![image](https://private-user-images.githubusercontent.com/48829375/254599137-99d886bd-3803-4a95-891b-0e447786e840.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjE1MjE2NjYsIm5iZiI6MTcyMTUyMTM2NiwicGF0aCI6Ii80ODgyOTM3NS8yNTQ1OTkxMzctOTlkODg2YmQtMzgwMy00YTk1LTg5MWItMGU0NDc3ODZlODQwLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MjElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzIxVDAwMjI0NlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTFlZGJjNjBiZDc5MTMzYTliMjU0YTRmM2M0YWQwM2MxYTQyNTQwZDBiZTNlNjhkMmViNWJhMGU4OGRlMjI4MGImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.rZjIBEEXx5QewRqL6LIA05NGGIybPMHjf_xXfxxDv3A)
Can you provide guidance on troubleshooting this error?
Environment
The text was updated successfully, but these errors were encountered: