Skip to content

Private Triage Process and Vulnerability Scanning for Build Time Dependencies #5853

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

Closed
wants to merge 3 commits into from

Conversation

PushkarJ
Copy link
Member

@PushkarJ PushkarJ commented Jun 22, 2021

@k8s-ci-robot
Copy link
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@k8s-ci-robot k8s-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Jun 22, 2021
@k8s-ci-robot k8s-ci-robot added sig/security Categorizes an issue or PR as relevant to SIG Security. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jun 22, 2021
@PushkarJ
Copy link
Member Author

PushkarJ commented Jun 22, 2021

@navidshaikh PTAL: 2314fea

@PushkarJ PushkarJ marked this pull request as ready for review June 22, 2021 21:15
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 22, 2021
@PushkarJ
Copy link
Member Author

PushkarJ commented Jul 9, 2021

This PR: kubernetes/test-infra#22833, enables notification and private triage after which the category and its corresponding resolution is identified.

@PushkarJ PushkarJ changed the title SIG Security Tooling OWNERS and Vulnerability management docs Private Triage and Resolution Policy and Vulnerability Scanning for Build Time Dependencies Jul 30, 2021
@PushkarJ PushkarJ changed the title Private Triage and Resolution Policy and Vulnerability Scanning for Build Time Dependencies Private Triage Policy and Vulnerability Scanning for Build Time Dependencies Jul 30, 2021
@PushkarJ
Copy link
Member Author

/hold until #5941 is merged

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 10, 2021
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: PushkarJ

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

The pull request process is described here

Needs approval from an approver in each of these files:

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 12, 2021
@PushkarJ
Copy link
Member Author

/hold remove

@PushkarJ
Copy link
Member Author

/hold

@PushkarJ
Copy link
Member Author

/assign @PushkarJ

1. Periodic CI scanning job
2. Policy for vulnerability resolution
@PushkarJ PushkarJ force-pushed the sec-tooling-vuln branch 3 times, most recently from 4bfe603 to 1c1dec5 Compare August 20, 2021 20:52
@PushkarJ PushkarJ changed the title Private Triage Policy and Vulnerability Scanning for Build Time Dependencies Private Triage Process and Vulnerability Scanning for Build Time Dependencies Aug 24, 2021
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 22, 2021
@MadhavJivrajani
Copy link
Contributor

/remove-lifecycle stale
/lifecycle frozen
@PushkarJ anything else that needs to be done here?

@k8s-ci-robot
Copy link
Contributor

@MadhavJivrajani: The lifecycle/frozen label cannot be applied to Pull Requests.

In response to this:

/remove-lifecycle stale
/lifecycle frozen
@PushkarJ anything else that needs to be done 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/test-infra repository.

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 22, 2021
@PushkarJ
Copy link
Member Author

PushkarJ commented Nov 22, 2021

@MadhavJivrajani I will be closing this shortly and create a new one (or two) on https://github.com/kubernetes/sig-security as most of the content on deliverables has moved there for SIG Security.

@PushkarJ
Copy link
Member Author

New PR: kubernetes/sig-security#16 replaces the need for this PR. Hence, closing!

@PushkarJ PushkarJ closed this Nov 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. sig/security Categorizes an issue or PR as relevant to SIG Security. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants