Re: [cft-dev] Neon aggregate build: which URL to use: /milestones vs /1.

[Nieraj Singh <nsingh@xxxxxxxxxx>]

Hi Martin,

I've filed a bug to get write access to simrel build here:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=489244

Thanks.

-Nieraj

On Tue, Mar 8, 2016 at 3:57 AM, Martin Lippert <mlippert@xxxxxxxxx> wrote:
> Hey!
>
>> Thanks for the feedback. With 1.0.M6 released, we'll use this update
>> site for the Neon aggregate build contribution.
>>
>> We should be able to do the gerrit commit for Neon simrel build before
>> end of the week, hopefully within a day or so assuming commit rights
>> are in place.
>
> Do you already have a bugzilla in place to request commit rights for the simrel build?
> If not, please file that bugzilla and refer to the meeting minutes of the planning council meeting.
>
> Cheers,
> -Martin
>
>
>
>
>>
>>
>> On Mon, Mar 7, 2016 at 11:30 AM, Martin Lippert <mlippert@xxxxxxxxx> wrote:
>>> Hey!
>>>
>>> I am all fine with the various approaches. Please continue to use the one that works best for you.
>>>
>>> I would like to suggest to file a bug now to get commit rights to the aggregate build and start to push your aggregate build changes to that repo using via gerrit.
>>> That way we can get the aggregate build to work fine already some time before M6. I would suggest to get all this done by the end of this week. That would be great.
>>>
>>> Cheers,
>>> -Martin
>>>
>>>
>>>
>>>> Am 03.03.2016 um 23:33 schrieb Nieraj Singh <nsingh@xxxxxxxxxx>:
>>>>
>>>> In preparation to join Neon M6 aggregate build, we have to include a
>>>> repository URL for CFT that the aggregate build will use, and it
>>>> should be somewhat static, in the sense that it is not updated by
>>>> automated builds (e.g. nightly build).
>>>>
>>>> We have at least three options, all which appear to be used by
>>>> different projects already in aggregate build:
>>>>
>>>> 1. Use a general cft/milestones p2 repo , where the latest released
>>>> milestone is always available, and this is what Eclipse Simultaneous
>>>> Release milestone builds will use. This will therefore remain
>>>> unchanged across different simrel milestone builds. So for each simrel
>>>> milestone, it will always use cft/milestones update site.
>>>>
>>>> 2. A specific CFT milestone p2 repo that uses a released milestone
>>>> version, which means for each simultaneous release we have to update
>>>> the simrel aggregate build.
>>>>
>>>> Example: for Neon M6, we use a cft/1.0.M6, for Neon M7, we use a
>>>> cft/1.0.M7, etc..
>>>>
>>>> 3. Use a very specific p2 URL that includes the build ID (e.g. date)
>>>> so that if we have to respin, we have to update the simrel aggregate
>>>> build with the new URL and that way we know that the simrel build used
>>>> the respin.
>>>>
>>>>
>>>> Right now we are going with option 2, and will include an cft/1.0.M6
>>>> update site for Neon simrel M6. The goal is to contribute this into
>>>> aggregate build by Monday March 7.
>>>>
>>>> If you have a different opinion, please post it here before March 7.
>>>> _______________________________________________
>>>> cft-dev mailing list
>>>> cft-dev@xxxxxxxxxxx
>>>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>>>> https://dev.eclipse.org/mailman/listinfo/cft-dev
>>>
>>> _______________________________________________
>>> cft-dev mailing list
>>> cft-dev@xxxxxxxxxxx
>>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>>> https://dev.eclipse.org/mailman/listinfo/cft-dev
>> _______________________________________________
>> cft-dev mailing list
>> cft-dev@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/cft-dev
>
> _______________________________________________
> cft-dev mailing list
> cft-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cft-dev