Dependency Track Pipeline
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 21
- Forks
- 5
- Avg merge
- 5h 36m
- Merged PRs (30d)
- 3
Description
Our dependency track pipeline doesnt seem to work anymore the last time a new sbom was pushed was
3 - 4 months ago
A pretty similar pipeline was created in pcts where the only major change is that we format our sbom like a json instead of a xml
The secrets should be in bitwarden in the pcts collection
Todos:
- Check if the secrets are correct
- Update the pipeline to use json format instead of sbom
- If it still doesnt work search for other solutions
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by comparing this repository's dependency-track pipeline with the similar pcts PR 77, then verify the secrets in the Bitwarden pcts collection and inspect the current SBOM format. Done means a newly generated JSON SBOM is accepted and reaches Dependency-Track; if it still fails, document the alternative solution investigated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, json
- Domain
- ci-cd, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100