jaegertracing/jaeger

Improve FOSSA integration

Open

#2,432 opened on Aug 29, 2020

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Go (18,974 stars) (2,326 forks)batch import
help wanted

Description

Related to FOSSA scanning introduced in #2347

  • make the check go red when license violations are discovered
  • make the scan report easily accessible, e.g. by clicking on the Details next to the check, and/or posting a summary as a PR comment

Contributor guide

Tech stack
gogithub actions
Domain
securitydevopsci cd
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
understanding of CI/CDfamiliarity with FOSSAbasic Go knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Review the existing FOSSA integration introduced in PR #2347. Examine the CI configuration files (likely .github/workflows) to understand current scanning setup. The issue requests two changes: make the check fail (red) on license violations, and make the scan report accessible via Details link or PR comment. Look at FOSSA documentation for CI integration options and explore how to post a summary comment using GitHub Actions. Consider implementing a step that parses FOSSA output and posts a comment on the PR if violations are found.