fuel-dev team mailing list archive

[Dmitry Burmistrov <dburmistrov@xxxxxxxxxxxx>]

Mike, every merge in fuel-* project triggers our job, which
immediatelly builds all changed packages. We can block mirroring and
iso building jobs while our job is running.

On Thu, Mar 20, 2014 at 11:28 AM, Oleg Gelbukh <ogelbukh@xxxxxxxxxxxx> wrote:
> Building those packages could be inserted in a chain of jobs that produces
> ISO pretty easily, IMO.
>
> -Oleg
>
>
> On Thu, Mar 20, 2014 at 11:23 AM, Mike Scherbakov <mscherbakov@xxxxxxxxxxxx>
> wrote:
>>
>> Dmitry,
>> do I get you right if I say that the ISO we will be building in CI will be
>> taking packages from OBS?
>> Does it mean, that new changes merged into master for nailgun/astute,
>> won't appear in ISO unless I file a ticket to OSCI team to rebuild the
>> packages?
>>
>> Thanks,
>>
>>
>> On Wed, Mar 19, 2014 at 1:19 PM, Dmitry Pyzhov <dpyzhov@xxxxxxxxxxxx>
>> wrote:
>>>
>>> Guys,
>>>
>>> As you know, nailgun and naily are installed on master node into virtual
>>> environments from source packages. It is convenient for developers and
>>> nightmare for continuous integration.
>>>
>>> We almost finished creation of rpm packages all the things. But here we
>>> face an issue: we need additional time for make system change. It will allow
>>> developer to build private versions of packages from the source code.
>>> Without this update the only option for creation of packages is via our
>>> ci/cd infrastructure.
>>>
>>> In ideal world we should wait till make system update. But we are limited
>>> in time, because packaging is dependency for master node upgrades. And there
>>> is a risk to spend about two weeks on changes and tests.
>>>
>>> Obviously we can't merge migration to rpm right now, because it will
>>> totally break our ability to create development iso.
>>>
>>> My proposal is to build development iso as before, in virtual
>>> environments. And for iso from master branch use packages. It will require
>>> additional flag during build time and will allow us start test packages
>>> really soon.
>>>
>>> Disadvantage of this solution - for some time we will have different
>>> types of builds and can create possible issues.
>>> Another disadvantage - we will need extra code, but it is about 15 lines
>>> and seems ok for me.
>>>
>>> I'm going to create blueprint if nobody have strong objections.
>>>
>>> --
>>> Mailing list: https://launchpad.net/~fuel-dev
>>> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~fuel-dev
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>>
>>
>> --
>> Mike Scherbakov
>> #mihgen
>>
>> --
>> Mailing list: https://launchpad.net/~fuel-dev
>> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~fuel-dev
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
> --
> Mailing list: https://launchpad.net/~fuel-dev
> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~fuel-dev
> More help   : https://help.launchpad.net/ListHelp
>