Skip to content
This repository has been archived by the owner on Sep 24, 2021. It is now read-only.

Build container image on all pushes and publish image on push to master #75

Merged
merged 2 commits into from
Jul 8, 2019

Conversation

chuckha
Copy link
Contributor

@chuckha chuckha commented Jul 8, 2019

What this PR does / why we need it:
This PR starts addressing #67

Special notes for your reviewer:
This will build an image but will not push until it merges to master.

NONE

/assign @detiber

Sorry for all the spam >.< this one finally does what I want.

chuckha added 2 commits July 8, 2019 14:15
At the very least the login should succeed
Signed-off-by: Chuck Ha <chuckh@vmware.com>
@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jul 8, 2019
@k8s-ci-robot k8s-ci-robot requested review from detiber and vincepri July 8, 2019 18:27
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chuckha

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 approved Indicates a PR has been approved by an approver from all required OWNERS files. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jul 8, 2019
}

action "Docker Registry" {
uses = "actions/docker/login@86ff551d26008267bb89ac11198ba7f1d807b699"
secrets = ["DOCKER_USERNAME", "DOCKER_PASSWORD", "DOCKER_REGISTRY_URL"]
Copy link
Contributor

Choose a reason for hiding this comment

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

Are these injected automatically?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

oh no, they are not. I had to create the secrets as an admin. There is a better way to do it with gpg which we should probably look into and use a robot user for these values instead of my personal account

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Copy link
Contributor

Choose a reason for hiding this comment

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

oh, that's disappointing, it would be nice if there was cleaner integration with github package repository.

Copy link
Contributor

Choose a reason for hiding this comment

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

Can the GitHub Token secret be used for this purpose instead of adding additional secrets?

@ashish-amarnath
Copy link
Contributor

Should we also expect "Checks" to run on this PR? I see 0 Checks

@vincepri
Copy link

vincepri commented Jul 8, 2019

I assume tests and verification can happen at PR time (before merging). That said, I'm not opposed if we want to duplicate it in GitHub CI as well, but that might require a larger effort.

@ashish-amarnath
Copy link
Contributor

Also, I am not sure I understand the switch to github workflow thingy. Is this replacing prow/ test-infra tests we've been using so far? I didn't get that memo.

@detiber
Copy link
Contributor

detiber commented Jul 8, 2019

I think the idea was to only use GitHub Actions for doing pushes for the latest tag to the GitHub Package Repository rather than attempt to replicate or replace prow-based testing.

@chuckha
Copy link
Contributor Author

chuckha commented Jul 8, 2019

@ashish-amarnath this is only for container images. There is no good place to put a container image for projects in kubernetes-sigs. Github packages fills that need and along with the image promoter work we can get images into a kubernetes sanctioned gcr repo (eventually)

@amy
Copy link
Contributor

amy commented Jul 8, 2019

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 8, 2019
@k8s-ci-robot k8s-ci-robot merged commit 4db6777 into kubernetes-retired:master Jul 8, 2019
@chuckha chuckha deleted the chuckha-patch-1 branch August 16, 2019 02:29
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
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. lgtm Indicates that a PR is ready to be merged. 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