[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Unpredictable oc binary path for Origin version v3.7.0

I can publish them to github for 3.7.  We’re looking to reduce the amount of effort required to publish binaries so we can do it more often.  Expect binaries to be published to GCS in the future.

On Nov 30, 2017, at 2:05 AM, Lalatendu Mohanty <lmohanty redhat com> wrote:


Till v3.7.0-rc.0 release oc binaries were published in github release page [1] but with 3.7.0 the location has changed and causing minishift start --openshift-version v3.7.0 to fail.

From Minishift side we can change the code to point it to the new location but the new location is difficult to guess programmatically because It seems to contain a build id "1032" which makes it hard for third parties to determine.

If we can not predict the location then Minishift users can not use a new version of Origin without code changes in Minishift which is not desirable.

Filed an github issue on the same : https://github.com/openshift/origin/issues/17527

Is this going to be the normal going forward? Is there a way to predict the oc binary path from Origin version? Do you have plan to setup a mirror some place with predictable URL?

[1] https://github.com/openshift/origin/releases/tag/v3.7.0-rc.0

[2] https://gcsweb-ci.svc.ci.openshift.org/gcs/origin-ci-test/branch-logs/origin/v3.7.0/builds/test_branch_origin_cross/1032/artifacts/zips/



dev mailing list
dev lists openshift redhat com

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]