Skip to content

Move verify-upstream-commits to a separate make target #12118

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

Closed

Conversation

soltysh
Copy link
Contributor

@soltysh soltysh commented Dec 2, 2016

One another cherry-pick of #12056 against 1.3 branch, per @liggitt request. @stevekuznetsov fyi as well

@liggitt
Copy link
Contributor

liggitt commented Dec 2, 2016

[test]

@soltysh
Copy link
Contributor Author

soltysh commented Dec 5, 2016

Flake #10951

re-[test]

@openshift-bot
Copy link
Contributor

Evaluated for origin test up to fbec109

@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/test FAILURE (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/12001/) (Base Commit: 0955c1d)

@soltysh
Copy link
Contributor Author

soltysh commented Dec 5, 2016

Hmmm... the failures are not related to the changes I've introduced. I wonder if test worked with 1.3 in the first place, @stevekuznetsov you might know?

@stevekuznetsov
Copy link
Contributor

Origin's tests are not set up to handle 1.3 -- we are testing everything with Docker 1.12, etc. Until I have more bandwidth or someone volunteers to help these tests are going to remain mostly meaningless.

@soltysh
Copy link
Contributor Author

soltysh commented Dec 5, 2016

With that in mind I'm closing this PR, if needed ping me I'll re-open it.

@soltysh soltysh closed this Dec 5, 2016
@liggitt
Copy link
Contributor

liggitt commented Dec 5, 2016

tests were passing in the 1.3 release branch as of #11308 (comment)

is there a way to lock the image used to test? it's important we have the ability to verify fixes against our release branches

@liggitt liggitt reopened this Dec 5, 2016
@liggitt
Copy link
Contributor

liggitt commented Dec 5, 2016

@danmcp, thoughts on origin CI jobs for release branches?

@danmcp
Copy link
Contributor

danmcp commented Dec 5, 2016

@liggitt I would worry about the maintenance of them. There are already a lot of previous release combinations we have a had time keeping running with the correct docker/golang.

@stevekuznetsov
Copy link
Contributor

@liggitt there is a way, and we are using it in the OSE queue today. We just have to build from base_ami on every job -- if you have the time, looking at the OSE pull request job should give you the info you need to reconfigure all of Origin's jobs to do this. I just don't have the bandwidth for it right now.

@smarterclayton
Copy link
Contributor

We really need release branches with CI. Probably needs to be folded into the other work going on though given limited attention.

@stevekuznetsov
Copy link
Contributor

With the caveat that run time will be much longer, we should be able to copy the logic from the OSE job to build non-branch tests from the base AMI. We'd also need to update Rosie.

@smarterclayton
Copy link
Contributor

smarterclayton commented Dec 30, 2016 via email

@soltysh
Copy link
Contributor Author

soltysh commented Mar 2, 2017

Closing due to age.

@soltysh soltysh closed this Mar 2, 2017
@soltysh soltysh deleted the separate_verifycommits13 branch March 2, 2017 13:49
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.

6 participants