1. Regarding CI organization for review.openstack.org: The simple setup is described here: http://ci.openstack.org/third_party.html (see Jenkins Gerrit Trigger section). And this is exactly what we use for fuel-jenkins.mirantis.com right now. Gerrit Trigger functionality is rather limited, but one can trigger builds for events like "new patchset created which changed this particular file".
Setup described by Jay Pypes is closer to the infrastructure used by Openstack Infra itself, but needs much more work and resources. 2. Regarding nightly builds: We publish community nightly builds at https://fuel-jenkins.mirantis.com/view/ISO/ If your tests can be applied to the already built iso, feel free to use it. Currently we publish links to torrent files for recent builds, but we can add something like 'latest' and 'latest successful' symlinks if needed, to simplify automatic downloads. Actually we plan to rework the community builds publishing process, so feature requests are welcome. On Thu, Oct 2, 2014 at 3:49 PM, Nurit Vilosny <[email protected]> wrote: > Hi, > > As part of Mellanox team I would like to emphasize the importance of such > CI for us. > > For example, in RC1 there was a fix that was made and failed the Mellnox > plugins, and we only discover it on our final manual testing. This could be > avoided on time. > > > > I would go with 2 different tests: > > 1. CI for commits that meets filter (specific files or folders) – > as in open stack community. > > 2. The ability to take a nightly build and automatically configured > it – to find problems that slipped through our CI filters. > > > > Nurit > > > > *From:* Fuel-dev [mailto:fuel-dev-bounces+nuritv= > [email protected]] *On Behalf Of *Sergii Golovatiuk > *Sent:* Wednesday, October 01, 2014 7:06 PM > *To:* Evgeniya Shumakher > *Cc:* [email protected] > *Subject:* Re: [Fuel-dev] External CI for external contributors > > > > Hi Fuelers, > > I think that our external contributors should definitely should have own > gateway. It should be a part of integration. Their gate can -1 but won't > affect on voting process though their team will be informed to take some > actions and fix their/our code respectively. > > > -- > Best regards, > Sergii Golovatiuk, > Skype #golserge > IRC #holser > > > > On Wed, Oct 1, 2014 at 5:49 PM, Evgeniya Shumakher < > [email protected]> wrote: > > Folks, > > > > Is there an approach that external contributors, like Mellanox, should use > in order to build an external CI to demonstrate build/test results? > > > > There is a bug in launchpad created couple of months ago: > https://bugs.launchpad.net/fuel/+bug/1320924, but i don't see any > progress there. > > > > My proposal is to take a look at the process OpenStack community selected > for building external CI systems and adapt it for MOS/Fuel. > > Jay Pypes wrote a series of blog posts with instructions for setting up > external CI's: > > - http://www.joinfu.com/2014/01/understanding-the-openstack-ci-system/ > - > > http://www.joinfu.com/2014/02/setting-up-an-external-openstack-testing-system/comment-page-1/#comment-216389 > - > > http://www.joinfu.com/2014/02/setting-up-an-openstack-external-testing-system-part-2/ > > Please let me know what you think about it. > > Mellanox team, your opinion is extremely important here. > > > > -- > > Regards, > Evgeniya > > > > > > > -- > 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 > > -- Aleksandra Fedorova bookwar
-- Mailing list: https://launchpad.net/~fuel-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~fuel-dev More help : https://help.launchpad.net/ListHelp
