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 blackduck scan to run on master #6130

Merged
merged 31 commits into from
Dec 3, 2020

Conversation

dasormeter
Copy link
Collaborator

@dasormeter dasormeter commented May 27, 2020

THIS PR

  • Enable blackduck scan to run only on linux
  • Include bazel haskell library scan with current snapshot verison of hub detect
  • bazel jvm and npm and all other build tool scans runs as a second round but to the same version and project

TODO (follow-on PRs)

@garyverhaegen-da
Copy link
Contributor

I don't think our CI has access to DACH-NY.

ci/build-unix.yml Outdated Show resolved Hide resolved
ci/build-unix.yml Outdated Show resolved Hide resolved
@dasormeter
Copy link
Collaborator Author

I don't think our CI has access to DACH-NY.

that particular repo in DACH-NY is public so should be okay

@dasormeter dasormeter mentioned this pull request May 27, 2020
5 tasks
@garyverhaegen-da
Copy link
Contributor

Also note that despite the description of the PR, as it stands it would run on every PR and master commit, and on both Linux and macOS.

@dasormeter
Copy link
Collaborator Author

Also note that despite the description of the PR, as it stands it would run on every PR and master commit, and on both Linux and macOS.

yeah just testing the run first, will then move it to the daily job. i'll mark it as DRAFT so it is clear it is not yet to be merged

@dasormeter dasormeter marked this pull request as draft May 27, 2020 22:30
@dasormeter dasormeter self-assigned this Jun 2, 2020
ci/build-unix.yml Outdated Show resolved Hide resolved
ci/build-unix.yml Outdated Show resolved Hide resolved
ci/build-unix.yml Outdated Show resolved Hide resolved
ci/build-unix.yml Outdated Show resolved Hide resolved
@dasormeter dasormeter marked this pull request as ready for review June 18, 2020 16:55
@dasormeter dasormeter changed the title add blackduck scan add blackduck scan to run on master Jun 18, 2020
Pipfile Show resolved Hide resolved
env:
BLACKDUCK_HUBDETECT_TOKEN: $(BLACKDUCK_HUBDETECT_TOKEN)


Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do these depend on the build having run? If not, could we move this to a separate job?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@garyverhaegen-da yeah it does depend on the build having run since we need the bazel build resolution and node modules and other build output to be interrogated to get the full list of libraries used

Copy link
Contributor

@cocreature cocreature left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Requesting changes until I understand how I can see results and why we want this to break our master builds but not our PR builds.

Copy link
Contributor

@garyverhaegen-da garyverhaegen-da left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I really don't like the idea that we have a check that can fail on master but is not checked on PRs.

@garyverhaegen-da
Copy link
Contributor

garyverhaegen-da commented Jun 19, 2020

I'm a bit confused by the change to use $(System.PullRequest.SourceBranch). I thought the conclusion of our discussions was to instead move this to a scheduled (daily) run on master, which would thus not be in the context of a PR and therefore not have that variable set.

@dasormeter
Copy link
Collaborator Author

I'm a bit confused by the change to use $(System.PullRequest.SourceBranch). I thought the conclusion of our discussions was to instead move this to a scheduled (daily) run on master, which would thus not be in the context of a PR and therefore not have that variable set.

experimenting with runs that fail on policy violation on PRs to see how long it takes

@dasormeter dasormeter force-pushed the enable-blackduck branch 3 times, most recently from 4fc7d3b to c71d956 Compare June 25, 2020 14:54
Comment on lines +221 to +223
- template: ../bash-lib.yml
parameters:
var_name: bash_lib
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- template: ../bash-lib.yml
parameters:
var_name: bash_lib

You're not using that library.

@dasormeter dasormeter changed the base branch from master to enable-blackduck-daily-scan December 3, 2020 18:58
@dasormeter dasormeter merged commit fbea7d5 into enable-blackduck-daily-scan Dec 3, 2020
@dasormeter dasormeter deleted the enable-blackduck branch December 3, 2020 18:59
dasormeter added a commit that referenced this pull request Dec 3, 2020
* add blackduck scan

* disable go scanning
exclude entire language-support/ts directory for node scanning
break to multiple lines to make command line params easier to parse

* Increase timeout for blackduck binary scan

* update blackduck scan config

* remove some exclusions, force python3

* exclude GO until path to go executable can be resolved

* added readme explanation of why we want this file

* fail in case of policy violation

* ensure haskell bazel scan completes before running second round scan for bazel jvm and node and other langs

* trigger notices file gen to ensure BOM complete

* remove trailing end of lines

* run with latest detect version and unique code location name changes to wrapper script

* Add blackduck to daily compat job

* DO NOT MERGE: condition false to disable other jobs for testing

* remove parameters not available to cronjob
mergify bot pushed a commit that referenced this pull request Dec 7, 2020
* add blackduck scan to run on master (#6130)

* add blackduck scan

* disable go scanning
exclude entire language-support/ts directory for node scanning
break to multiple lines to make command line params easier to parse

* Increase timeout for blackduck binary scan

* update blackduck scan config

* remove some exclusions, force python3

* exclude GO until path to go executable can be resolved

* added readme explanation of why we want this file

* fail in case of policy violation

* ensure haskell bazel scan completes before running second round scan for bazel jvm and node and other langs

* trigger notices file gen to ensure BOM complete

* remove trailing end of lines

* run with latest detect version and unique code location name changes to wrapper script

* Add blackduck to daily compat job

* DO NOT MERGE: condition false to disable other jobs for testing

* remove parameters not available to cronjob

* Revert changes to regular CI pipeline

CHANGELOG_BEGIN
CHANGELOG_END

Signed-off-by: Brian Healey <brian.healey@digitalasset.com>

* Do not get branch name from variable

* Upgrade com.fasterxml.jackson.core:jackson-databind to 2.12.0 to address security vulnerability

* Remove disabling of other jobs, set to branch to be used on prod runs

* Apply suggestions from code review

Co-authored-by: Gary Verhaegen <gary.verhaegen@digitalasset.com>

* Address code review comments

* Updated NOTICES file

* Run bazel build, update NOTICES file

* Correct dade-assist

* do not have perms to pipe to dev/null

* Add md file explaining how to update NOTICES file

* Add instructions for running blackduck locally

* Add a link to full security-blackduck readme

Co-authored-by: Gary Verhaegen <gary.verhaegen@digitalasset.com>
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.

4 participants