Build and build config describers are poorly laid out and not useful to users

[smarterclayton]

Probably need to be reorganized for structure, a lot of the duplicate fields are confusing or not properly presented. Engage UX and others. A lot of fields can probably be unified, or simplified.

[bparees]

@fabianofranz I won't be at the CLI meeting tomorrow morning but this might be a good topic.

[bparees]

for reference here's the current BC output:

$ oc describe bc ruby-sample-build
Name:           ruby-sample-build
Created:        8 minutes ago
Labels:         app=ruby-sample-build,name=ruby-sample-build,template=application-template-stibuild
Annotations:        openshift.io/generated-by=OpenShiftNewApp
Latest Version:     2
Strategy:       Source
Source Type:        Git
URL:            https://github.com/openshift/ruby-hello-world.git
From Image:     ImageStreamTag ruby-20-centos7:latest
Output to:      ImageStreamTag origin-ruby-sample:latest
Triggered by:       ImageChange, Config
Webhook GitHub:     https://10.192.210.243:8443/oapi/v1/namespaces/test/buildconfigs/ruby-sample-build/webhooks/secret101/github
Webhook Generic:    https://10.192.210.243:8443/oapi/v1/namespaces/test/buildconfigs/ruby-sample-build/webhooks/secret101/generic

Build           Status      Duration    Creation Time
ruby-sample-build-2     complete    2m24s       2015-11-09 16:54:57 -0500 EST
ruby-sample-build-1     failed      4m10s       2015-11-09 16:49:04 -0500 EST

and build output:

$ oc describe build ruby-sample-build-2
Name:       ruby-sample-build-2
Created:    2 minutes ago
Labels:     app=ruby-sample-build,buildconfig=ruby-sample-build,name=ruby-sample-build,openshift.io/build-config.name=ruby-sample-build,template=application-template-stibuild
Annotations:    openshift.io/build.number=2
Build Config:   ruby-sample-build
Started:    2015-11-09 16:55:02 -0500 EST
Finished:   2015-11-09 16:57:26 -0500 EST
Duration:   2m24s
Build Pod:  ruby-sample-build-2-build
Strategy:   Source
Source Type:    Git
URL:        https://github.com/openshift/ruby-hello-world.git
From Image: DockerImage openshift/ruby-20-centos7@sha256:20098eb056620c0ceade04b4bec642fb89c8f3361e89e6ff4729b273f2c799ed
Output to:  ImageStreamTag origin-ruby-sample:latest
Push Secret:    builder-dockercfg-n3m9h
Status:     Complete
Events:
  FirstSeen LastSeen    Count   From            SubobjectPath   Reason      Message
  ─────────   ────────    ───── ────            ───────────── ──────      ───────
  2m        2m      1   {kubelet bparees.rh}    implicitly required container POD   Pulled      Container image "openshift/origin-pod:latest" already present on machine
  2m        2m      1   {scheduler }                Scheduled   Successfully assigned ruby-sample-build-2-build to bparees.rh
  2m        2m      1   {kubelet bparees.rh}    implicitly required container POD   Created     Created with docker id 07c1907a67b8
  2m        2m      1   {kubelet bparees.rh}    spec.containers{sti-build}      Pulled      Container image "openshift/origin-sti-builder:latest" already present on machine
  2m        2m      1   {kubelet bparees.rh}    implicitly required container POD   Started     Started with docker id 07c1907a67b8
  2m        2m      1   {kubelet bparees.rh}    spec.containers{sti-build}      Created     Created with docker id 27f199d5b554
  2m        2m      1   {kubelet bparees.rh}    spec.containers{sti-build}      Started     Started with docker id 27f199d5b554
  29s       29s     1   {kubelet bparees.rh}    implicitly required container POD   Killing     Killing with docker id 07c1907a67b8

[mfojtik]

@bparees the output is also different for other build strategies, right? For example in Dockerfile strategy we display the Dockerfile (but we don't format it ;-), etc

[bparees]

@soltysh @jwforres fyi

[jwforres]

Current state of the web console for reference

[smarterclayton]

Given more time (not saying we do that here), I'd make the strategy section
much more important, with Source being dramatically different than Docker
being dramatically different than custom, with a description of what it
does, and specific layout of the inputs. I.e.:

Docker

Build the provided source code using a direct Docker build.
FROM # updated automatically
<if custom Dockerfile, show here>

Source

Take the base image and upload source into it, resulting in a runnable image
Base image php:5.4 which currently will setup - PHP 5.4.3 with all APC
extensions
...

On Tue, Nov 17, 2015 at 11:10 AM, Jessica Forrester <
notifications@github.com> wrote:

Current state of the web console for reference

[image: 20151117_111004_]
https://cloud.githubusercontent.com/assets/1467629/11216931/dd665a7c-8d1b-11e5-825a-e433da76fb42.png
[image: 20151117_111020_]
https://cloud.githubusercontent.com/assets/1467629/11216932/dd6656b2-8d1b-11e5-8ae3-3f7c4283ab9b.png

—
Reply to this email directly or view it on GitHub
#5247 (comment).