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

Consolidate PR and real release workflows #1845

Merged
merged 4 commits into from
Dec 21, 2021

Conversation

imjasonh
Copy link
Collaborator

Description

  • push and sign an image tagged for every push to the repo (e.g., merged PRs)
  • push and sign for tag pushes, with release tags
  • build but don't push for opened PRs

WIP because I'm pushing to GHCR to test for now.

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

  • Includes unit tests
  • Adds integration tests if needed.

See the contribution guide for more details.

Reviewer Notes

  • The code flow looks good.
  • Unit tests and or integration tests added.

Release Notes

Images are built, tagged and signed for every push to the repo

cc @mattmoor @priyawadhwa

- push and sign an image tagged for every push to the repo (e.g., merged PRs)
- push and sign for tag pushes, with release tags
- build but don't push for opened PRs

WIP because I need to test more with the tag flow, but pushes worked in
my fork.
Comment on lines +76 to +78
# https://github.com/docker/build-push-action/blob/master/docs/advanced/cache.md#github-cache
cache-from: type=gha
cache-to: type=gha,mode=max
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can we avoid the cache on releases?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

That feels a bit overly paranoid, but sure. Is there some public guidance around building release without caches that I can link to in a comment?

Copy link
Collaborator

Choose a reason for hiding this comment

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

It’s a strict interpretation of some of the higher SLSA levels, and one build being able to influence others.

@mattmoor
Copy link
Collaborator

one small bug and a nit, but otherwise LGTM

@mattmoor
Copy link
Collaborator

I can't check the reviewer boxes, since I'm not a maintainer, so cc @priyawadhwa

Copy link
Collaborator

@priyawadhwa priyawadhwa left a comment

Choose a reason for hiding this comment

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

Lgtm!!

@imjasonh imjasonh changed the title WIP: consolidate PR and real release workflows Consolidate PR and real release workflows Dec 21, 2021
@imjasonh imjasonh merged commit 6e500ec into GoogleContainerTools:master Dec 21, 2021
gcalmettes pushed a commit to gcalmettes/kaniko that referenced this pull request Dec 24, 2021
* WIP: consolidate PR and real release workflows

- push and sign an image tagged for every push to the repo (e.g., merged PRs)
- push and sign for tag pushes, with release tags
- build but don't push for opened PRs

WIP because I need to test more with the tag flow, but pushes worked in
my fork.

* apply release tags, uncomment kms stuff

* Tag images correctly during releases

* review feedback
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.

3 participants