Test-infra: prow: deck: show overview page for a ProwJob
Right now we can see the full list of jobs that ran, but it would be great to be able to open up a single job and see at the very least the job specification that was used to run it -- the refs involved, etc.
/kind enhancement
/area prow
/cc @BenTheElder @qhuynh96
stevekuznetsov
All 18 comments
/assign
qhuynh96
on 15 Mar 2018
FWIW pjutil.JobSpec describes the job's variables, so exposing that would be a great start.
stevekuznetsov
on 15 Mar 2018
Probably doing this when I come back Australia :laughing:
qhuynh96
on 15 Mar 2018
Yeah! Or I can take a stab at it, too!
stevekuznetsov
on 16 Mar 2018
Do you want a linkable page on prow to show a job's details? If you click the rerun button and follow the link, you can see the pod spec.
rmmh
on 2 Apr 2018
Yes, a nice table with good formatting showing me what the job was that ran -- a step up in UX from the PodSpec.
stevekuznetsov
on 3 Apr 2018
/assign
stevekuznetsov
on 3 Apr 2018
I'm actively working on this.
stevekuznetsov
on 6 Apr 2018
Thanks Steve
qhuynh96
on 6 Apr 2018
@qhuynh96 will tag you for review when it's less rough, but code is at https://github.com/stevekuznetsov/test-infra/tree/skuznets/job-page and a prototype hosted at https://deck-test-ci.svc.ci.openshift.org/job
stevekuznetsov
on 6 Apr 2018
I just have a quick look at the prototype. Is Job Status going to display all jobs as Prow Status does?
qhuynh96
on 6 Apr 2018
Intent is for it to be searchable, right now supports by job/id or org/repo/author, etc.
stevekuznetsov
on 6 Apr 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 5 Jul 2018
/remove-lifecycle stale
/assign @paulangton
On Thu, Jul 5, 2018, 08:02 fejta-bot notifications@github.com wrote:
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
https://github.com/fejta.
/lifecycle stale—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/test-infra/issues/7299#issuecomment-402752671,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA4Bq_yS_jM9nTMIWD1jZHcelGeharH7ks5uDiqTgaJpZM4SskWC
.
BenTheElder
on 5 Jul 2018
/unassign
stevekuznetsov
on 5 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 3 Oct 2018
This is #9374
/close
stevekuznetsov
on 4 Oct 2018
@stevekuznetsov: Closing this issue.
In response to this:
This is #9374
/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.
k8s-ci-robot
on 4 Oct 2018
Related issues
spzala
·
4Comments
xiangpengzhao
·
3Comments
cjwagner
·
3Comments
lavalamp
·
3Comments
benmoss
·
3Comments