[Devtools] OpenShift 3.2

[Burr Sutter]

On Wed, May 11, 2016 at 11:33 AM, Lalatendu Mohanty <lmohanty at redhat.com>
wrote:

> On 05/11/2016 08:32 PM, Praveen Kumar wrote:
>
>>
>> ----- Original Message -----
>> | From: "Burr Sutter" <bsutter at redhat.com>
>> | To: devtools at redhat.com
>> | Sent: Wednesday, May 11, 2016 8:13:28 PM
>> | Subject: [Devtools] OpenShift 3.2
>> |
>> | What is the plan for getting 3.2 into the CDK?
>>
>> For testing purpose you can use vagrant file available on
>> redhat-developer-tooling github[0]. You have to set
>> *OPENSHIFT_VAGRANT_USE_OSE_3_2=true* environment variable before doing
>> *vagant up*. We still don't have any CDK build to cache OSE-3.2 images
>> because of a issue with brew[1], we will try again if that is resolved now.
>>
>> [0]
>> https://github.com/redhat-developer-tooling/openshift-vagrant/blob/master/cdk-v2/Vagrantfile
>> [1] https://projects.engineering.redhat.com/browse/RCM-1329
>>
>> Burr,
>
> The above issue came because we tried to use the docker registry which
> hosts the nightly 3.2 builds. Post OSE 3.2 GA  and it is available from Red
> Hat registry it would be relatively easy for us to cache it in to CDK.
>
> Do you need nightly OSE 3.2 builds in nightly/weekly CDK builds or OSE 3.2
> GA version?
>

I would be comfortable with the GA version.  Just looking for the timing of
the deliverable.   I am trying to push many other parties to consider the
CDK as a "first-class citizen" for running their stuff (e.g. Vert.x,
Hawkular, APIMan, Fabric8) but often those teams want the "latest &
greatest".


>
> Thanks,
>
> Lala
>
> _______________________________________________
> Devtools mailing list
> Devtools at redhat.com
> https://www.redhat.com/mailman/listinfo/devtools
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/devtools/attachments/20160511/36f4763b/attachment.htm>