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

Perform provenance verification in dedicated scratch dir #2297

Merged
merged 1 commit into from
Oct 25, 2021

Conversation

puerco
Copy link
Member

@puerco puerco commented Oct 24, 2021

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

This PR modifies the provenance code to perform the staged artifact verification in a dedicated scratch directory inside the Cloud Build workspace.

Before, the scratch directory was created without control in the current directory, resulting in the bucket copy being performed in the git tree.

Signed-off-by: Adolfo García Veytia (Puerco) [email protected]

Which issue(s) this PR fixes:

Part of: #2267
Follow-up to #2283

Special notes for your reviewer:

/assign @Verolop @justaugustus @cpanato
/cc @kubernetes/release-engineering
/priority important-soon

Does this PR introduce a user-facing change?

During `anago.release`, krel will now download and perform the staged artifact verification in a dedicated directory in the Cloud Build workspace. 

This commit modifies the provenance code to perform the artifact
verification from stage in a dedicated scratch directory inside the
Cloud Build workspace.

Before, the scratch directory was created without control in the CWD
resulting the bucket copy beign performed in the git tree.

Signed-off-by: Adolfo García Veytia (Puerco) <[email protected]>
@k8s-ci-robot k8s-ci-robot added the release-note Denotes a PR that will be considered when it comes time to generate release notes. label Oct 24, 2021
@k8s-ci-robot k8s-ci-robot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Oct 24, 2021
@k8s-ci-robot k8s-ci-robot requested a review from a team October 24, 2021 20:27
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. area/release-eng Issues or PRs related to the Release Engineering subproject sig/release Categorizes an issue or PR as relevant to SIG Release. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Oct 24, 2021
@puerco puerco added this to the v1.23 milestone Oct 24, 2021
@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 25, 2021
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: puerco, saschagrunert

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 merged commit cbcbf48 into kubernetes:master Oct 25, 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. area/release-eng Issues or PRs related to the Release Engineering subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm "Looks good to me", indicates that a PR is ready to be merged. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/release Categorizes an issue or PR as relevant to SIG Release. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants