Skip to content

sig-release: Add ci-kubernetes-build-canary to canary release tooling#13340

Closed
justaugustus wants to merge 1 commit intokubernetes:masterfrom
justaugustus:k-r-canary
Closed

sig-release: Add ci-kubernetes-build-canary to canary release tooling#13340
justaugustus wants to merge 1 commit intokubernetes:masterfrom
justaugustus:k-r-canary

Conversation

@justaugustus
Copy link
Copy Markdown
Member

@justaugustus justaugustus commented Jul 6, 2019 •
edited
Loading

ci-kubernetes-build-canary builds and publishes artifacts to a canary GCS bucket
using the tooling on the master branch of kubernetes/release. The goal here is
to allow Release Engineering to improve the current toolset without impacting CI
for the entire project.

While this job should closely mirror the configuration of ci-kubernetes-build,
it should differ in a few ways:

  • runs on CI ref of kubernetes/kubernetes
  • runs on master branch of kubernetes/release
  • publishes artifacts to a different GCS bucket
  • alerts Release Managers instead of the Release Team

ref: kubernetes/release#816

Signed-off-by: Stephen Augustus [email protected]

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jul 6, 2019
@k8s-ci-robot k8s-ci-robot requested review from amwat and ixdy July 6, 2019 14:44
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

k8s-ci-robot commented Jul 6, 2019

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: justaugustus

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

The pull request process is described here

Details 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/M Denotes a PR that changes 30-99 lines, ignoring generated files. area/config Issues or PRs related to code in /config sig/release Categorizes an issue or PR as relevant to SIG Release. sig/testing Categorizes an issue or PR as relevant to SIG Testing. labels Jul 6, 2019
@justaugustus
Copy link
Copy Markdown
Member Author

justaugustus commented Jul 6, 2019 •
edited
Loading

/hold
(I think there are a few things like buckets to configure before this could work)

@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 Jul 6, 2019
@justaugustus justaugustus mentioned this pull request Jul 6, 2019
Closed
8 tasks
@justaugustus
sig-release: Add ci-kubernetes-build-canary to canary release tooling
9c026fb 
ci-kubernetes-build-canary builds and publishes artifacts to a canary GCS bucket
using the tooling on the master branch of kubernetes/release. The goal here is
to allow Release Engineering to improve the current toolset without impacting CI
for the entire project.

While this job should closely mirror the configuration of ci-kubernetes-build,
it should differ in a few ways:
 - runs on CI ref of kubernetes/kubernetes
 - runs on master branch of kubernetes/release
 - publishes artifacts to a different GCS bucket
 - alerts Release Managers instead of the Release Team

ref: k/release#816

Signed-off-by: Stephen Augustus <[email protected]>
@justaugustus
Copy link
Copy Markdown
Member Author

justaugustus commented Jul 6, 2019

Set job to point at kubernetes/release@aa5d559.
This is a commit where the tooling is known to be broken, so we can see the failure before fixing it.

@justaugustus
Copy link
Copy Markdown
Member Author

justaugustus commented Jul 6, 2019

/area release-eng

@k8s-ci-robot k8s-ci-robot added the area/release-eng Issues or PRs related to the Release Engineering subproject label Jul 6, 2019
@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 13, 2019
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

k8s-ci-robot commented Jul 13, 2019

@justaugustus: PR needs rebase.

Details

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.

@fejta-bot
Copy link
Copy Markdown

fejta-bot commented Oct 11, 2019

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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 Oct 11, 2019
@justaugustus
Copy link
Copy Markdown
Member Author

justaugustus commented Oct 19, 2019

I'm going to attack this a different way. First attempt at this is here: kubernetes/release#900

/close

@k8s-ci-robot
Copy link
Copy Markdown
Contributor

k8s-ci-robot commented Oct 19, 2019

@justaugustus: Closed this PR.

Details

In response to this:

I'm going to attack this a different way. First attempt at this is here: kubernetes/release#900

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@amwat amwat Awaiting requested review from amwat

@ixdy ixdy Awaiting requested review from ixdy

Assignees

No one assigned

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/config Issues or PRs related to code in /config 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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@justaugustus @k8s-ci-robot @fejta-bot