-
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
Flake: hack/build-images.sh fails with "stat examples/gitserver/bin/gitserver: no such file or directory" #17684
Comments
return "${result}"
exited with status 1.
this PR was for release-3.7 branch and it doesn't have #17373 |
@tnozicka The release-3.7 branch is no longer pulled into OCP 3.7 and should not be targeted by PRs. You will need to PR against ose/enterprise-3.7 . |
@jupierce what if I want to fix origin as well, why shouldn't I target release-3.7? 3.7 is our latest stable release in upstream. I am not sure why we don't auto pull stuff from origin release-3.7 anymore but I'll send it manually there too. |
@tnozicka We just don't offer long term support in these branches. |
If previous releases in origin are of any guidance we used to release x.x.1 at least. I went though the history and we've released (1.1.6, 1.2.2, 1.3.3, 1.4.1, 1.5.1, 3.6.1). @smarterclayton is 3.7 in origin really dead? Are we sure there won't be 3.7.1? For one I know that 3.7.0 How can we mark 3.7 as not supported without having a newer release? |
The branch should be fixed, but gitserver should be removed. |
We ensure oc cluster up works on origin release branches, and occasionally
do security fixes. So we should fix things broken on the branch that would
make cutting a release for security harder.
On Dec 21, 2017, at 12:30 PM, Tomáš Nožička <[email protected]> wrote:
If previous releases in origin are of any guidance we used to release x.x.1
at least. I went though the history and we've released (1.1.6, 1.2.2,
1.3.3, 1.4.1, 1.5.1, 3.6.1).
@smarterclayton <https://github.com/smarterclayton> is 3.7 in origin really
dead? Are we sure there won't be 3.7.1? For one I know that 3.7.0 oc
cluster up is completely broken on some platforms (#17638
<#17638>)
How can we mark 3.7 as not supported without having a newer release?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#17684 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABG_p-o77QYleJJE8lFXrrO-47dJzrOeks5tCpXGgaJpZM4Q7JT4>
.
|
https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/17620/test_pull_request_origin_extended_conformance_install/3776/
The text was updated successfully, but these errors were encountered: