[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] ECF project and Tycho

----- Original Message -----
> From: "Wim Jongman" <wim.jongman@xxxxxxxxx>
> To: "Eclipse Communication Framework (ECF) developer mailing list." <ecf-dev@xxxxxxxxxxx>
> Sent: Sunday, 9 November, 2014 7:59:12 PM
> Subject: Re: [ecf-dev] ECF project and Tycho
> 
> Yes this is what I had in mind. I don't mind getting the new VM from OSU
> neither. But I guess this will take some time to complete and the HIPP is
> there now.
> 

Hi Wim,

I can log into the HIPP instance (although I don't have permission to do anything), but I cannot log into the Jenkins at https://build.ecf-project.org/jenkins

Is there a way to request an account there to see the build output?

Mat


> it is some more work but also guarantees that the build is portable.
> 
> Cheers,
> 
> Wim
> 
> On Sun, Nov 9, 2014 at 8:49 PM, Scott Lewis < slewis@xxxxxxxxxxxxx > wrote:
> 
> 
> On 11/9/2014 11:31 AM, Wim Jongman wrote:
> 
> 
> 
> 
> Yes. Given that we already have our own website, builder, and test
> infrastructure, I don't see any advantages of creating/using a HIPP
> instance. And there are a lot of associated hassles if we were to do so
> (restrictions or complexity of distribution of non-EPL components, OSGi CT
> usage/testing, our support for other target platforms...e.g. Karaf, etc).
> Our HIPP already exists and is building some of our example stuff. Building
> the new tycho on our HIPP is better because it is sandboxed away from our
> main build server.
> 
> Once the Tycho build is running it is easy to restore it on the main build.
> 
> The missing link here Wim is that before we switch to a new Tycho-based
> build, it has to build/run/test all of the pieces of our build that cannot
> be run/tested on the HIPP instance:
> 
> 1) Non-EPL projects (e.g. JMS provider, MQTT provider)
> 2) OSGI CT (as per Markus' reply just now)
> 3) Discovery and other config needed for multi-process automated testing
> (e.g. dns, xmpp server, etc.)
> 
> I can see this working if the conversion process is:
> 
> a) Setup Tycho on HIPP instance and convert EF projects (ECF core,
> filetransfer, remote services, etc)
> b) Move setup to new VM on OSU OSL instance
> c) Do work to convert remaining proejcts (i.e. 1, 2, 3, and any others) to
> Tycho build
> d) Switch to depending upon the new Tycho build
> 
> If this is what you have intended then that's fine. But it seems to me extra
> work to do 'a', as opposed to just jumping to/starting with 'b'.
> 
> 
> Scott
> 
> ______________________________ _________________
> ecf-dev mailing list
> ecf-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/ mailman/listinfo/ecf-dev
> 
> 
> _______________________________________________
> ecf-dev mailing list
> ecf-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/ecf-dev