-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Do not check builds/details in build by strategy admission control #6678
Conversation
Evaluated for origin testonlyextended up to 1e9cd7f |
@@ -49,6 +49,11 @@ func (a *buildByStrategy) Admit(attr admission.Attributes) error { | |||
if resource := attr.GetResource(); resource != buildsResource && resource != buildConfigsResource { | |||
return nil | |||
} | |||
// Explicitly exclude the builds/details subresource because it's only | |||
// updating commit info and cannot change build type. | |||
if attr.GetResource() == "builds" && attr.GetSubresource() == "details" { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/"builds"/buildsResource/
one nit and lgtm. over to @smarterclayton |
also fyi test+testonlyextended doesn't make much sense :) |
1e9cd7f
to
378876c
Compare
updated. Should the tag be "testextended" ? |
Approved, merge when ready |
"[test][extended:core(builds)]" is what you wanted (but it's also what you got as a result of what you did.. just saying the onlyextended does not actually limit it to only extended tests if you also put a test tag on it) |
[test] |
@smarterclayton for approval to prevent regression in builders updating build details |
nm, saw comment |
@csrwng those extended test failures look scary, can you take a look? |
@csrwng this one: https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin/8636/consoleFull going to run it again in the meantime after cleaning up the test tags. [test] |
@bparees after the failure below every test fails. It looks like the server stopped responding after that point. I didn't see this when I ran extended tests earlier today, so I think something must have gone wrong with the vm.
|
ok we'll see what the current run yields. |
[test] On Fri, Jan 15, 2016 at 6:35 PM, OpenShift Bot [email protected]
|
@smarterclayton extended passed in one of the tests: and failed with the same exact error above in the other test:
|
I don't think that error is related to this pull |
[test] |
Evaluated for origin test up to 378876c |
I wanted to kick off regular tests without the extended tests and then extended tests separately, but it doesn't look like it's letting me do that. It kicked off both again. |
continuous-integration/openshift-jenkins/test ABORTED (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/53/) (Extended Tests: core(builds)) |
Started 2 sets of tests manually... |
It aggregates all the tags. If you want extended separate you can add the Ben Parees | OpenShift
|
1 for 2 on the test job, 2 for 2 on extended. test failure looks unrelated. |
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge_pull_requests_origin/4647/) (Image: devenv-rhel7_3166) |
Evaluated for origin merge up to 378876c |
Merged by openshift-bot
Fixes BZ 1298861
This was a regression introduced by #6576.