|Re: [ecf-dev] Create a build based on tycho|
Scott Lewis <slewis@xxxxxxxxxxxxx> writes:
> I don't have the personal resources to do the necessary releng work
> myself without some commitment of support, but so far that support
> doesn't appear to be forthcoming.
> If you are willing to contribute releng work on ECF we would be happy
> to incorporate it.Â Actually, it would be very helpful to extend our
> build to many of the repos at github as well .
Neither do I have resources to come up with a solution that will be able
to replace an existing build system in a single shot.
> In short, ECF is lacking resources sufficient to effect these releng
> changes. If you can provide resources or know how that might be done,
> please contact me directly.
It looks like chicken-n-egg problem - speaking for myself, a complete
solution is too complex to implement, OTOH there is nothing I can
improve. That's why I was asking if there are any plans. I like Mat's
incremental approach (see commit message ), so my proposal would be:
- setup a new CI job that will build ECF with Tycho;
- make resulting p2 repository available (i.e., like last successful
Â build's artifact );
- enable Gerrit trigger for this job to build Gerrit changes to ECF;
- merge Mat's contribution.
These steps will allow to move forward, step by step, without breaking
current workflow and consuming limited resources of the core development
team including you.
Does it make sense?
> On 5/11/2016 2:02 PM, Mykola Nikishov wrote:
>> I'm wondering what is the plan to move forward with Tycho-based build
>> As I understand, it's not possible/desirable to switch from b3 to Tycho
>> in a single shot and Tycho-based build should prove it can replace an
>> existing one. Ideally, for the same Git commit, a p2 repository built by
>> Tycho should be identical, bit-by-bit, to official p2 repository (not
>> sure if it's possible, though).
>> So, the first thing that is missing, from my PoV, is Gerrit trigger that
>> will build new changes with Tycho and publish a p2 repository.
>>  https://bugs.eclipse.org/bugs/show_bug.cgi?id=396457