UPDATE: 2020-09-01 main repo FOSSA check was fixed in #2347, but we need to add them to client libs as well.
We used to have FOSSA checks run on many repositories, but now it only runs on 5 of them (excluding the main one), and we cannot add more.
According to Kevin Wang from FOSSA:
I’ve noticed that Jaeger is enrolled in Automated Builds, which is not the ideal integration method.
In this model, fossa has to “guess” your dependencies by running every build path — its convenient since you can import code through the UI, but not scalable if you want to make continuous scans. You will likely experience performance issues and false positives if you run this on a large project per commit.
I suggest we integrate Jaeger through Provided Builds, where you deploy our build client (https://github.com/fossas/fossa-cli) into your CI to report dependencies back to fossa. This model should enable extremely fast and high scale builds/scans from within your CI.
See “from a local dev machine” in this article below:
https://docs.fossa.io/docs/importing-a-project
UPDATE: 2020-09-01 main repo FOSSA check was fixed in #2347, but we need to add them to client libs as well.
We used to have FOSSA checks run on many repositories, but now it only runs on 5 of them (excluding the main one), and we cannot add more.
According to Kevin Wang from FOSSA: