decouple cut-stable-release from snap_k8s_track_list

Bug #2016189 reported by Kevin W Monroe
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Charmed Kubernetes Testing
Fix Released
Medium
Adam Dyess

Bug Description

This should either take a param for the k8s version or use the K8S_NEXT_VERSION enum. It should also do some error checking (e.g. does `release_x.xx` branch exist already?) and stop relying on the order of a list to make the release branches:

https://github.com/charmed-kubernetes/jenkins/blob/1.27/jobs/sync-upstream/sync.py#L83

Changed in charmed-kubernetes-testing:
milestone: none → 1.28
status: New → Triaged
Revision history for this message
Adam Dyess (addyess) wrote :
Changed in charmed-kubernetes-testing:
status: Triaged → In Progress
assignee: nobody → Adam Dyess (addyess)
importance: Undecided → Medium
Adam Dyess (addyess)
Changed in charmed-kubernetes-testing:
milestone: 1.28 → 1.28+ck1
Adam Dyess (addyess)
Changed in charmed-kubernetes-testing:
status: In Progress → Fix Committed
Adam Dyess (addyess)
tags: added: backport-needed
Revision history for this message
Adam Dyess (addyess) wrote :
tags: removed: backport-needed
Adam Dyess (addyess)
Changed in charmed-kubernetes-testing:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.