;> will break the model about current separation on ignite and ignite-3,
>>>>>>> ignite-extensions and so-on.
>>>>>>> As we have different repositories for different parts of our project
>>>> and
>>>>>>> TeamC
ssues — we still will be able to
> >> use
> >>> it
> >>>>> with creating branches with the same name on both project and TC
> >>> repository.
> >>>>>
> >>>>>> On 17 Dec 2021, at 14:06, Pavel Tupitsyn
> &g
t;> it
>>>>> with creating branches with the same name on both project and TC
>>> repository.
>>>>>
>>>>>> On 17 Dec 2021, at 14:06, Pavel Tupitsyn
>> wrote:
>>>>>>
>>>>>> Witaliy,
>>>&g
ues — we still will be able to
>>> use
>>>> it
>>>>>> with creating branches with the same name on both project and TC
>>>> repository.
>>>>>>
>>>>>>> On 17 Dec 2021, at 14:06, Pavel Tupitsyn
>>> wrot
repository is created
>>>>>> only in the master branch
>>>>>
>>>>> I strongly suggest avoiding a separate repository for project settings.
>>>>> Let's store them in https://github.com/apache/ignite
>>>>>
>>>&g
Dec 2021, at 14:06, Pavel Tupitsyn
> > wrote:
> > > >>>
> > > >>> Witaliy,
> > > >>>
> > > >>>> repository is created
> > > >>>> only in the master branch
> > > >>>
>
r project
> settings.
> > >>> Let's store them in https://github.com/apache/ignite
> > >>>
> > >>> *1. We should be able to test code changes together with CI/CD
> > changes.*
> > >>> *2. We should be able to have different project settings
rent
> >>> branches.*
> >>>
> >>> For example, I may remove or rename a module in ignite/master branch
> and
> >>> update TC project accordingly,
> >>> while it continues to work as before in ignite-2.12 branch where we
> >
I may remove or rename a module in ignite/master branch and
>>> update TC project accordingly,
>>> while it continues to work as before in ignite-2.12 branch where we
>> prepare
>>> the release with older code.
>>>
>>> This is super impor
tinues to work as before in ignite-2.12 branch where we
> prepare
> > the release with older code.
> >
> > This is super important and this is how most other projects do it (from
> my
> > experience).
> >
> >
> >
> > On Fri, Dec 17, 2021 at 11:12 AM Виталий
ore in ignite-2.12 branch where we prepare
> the release with older code.
>
> This is super important and this is how most other projects do it (from my
> experience).
>
>
>
> On Fri, Dec 17, 2021 at 11:12 AM Виталий Осилов
> wrote:
>
>> Dear Ignite Co
is how most other projects do it (from my
experience).
On Fri, Dec 17, 2021 at 11:12 AM Виталий Осилов
wrote:
> Dear Ignite Community!
>
> I propose for discussion the conception of using two TeamCity servers with
> a roadmap.
> https://ci.ignite.apache.org/
> https://ci2.i
Dear Ignite Community!
I propose for discussion the conception of using two TeamCity servers with
a roadmap.
https://ci.ignite.apache.org/
https://ci2.ignite.apache.org/
Storing project settings.
Servers synchronize configurations between themselves using the version
control-storing DSL
13 matches
Mail list logo
