blob: 7c677e3c750f63b47e9d090c6b0e3527952b32d3 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
|
.. _xci-overview:
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. SPDX-License-Identifier: CC-BY-4.0
.. (c) Fatih Degirmenci (fatih.degirmenci@ericsson.com)
======================================
Cross Community Continuous Integration
======================================
This document will contain the overview, the pipelines, and stuff.
Introduction
============
OPNFV has an advanced Continuous Integration (CI) machinery that provides support
to OPNFV community to develop, integrate, test and release the integrated
reference platform for NFV.
During the past releases, OPNFV integrated, deployed and tested different
flavors (scenarios) of the platform in an entirely automated fashion, resulting
in feedback to OPNFV itself and the communities OPNFV works with. This enabled
communities to implement new features directly in the upstream, identify bugs
and issue fixes for them.
The development and release model employed by OPNFV uses stable versions of
upstream components. This helps developers and users who are after the stability
however it slows down the speed of development, testing, resulting in slower pace
in innovation.
In order to provide means for developers to work with OpenStack master
branch, cutting the time it takes to develop new features significantly and
testing them on OPNFV Infrastructure
enable OPNFV developers to identify bugs earlier, issue fixes faster, and
get feedback on a daily basis
establish mechanisms to run additional testing on OPNFV Infrastructure to
provide feedback to OpenStack community
make the solutions we put in place available to other LF Networking Projects
OPNFV works with closely
embrace the change and apply Continuous Delivery and DevOps principles and
practices to OPNFV
|
