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.

Sign up for GitHub

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

Jump to bottom

Manually push 1.18.0-alpha.4 tag and cut 1.18.0-alpha.5 release #985

Closed
10 tasks done
hasheddan opened this issue Feb 7, 2020 · 6 comments
Closed
10 tasks done

Manually push 1.18.0-alpha.4 tag and cut 1.18.0-alpha.5 release #985

hasheddan opened this issue Feb 7, 2020 · 6 comments
Assignees
@justaugustus @hasheddan
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject sig/release Categorizes an issue or PR as relevant to SIG Release.
Milestone
v1.18

Comments

@hasheddan
Copy link
Contributor

hasheddan commented Feb 7, 2020 •
edited by justaugustus
Loading

Scheduled to happen: Tue, 2020-02-11 Wed, 2020-02-12

  • Screenshot unhealthy release branch testgrid boards and add them as a comment
  • Stage & release
  • Send notification email

Release steps (v1.18.0-alpha.5)

Step Command Link Start Duration Succeeded?
Mock stage ./gcbmgr stage master --buildversion=$(curl -Ls https://dl.k8s.io/ci/latest.txt) https://console.cloud.google.com/cloud-build/builds/0a39e34c-3ef8-4698-a947-fb43310279f0?project=kubernetes-release-test February 12, 2020 at 2:09:16 PM GMT-5 47 min 9 sec yes
Mock release ./gcbmgr release master --buildversion=v1.18.0-alpha.4.4+6541758fd4d9fc https://console.cloud.google.com/cloud-build/builds/8e90b7a0-d507-470e-9bdd-3acc71b8b366?project=kubernetes-release-test February 12, 2020 at 2:57:39 PM GMT-5 17 min 42 sec yes
Stage ./gcbmgr stage master --buildversion=v1.18.0-alpha.4.4+6541758fd4d9fc --nomock https://console.cloud.google.com/cloud-build/builds/e38e54ba-183d-4b1a-9096-931cba92f1fb?project=kubernetes-release-test February 12, 2020 at 3:24:33 PM GMT-5 46 min 26 sec yes
Release ./gcbmgr release --nomock master --buildversion=v1.18.0-alpha.4.4+6541758fd4d9fc https://console.cloud.google.com/cloud-build/builds/f78989b3-da80-4970-b78d-87ddae7149b2?project=kubernetes-release-test February 13, 2020 at 1:19:48 AM GMT-5 18 min yes
Notify --  https://groups.google.com/d/topic/kubernetes-announce/wahAv9Gc3d0/discussion   -- yes

Action items

Open questions

/area release-eng
/milestone v1.18
/assign
cc: @kubernetes/release-team @kubernetes/release-engineering
@hasheddan hasheddan added sig/release Categorizes an issue or PR as relevant to SIG Release. area/release-eng Issues or PRs related to the Release Engineering subproject labels Feb 7, 2020
@k8s-ci-robot k8s-ci-robot added this to the v1.18 milestone Feb 7, 2020
@justaugustus justaugustus mentioned this issue Feb 7, 2020
Closed
@justaugustus
Copy link
Member

Release is blocked on kubernetes/release#1080.

This was referenced Feb 11, 2020
Merged
Merged
@justaugustus justaugustus changed the title Cut 1.18.0-alpha.4 release Manually push 1.18.0-alpha.4 tag and cut 1.18.0-alpha.5 release Feb 13, 2020
@justaugustus
Copy link
Member

I took over this release due to the need to cut a manual tag and wanting to watch any potential issues that could've arisen from that.
/assign

@justaugustus
Copy link
Member

Didn't have a chance to snapshot the boards ahead of the release, but here's their current status:

Testgrid dashboards for master

Boards checked for FAILING:

2020-02-13 03:13:31-0500 FAILING sig-release-master-informing#capa-conformance-stable-k8s-master [testgrid]

sig-release-master-informing#capa-conformance-stable-k8s-master

2020-02-13 03:13:31-0500 FAILING sig-release-master-informing#capg-conformance-stable-k8s-master [testgrid]

sig-release-master-informing#capg-conformance-stable-k8s-master

2020-02-13 03:13:32-0500 FAILING sig-release-master-informing#gce-cos-master-reboot [testgrid]

sig-release-master-informing#gce-cos-master-reboot

2020-02-13 03:13:29-0500 FAILING sig-release-master-informing#gce-cos-master-serial [testgrid]

sig-release-master-informing#gce-cos-master-serial

2020-02-13 03:13:29-0500 FAILING sig-release-master-informing#gce-windows-1909-master [testgrid]

sig-release-master-informing#gce-windows-1909-master

2020-02-13 03:13:31-0500 FAILING sig-release-master-informing#gce-windows-2019-containerd-master [testgrid]

sig-release-master-informing#gce-windows-2019-containerd-master

2020-02-13 03:13:29-0500 FAILING sig-release-master-informing#gce-windows-2019-master [testgrid]

sig-release-master-informing#gce-windows-2019-master

@justaugustus
Copy link
Member

Scrollback from the manual tag push of v1.18.0-alpha.4 I did to resolve kubernetes/release#1080:

$ git remote add danger [email protected]:kubernetes/kubernetes.git
$ git remote update
Fetching origin
Fetching upstream
Fetching danger
From github.com:kubernetes/kubernetes
 * [new branch]              feature-rate-limiting    -> danger/feature-rate-limiting
 * [new branch]              feature-serverside-apply -> danger/feature-serverside-apply
 * [new branch]              feature-workload-ga      -> danger/feature-workload-ga
 * [new branch]              master                   -> danger/master
 * [new branch]              release-0.10             -> danger/release-0.10
 * [new branch]              release-0.12             -> danger/release-0.12
 * [new branch]              release-0.13             -> danger/release-0.13
 * [new branch]              release-0.14             -> danger/release-0.14
 * [new branch]              release-0.15             -> danger/release-0.15
 * [new branch]              release-0.16             -> danger/release-0.16
 * [new branch]              release-0.17             -> danger/release-0.17
 * [new branch]              release-0.18             -> danger/release-0.18
 * [new branch]              release-0.19             -> danger/release-0.19
 * [new branch]              release-0.20             -> danger/release-0.20
 * [new branch]              release-0.21             -> danger/release-0.21
 * [new branch]              release-0.4              -> danger/release-0.4
 * [new branch]              release-0.5              -> danger/release-0.5
 * [new branch]              release-0.6              -> danger/release-0.6
 * [new branch]              release-0.7              -> danger/release-0.7
 * [new branch]              release-0.8              -> danger/release-0.8
 * [new branch]              release-0.9              -> danger/release-0.9
 * [new branch]              release-1.0              -> danger/release-1.0
 * [new branch]              release-1.1              -> danger/release-1.1
 * [new branch]              release-1.10             -> danger/release-1.10
 * [new branch]              release-1.11             -> danger/release-1.11
 * [new branch]              release-1.12             -> danger/release-1.12
 * [new branch]              release-1.13             -> danger/release-1.13
 * [new branch]              release-1.14             -> danger/release-1.14
 * [new branch]              release-1.15             -> danger/release-1.15
 * [new branch]              release-1.16             -> danger/release-1.16
 * [new branch]              release-1.17             -> danger/release-1.17
 * [new branch]              release-1.2              -> danger/release-1.2
 * [new branch]              release-1.3              -> danger/release-1.3
 * [new branch]              release-1.4              -> danger/release-1.4
 * [new branch]              release-1.5              -> danger/release-1.5
 * [new branch]              release-1.6              -> danger/release-1.6
 * [new branch]              release-1.6.3            -> danger/release-1.6.3
 * [new branch]              release-1.7              -> danger/release-1.7
 * [new branch]              release-1.8              -> danger/release-1.8
 * [new branch]              release-1.9              -> danger/release-1.9
$ git checkout master
Already on 'master'
$ git reset --hard danger/master
HEAD is now at 50c8f73a4b2 Merge pull request #88017 from feiskyer/fix-409
$ git tag -s v1.18.0-alpha.4 HEAD^
$ git push --dry-run danger v1.18.0-alpha.4 
To github.com:kubernetes/kubernetes.git
 * [new tag]                 v1.18.0-alpha.4 -> v1.18.0-alpha.4
$ git push danger v1.18.0-alpha.4 
Enumerating objects: 21957, done.
Counting objects: 100% (9472/9472), done.
Delta compression using up to 12 threads
Compressing objects: 100% (2077/2077), done.
Writing objects: 100% (6165/6165), 1.85 MiB | 2.28 MiB/s, done.
Total 6165 (delta 4734), reused 5043 (delta 3969)
remote: Resolving deltas: 100% (4734/4734), completed with 1486 local objects.
To github.com:kubernetes/kubernetes.git
 * [new tag]                 v1.18.0-alpha.4 -> v1.18.0-alpha.4

@justaugustus justaugustus mentioned this issue Feb 13, 2020
Merged
@justaugustus
Copy link
Member

AIs are complete.
/close

@k8s-ci-robot
Copy link
Contributor

@justaugustus: Closing this issue.

In response to this:

AIs are complete.
/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
Assignees

@justaugustus justaugustus

@hasheddan hasheddan

Labels
area/release-eng Issues or PRs related to the Release Engineering subproject sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
None yet
Milestone
v1.18
Development

No branches or pull requests
3 participants
@justaugustus @k8s-ci-robot @hasheddan