Only if these changes already merged. You aren't able to build iso with fuel packages from request.
On Thu, Mar 20, 2014 at 12:20 PM, Mike Scherbakov <[email protected]> wrote: > Ok, great. Then it means that development flow will not be affected at all? > > I mean, if I hack on Nailgun / Astute I won't even notice any changes? Only > when I login to running Fuel Master, and won't see virtual env / gems there > anymore? > > > On Thu, Mar 20, 2014 at 12:03 PM, Dmitry Burmistrov > <[email protected]> wrote: >> >> 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 <[email protected]> >> 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 >> > <[email protected]> >> > 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 <[email protected]> >> >> 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 : [email protected] >> >>> 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 : [email protected] >> >> Unsubscribe : https://launchpad.net/~fuel-dev >> >> More help : https://help.launchpad.net/ListHelp >> >> >> > >> > >> > -- >> > Mailing list: https://launchpad.net/~fuel-dev >> > Post to : [email protected] >> > 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 : [email protected] Unsubscribe : https://launchpad.net/~fuel-dev More help : https://help.launchpad.net/ListHelp
