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
Makefile target to build and push image for release #138
Conversation
Makefile
Outdated
@@ -12,17 +12,20 @@ | |||
# See the License for the specific language governing permissions and | |||
# limitations under the License. | |||
# | |||
.EXPORT_ALL_VARIABLES: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TIL
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
handy, isn't it?
For an example of the cloudbuild config, we have: Image promoter configuration: Release process: |
d559cf4
to
c6112a5
Compare
Looking good. I think we can iterate once we have cloudbuild enabled in test-infra? |
Yup. |
c6112a5
to
b6ad417
Compare
b6ad417
to
8827c3c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: M00nF1sh, nckturner 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 |
What type of PR is this?
/kind feature
What this PR does / why we need it:
We want to build and push containers using prow post-submits. This is a first pass at a script that takes care of tag format validation and passing GCR credentials to docker. Simplified version of the vsphere cloud provider release.sh script and makefile.
Which issue(s) this PR fixes:
Fixes #135
Special notes for your reviewer:
Does this PR introduce a user-facing change?: