test: Test Security PR Checkpoints

[TopScrew]

Add risk dependencies and licenses for scanning and testing

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign wuhuizuo for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• change-insight/OWNERS
• tibuild/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

Sorry, some error happened!

[ti-chi-bot]

Hi @TopScrew. Thanks for your PR.

I'm waiting for a PingCAP-QE member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[TopScrew]

/test pull-security-scan

[ti-chi-bot]

@TopScrew: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test pull-security-scan

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[TopScrew]

/ok-to-test

[ti-chi-bot]

@TopScrew: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/ok-to-test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[purelind]

/ok-to-test

[TopScrew]

/test pull-security-scan

[ti-chi-bot]

@TopScrew: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test pull-scan-deps

Use /test all to run all jobs.

In response to this:

/test pull-security-scan

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[TopScrew]

/test pull-security-scan

[ti-chi-bot]

@TopScrew: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test pull-scan-deps

Use /test all to run all jobs.

In response to this:

/test pull-security-scan

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[TopScrew]

/retest

[ti-chi-bot]

@TopScrew: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-scan-deps	2eeb4a0	link	true	/test pull-scan-deps

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.