Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cleanup oc version output #10602

Conversation

juanvallejo
Copy link
Contributor

@juanvallejo juanvallejo commented Aug 23, 2016

Related BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1368913

openshift version returns unformatted "GitVersion".

This patch prints a cleaner output of the server version in oc version
and openshift version commands.

Before

$ openshift version

openshift v1.3.0-alpha.0+1605423-dirty
kubernetes v1.3.0+507d3a7
etcd 2.3.0+git
After

$ openshift version

openshift v1.3.0-alpha.0
kubernetes v1.3.0+507d3a7
etcd 2.3.0+git`

$ oc version

oc v1.3.0-alpha.0
kubernetes v1.3.0+507d3a7
features: Basic-Auth

Server https://10.13.137.149:8443
openshift v1.3.0-alpha.0
kubernetes v1.3.0+507d3a7

cc @fabianofranz

@juanvallejo juanvallejo force-pushed the jvallejo_update-oc-version-output branch from 141219b to 869596f Compare August 23, 2016 19:45
Related BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1368913

`openshift version` returns unformatted "GitVersion".

This patch prints a cleaner output of the server version in `oc version`
and `openshift version` commands.

Before
`$ openshift version`
```
openshift v1.3.0-alpha.0+1605423-dirty
kubernetes v1.3.0+507d3a7
etcd 2.3.0+git
```

After
`$ openshift version`
```
openshift v1.3.0-alpha.0
kubernetes v1.3.0+507d3a7
etcd 2.3.0+git`
```

`$ oc version`
```
oc v1.3.0-alpha.0
kubernetes v1.3.0+507d3a7
features: Basic-Auth

Server https://10.13.137.149:8443
openshift v1.3.0-alpha.0
kubernetes v1.3.0+507d3a7
```
@juanvallejo juanvallejo force-pushed the jvallejo_update-oc-version-output branch from 869596f to 3968408 Compare August 23, 2016 19:46
@liggitt
Copy link
Contributor

liggitt commented Aug 23, 2016

no, we want the git commit, and the indication that the build was from a dirty repo

@liggitt
Copy link
Contributor

liggitt commented Aug 23, 2016

that is an indication that the build process is dirtying the working dir, which is concerning

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants