On Thu, Nov 30, 2017 at 1:38 PM, Graham Dumpleton <[email protected]> wrote:
> Personally I would have had a GitHub repo under Minishift org which had > just an index file in it keyed by versions which are known to work and can > be used. Minishift could then pull down the index file, get the URL for > where binary is, which could be anywhere, and then fetch it from there. > > Yes it means the index file has to be updated, but being a separate repo > that doesn't need a new Minishift release and could be done at any time. > > This would also solve problem of GitHub API rate limiting when Minishift > is behind a corporate fire wall, something that I believe was affecting the > Minishift developers themselves early on. Not sure if workaround for that > was worked out. > > So as is always the case, a level of indirection solves all problems. > > Graham > That's a good suggestion. However I believe it is in OpenShift Origin's favor if we can have predictable download links. It will help users automate the download of oc binary. > > > On 30 Nov 2017, at 6:43 pm, Jean-Francois Maury <[email protected]> wrote: > > Could be doable through the Github API but since 3.7.0 seems binary are > not hosted anymore on Github > > On Thu, Nov 30, 2017 at 8:04 AM, Lalatendu Mohanty <[email protected]> > wrote: > >> Hi, >> >> 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/o >> rigin/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_cros >> s/1032/artifacts/zips/ >> >> Thanks, >> >> Lala >> >> _______________________________________________ >> dev mailing list >> [email protected] >> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >> >> > > > -- > JEFF MAURY > Red Hat > > <https://www.redhat.com/> > > [email protected] > <https://red.ht/sig> > <https://redhat.com/summit> > @redhatjobs <https://twitter.com/redhatjobs> redhatjobs > <https://www.facebook.com/redhatjobs/> @redhatjobs > <https://instagram.com/redhatjobs> > _______________________________________________ > dev mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > > >
_______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
