On Thu, Nov 30, 2017 at 8:59 PM, Marek Jelen <[email protected]> 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- > logs/origin/openshift-origin-client-tools-v3.7.0-latest-linux-64bit.tar.gz > https://storage.googleapis.com/origin-ci-test/branch- > logs/origin/openshift-origin-client-tools-v3.7.0-release- > linux-64bit.tar.gz > > where “latest” would track development builds and “stable” would track > tagged releases. > > It would be pretty convenient for scripting. not to have to employ logic > to figure out latest build ids or release hashes. > +1. It would be great if we get such known paths. Path containing ids or hash will definitely create issue in scripting. If not then, we need to move to solution suggested by @graham or similar ones. > > -- > > MAREK JELEN > > DEVELOPER ADVOCATE, OPENSHIFT > > https://www.redhat.com/ > > [email protected] M: +420724255807 > > On 30 November 2017 at 16:13:08, Clayton Coleman ([email protected]) > 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. > > On Nov 30, 2017, at 2:05 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/ > 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/ > > Thanks, > > Lala > > _______________________________________________ > 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 > > > _______________________________________________ > dev mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > > Regards, Budh Ram Gurung
_______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
