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

2017-12-01 Thread Budh Ram Gurung
On Fri, Dec 1, 2017 at 4:21 AM, Clayton Coleman wrote: > Binaries are published. > Thanks Clayton. Now, minishift start --openshift-version v3.7.0 is working fine as expected. This give us some time to think [1] for the strategy to handle this in future minishift

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

2017-12-01 Thread Marek Jelen
Thanks! -- MAREK JELEN DEVELOPER ADVOCATE, OPENSHIFT https://www.redhat.com/ mje...@redhat.comM: +420724255807 On 30 November 2017 at 23:51:15, Clayton Coleman (ccole...@redhat.com) wrote: > Binaries are published. > > On Nov 30, 2017, at 10:11 AM, Clayton Coleman

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

2017-11-30 Thread Clayton Coleman
Binaries are published. On Nov 30, 2017, at 10:11 AM, Clayton Coleman wrote: 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.

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

2017-11-30 Thread Lalatendu Mohanty
On Thu, Nov 30, 2017 at 8:41 PM, Clayton Coleman wrote: > 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 > Please do publish them to github for 3.7. It will give us sometime to

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

2017-11-30 Thread Budh Ram Gurung
On Thu, Nov 30, 2017 at 8:59 PM, Marek Jelen wrote: > Hi Clayton, > > when uploaded to GCS, could the binaries be as well uploaded to some well > known paths? Something like > > https://storage.googleapis.com/origin-ci-test/branch- >

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

2017-11-30 Thread Clayton Coleman
Yes, that is one of the considerations. I can’t promise anything at the moment. On Nov 30, 2017, at 10:29 AM, Marek Jelen wrote: Hi Clayton, when uploaded to GCS, could the binaries be as well uploaded to some well known paths? Something like

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

2017-11-30 Thread Marek Jelen
Hi Clayton, when uploaded to GCS, could the binaries be as well uploaded to some well known paths? Something like https://storage.googleapis.com/origin-ci-test/branch-logs/origin/openshift-origin-client-tools-v3.7.0-latest-linux-64bit.tar.gz

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

2017-11-30 Thread Clayton Coleman
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 wrote: Hi, Till v3.7.0-rc.0

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

2017-11-30 Thread Graham Dumpleton
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

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

2017-11-29 Thread Jean-Francois Maury
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 wrote: > Hi, > > Till v3.7.0-rc.0 release oc binaries were published in github release > page [1] but with 3.7.0 the

Unpredictable oc binary path for Origin version v3.7.0

2017-11-29 Thread Lalatendu Mohanty
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