Build pod controller: Always set pod name annotation on build

[csrwng]

When cloning a build, the build pod name annotation is not getting updated on the cloned build because one from the cloned build exists.

[csrwng]

@bparees This is an unexpected effect of my recent change to the build pod controller. There's no reason not to overwrite the annotation. Previously I was not setting it if it already exists, but found it's not the right thing to do when dealing with a build that has been cloned. ptal.

[bparees]

Lgtm [merge]

[bparees]

Flake #9959

[merge]

Ben Parees | OpenShift

On Jul 30, 2016 12:15 AM, "OpenShift Bot" [email protected] wrote:

continuous-integration/openshift-jenkins/merge FAILURE (
https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/7196/)

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

[csrwng]

flake #9959
[merge]

[csrwng]

Flake #9959
[merge]

[bparees]

[merge]

Ben Parees | OpenShift

On Jul 30, 2016 3:20 PM, "OpenShift Bot" [email protected] wrote:

continuous-integration/openshift-jenkins/merge FAILURE (
https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/7209/)

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

[bparees]

https_://github.com/ http://github.com/__openshift__/origin/issues/9959_

[merge]

Ben Parees | OpenShift

On Jul 30, 2016 5:15 PM, "OpenShift Bot" [email protected] wrote:

continuous-integration/openshift-jenkins/merge FAILURE (
https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/7211/)

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

[csrwng]

#9959
[merge]

[csrwng]

#9775
[merge]

[csrwng]

#9959
[merge]

[csrwng]

#9775
[merge]

[bparees]

#9959

[merge]

On Sun, Jul 31, 2016 at 11:40 PM, OpenShift Bot [email protected]
wrote:

continuous-integration/openshift-jenkins/merge FAILURE (
https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/7230/)

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

Ben Parees | OpenShift

[openshift-bot]

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

[bparees]

flake #9959
[merge]

[openshift-bot]

Evaluated for origin merge up to 30bae45

[openshift-bot]

[Test]ing while waiting on the merge queue

[csrwng]

issue with jenkins job post-build script
[merge]

[stevekuznetsov]

re[test]

[csrwng]

#7355
[test]

[openshift-bot]

Evaluated for origin test up to 30bae45

[openshift-bot]

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