-Intel POD1 is used as test environment for kvmfornfv to execute cyclictest. As
-part of this test environment Intel pod1-jump is configured as jenkins slave
-and all the latest build artifacts are downloaded on to it. Intel pod1-node1
+Intel POD10 is used as test environment for kvmfornfv to execute cyclictest. As
+part of this test environment Intel pod10-jump is configured as jenkins slave
+and all the latest build artifacts are downloaded on to it. Intel pod10-node1
the Rpms (on 'centos') and Debians (on 'ubuntu') builds in this case.
* How to build Kernel/Qemu Rpms- To build rpm packages, build.sh script is run
with -p and -o option (i.e. if -p package option is passed as "centos" or in
the Rpms (on 'centos') and Debians (on 'ubuntu') builds in this case.
* How to build Kernel/Qemu Rpms- To build rpm packages, build.sh script is run
with -p and -o option (i.e. if -p package option is passed as "centos" or in
* How to build Kernel/Qemu Debians- To build debian packages, build.sh script
is run with -p and -o option (i.e. if -p package option is passed as
* How to build Kernel/Qemu Debians- To build debian packages, build.sh script
is run with -p and -o option (i.e. if -p package option is passed as
* How to build all Kernel & Qemu, Rpms & Debians- To build both debian and rpm
packages, build.sh script is run with -p and -o option (i.e. if -p package
* How to build all Kernel & Qemu, Rpms & Debians- To build both debian and rpm
packages, build.sh script is run with -p and -o option (i.e. if -p package
- option is passed as "both"). Example: sh ./ci/build.sh -p both -o build_output
+ option is passed as "both"). Example:
+
+.. code:: bash
+
+ cd kvmfornfv/
+
+ For Kernel/Qemu RPMs and Debians,
+ sh ./ci/build.sh -p both -o build_output