Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add fossa cli config for license scanning #892

Merged
merged 5 commits into from
Sep 18, 2019

Conversation

lukpueh
Copy link
Member

@lukpueh lukpueh commented Jul 4, 2019

Fixes issue #:
None

Description of the changes being introduced by the pull request:
The new way of doing license scans with fossa, uses the fossa cli (e.g. on the CI/CD build) and an API token to publish to app.fossa.com. This PR adds a fossa config file and updates the travis config file accordingly. See commit messages for details.

Note that we can't keep the FOSSA_API_TOKEN secret (e.g. via Travis encrypted or repository setting environment variables), because those are not available for Travis builds of PRs from forked repository, which we need to support. Therefor we use a non-confidential push only API token.

For details see and

Please verify and check that the pull request fulfills the following
requirements
:

  • The code follows the Code Style Guidelines
  • Tests have been added for the bug fix or new feature
  • Docs have been added for the bug fix or new feature

@lukpueh lukpueh closed this Jul 4, 2019
@lukpueh lukpueh reopened this Jul 4, 2019
@lukpueh lukpueh force-pushed the add-fossa-cli branch 3 times, most recently from 5674e8d to 737a411 Compare July 4, 2019 11:34
@lukpueh
Copy link
Member Author

lukpueh commented Jul 4, 2019

Things to consider:

  • We should deprecate (delete) the old TUF Fossa page in favor of the new TUF Fossa page, once this PR is merged.
  • GitHub integration of the new page, to e.g. post status checks, does not seem to work.
  • This PR configures Travis to trigger one license scan per build (per version), which IMO makes sense because different versions, have different dependencies. However, the Fossa dashboard seems to only always show the latest scan, and, moreover, does not make it clear which build provided it.
  • This PR configures fossa to use a pip analysis strategy, but this also includes test/build dependencies in the scan (pylint, bandit, tox, etc...). It might make more sense to use requirements strategy...

@caniszczyk
Copy link

I would remove the test/build deps in the scan

Generated by running `fossa init`.

Signed-off-by: Lukas Puehringer <lukas.puehringer@nyu.edu>
For fossa Python project configruation see:
https://github.com/fossas/fossa-cli/blob/master/docs/integrations/python.md

Signed-off-by: Lukas Puehringer <lukas.puehringer@nyu.edu>
Note that we can't keep the FOSSA_API_TOKEN secret (e.g. via
Travis encrypted or repository setting environment variables),
because those are not available for PRs from forked repository.
Therefor we use a non-confidential push only API token.

For details see https://docs.fossa.com/docs/travisci and
https://docs.fossa.com/docs/api-reference#section-push-only-api-token

Signed-off-by: Lukas Puehringer <lukas.puehringer@nyu.edu>
Signed-off-by: Lukas Puehringer <lukas.puehringer@nyu.edu>
Before we used pip analysis strategy, which also includes
test/build dependencies in the scan (pylint, bandit, tox, etc...).

Signed-off-by: Lukas Puehringer <lukas.puehringer@nyu.edu>
@lukpueh lukpueh merged commit 21c3285 into theupdateframework:develop Sep 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants