Test-infra: Document criteria for kubernetes/kubernetes merge-blocking jobs
i.e. when shall we add/remove a presubmit job from queue blocking
cc @spiffxp I remember you have mentioned similar topic, not sure if it's documented anywhere
krzyzacy
All 16 comments
This is basically about
- extracting info from the google doc at kubernetes/sig-release#24
- figuring out where to put it
- PR it to that place
- making sure folks are aware of the criteria
- making sure folks know how/when we're enforcing those criteria
spiffxp
on 27 Feb 2018
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
fejta-bot
on 28 May 2018
this is recently relevant to @shyamjvs with scalability presubmits for example
/remove-lifecycle stale
I know there was a discussion around this, and some initial attempt to document, but we should get that finalized and committed somewhere official..
BenTheElder
on 29 May 2018
/milestone 1.12
spiffxp
on 23 Aug 2018
/assign @spiffxp
assume you have the most ideas here
krzyzacy
on 1 Sep 2018
/milestone v1.13
OK for really reals this time :P
spiffxp
on 29 Sep 2018
/remove-help
spiffxp
on 29 Sep 2018
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
fejta-bot
on 28 Dec 2018
/remove-lifecycle stale
idealhack
on 28 Dec 2018
/lifecycle frozen
/milestone v1.14
FYI @BenTheElder @fejta
Oh look, another milestone bump. The deal is that I'd like for us to implement measurement and enforcement of the criteria laid out for release-blocking. I would then expect merge blocking criteria to be basically the same, but with tighter numbers.
We also have aspirations to move away from the use of clouds in merge-blocking jobs, in the spirit of failing fast, and deferring the slower/flakier jobs later. The difficult balance here is this harkens back to the bad old days where slow/flaky postsubmit builds blocked the queue, which caused much pain for everyone.
spiffxp
on 3 Jan 2019
/milestone v1.15
spiffxp
on 7 May 2019
/milestone v1.16
/sig testing
/sig release
spiffxp
on 6 Aug 2019
/remove-lifecycle frozen
/cc @BenTheElder
FYI @kubernetes/ci-signal
spiffxp
on 11 Sep 2020
/milestone v1.20
Maybe we can do this before the 3 year anniversary? (because adding a milestone has _totally_ made this happen in the past)
spiffxp
on 11 Sep 2020
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
fejta-bot
on 10 Dec 2020
/remove-lifecycle stale
/milestone v1.21
Nope. Fourth year's a charm.
spiffxp
on 8 Jan 2021
Related issues
spiffxp
路
3Comments
sjenning
路
4Comments
fen4o
路
4Comments
cblecker
路
4Comments
Aisuko
路
3Comments
Most helpful comment
/lifecycle frozen
/milestone v1.14
FYI @BenTheElder @fejta
Oh look, another milestone bump. The deal is that I'd like for us to implement measurement and enforcement of the criteria laid out for release-blocking. I would then expect merge blocking criteria to be basically the same, but with tighter numbers.
We also have aspirations to move away from the use of clouds in merge-blocking jobs, in the spirit of failing fast, and deferring the slower/flakier jobs later. The difficult balance here is this harkens back to the bad old days where slow/flaky postsubmit builds blocked the queue, which caused much pain for everyone.