BuildSource: mark secrets field as omitempty

[php-coder]

Prior this change secrets field was always serialized and was shown in build logs and available to assemble scripts as part of BUILD variable. I don't see a reason why we need to serialize it and print as "secrets":null.

PTAL @bparees

[bparees]

lgtm [merge]

[openshift-bot]

[Test]ing while waiting on the merge queue

[openshift-bot]

continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/6969/) (Image: devenv-rhel7_4682)

[bparees]

FAILURE: Swagger spec is out of date. Please run hack/update-generated-swagger-spec.sh

[php-coder]

Ah, I'm sorry. Should be fixed now.

[openshift-bot]

Evaluated for origin test up to 7f52ce2

[openshift-bot]

continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/6969/)

[bparees]

[merge]

Ben Parees | OpenShift

On Jul 27, 2016 7:05 AM, "OpenShift Bot" [email protected] wrote:

continuous-integration/openshift-jenkins/test SUCCESS (
https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/6969/)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#10038 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEvl3qUyh-lAZN3lLerFoKAphY9M5YCaks5qZztwgaJpZM4JVIdq
.

[openshift-bot]

Evaluated for origin merge up to 7f52ce2