commit | 7b4a1e87ccc16e182b0e65f6be1a11600435f225 | [log] [tgz] |
---|---|---|
author | Luca Prete <luca@onlab.us> | Tue Sep 12 10:44:48 2017 -0700 |
committer | Luca Prete <luca@opennetworking.org> | Tue Sep 12 10:45:40 2017 -0700 |
tree | 8f004fdbf19ecdf6c36c9a17992f67ecd6b50309 | |
parent | 27a9205e6b12b0898e3443257396fb7c3cc8b610 [diff] |
Moving build cleanup at the end of the jenkins file in the finally block Change-Id: If5fc49e5bd25e41b7add7c19c6c217eae93e62fa (cherry picked from commit 225d965e92f1e73add82d1ae222d00c069be4ce6)
This is the main entry point for building and installing CORD.
If this is your first encounter with CORD, we suggest you start by bringing up an emulated version called CORD-in-a-Box. It installs CORD on a set of virtual machines running on a single physical server. Just follow our CORD-in-a-Box Guide.
You can also install CORD on a physical POD. This involves first assembling a set of servers and switches, and then pointing the build system at that target hardware. Just follow our Physical POD Guide.
For additional information about the CORD Project, see: