/assign
/assign @BenTheElder
Also delete *json.yaml files :smiling_imp:
see: https://github.com/kubernetes/test-infra/issues/4871 instead of #4430
I guess one reason for this is that you can add comments?
I guess one reason for this is that you can add comments?
Yes, which is super useful for explaining exceptional configurations. :+1:
Does this include jobs/config.json? Could use an area/jobs label if so
Does this include jobs/config.json? Could use an area/jobs label if so
Very much so, job configs don't really need to be two files if we are all-in on Prow in our shiny future.
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
/remove-lifecycle stale
boskos config will be migrated to yaml in https://github.com/kubernetes/test-infra/pull/6676
I have one issue left there. I did not update the python script that looks for existing projects and recreate the resources.yaml.
config.json will be gone after we split up prow/config.yaml, and we can embed kubetest/scenario args there
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
/remove-lifecycle stale
it's getting there!
/milestone 1.12
config.json has 4 ghost entry used by bootstrap_test.py... which probably not worth spend time to untangle and we can ditch the file when we switch to podutils. I'll declare victory here.
:tada:
Most helpful comment
I guess one reason for this is that you can add comments?