Difference between revisions of "ThirdPartySystems/Tail-f NCS CI"
Line 6: | Line 6: | ||
|method=Gerrit Trigger to run Network API tests with Tail-f NCS driver enabled. Planning to enable Scenario tests under shellci when the tests are contained in VMs. | |method=Gerrit Trigger to run Network API tests with Tail-f NCS driver enabled. Planning to enable Scenario tests under shellci when the tests are contained in VMs. | ||
|programs=Neutron (ml2) | |programs=Neutron (ml2) | ||
− | |status=in production, non-voting}} | + | |status=in production, non-voting. +1 on success, 0 on failure. Daily manual review of failures}} |
Revision as of 01:58, 18 August 2014
Gerrit Account: tailfncs | |
Contact Information: email: Luke Gorrie <luke@tail-f.com>; irc: lukego; mobile: +41 79 244 32 17 | |
Intent: Test ML2 subsystem changes with the Tail-f NCS driver. | |
Structure: Currently Jenkins with all software running on the master. Planning switch to shellci (https://github.com/SnabbCo/shellci) to support parallel tests boxed in virtual machines. | |
Method: Gerrit Trigger to run Network API tests with Tail-f NCS driver enabled. Planning to enable Scenario tests under shellci when the tests are contained in VMs. | |
OpenStack Programs: Neutron (ml2) | |
Current Status: in production, non-voting. +1 on success, 0 on failure. Daily manual review of failures |