Test-infra: prow should have better introspection

Created on 5 Oct 2017 · 11Comments · Source: kubernetes/test-infra

@rmmh brought up some ideas for improving prow introspection today, writing down what I remember here:

deck should serve config.yaml and plugins.yaml
- possibly deck should also be able to serve selected subsets of these since they're huge and growing (seperate discussions about orthogonaly improving this)
deck should serve recent events (trigger events etc?)
it should be easier to view a specific job's configuration (possibly somewhat covered in https://github.com/kubernetes/test-infra/pull/4881, but we might be able to do better)

Possibly other things I'm forgetting...

areprow help wanted kinvelocity-improvement lifecyclrotten prioritbacklog

Source

BenTheElder

👍2

All 11 comments

deck should serve config.yaml and plugins.yaml

That could be useful, and it's pretty easy to do.

possibly deck should also be able to serve selected subsets of these since they're huge and growing (seperate discussions about orthogonaly improving this)

They'll shrink eventually(TM).

deck should serve recent events (trigger events etc?)

Not sure how useful that is. They're in the logs if you need to see them. Not only that but we wouldn't be able to provide any guarantees about this.

it should be easier to view a specific job's configuration (possibly somewhat covered in #4881, but we might be able to do better)

That's not a bad idea, related sorta to the first one.

spxtr on 5 Oct 2017

👍1

We do serve the serialized config now, but I didn't get to plugins.yaml or anything more complex.

BenTheElder on 11 Dec 2017

We have log tracing now, the config is hosted, and @stevekuznetsov has been mentioning uploading the spec. hopefully when we get our init / sidecar containers we can have the uploader store the prow job and then close this out.

BenTheElder on 8 Mar 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 6 Jun 2018

/remove-lifecycle stale

stale and help-wanted don't go hand in hand :)

nikhita on 13 Jun 2018

Perhaps we should freeze help wanted?

On Wed, Jun 13, 2018, 08:58 Nikhita Raghunath notifications@github.com
wrote:

/remove-lifecycle stale

stale and help-wanted don't go hand in hand :)

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/test-infra/issues/4891#issuecomment-396991599,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA4Bq4fyKI2EnAKtV5__6YuQFzc-GGs9ks5t8Ta0gaJpZM4PvkPl
.

BenTheElder on 13 Jun 2018

👍1

@rmmh since patched bootstrap to upload the pod .yaml dumped from the running job into artifacts/ which is pretty handy. we should consider something like this in the podutils... @cjwagner @paulangton

BenTheElder on 2 Jul 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 30 Sep 2018

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

fejta-bot on 30 Oct 2018

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

fejta-bot on 30 Nov 2018

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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.