Gitiles
Code Review Sign In
gerrit.opencord.org / cord / f9cb2f3faa70a306df314eb31ae98fd588e45425
commitf9cb2f3faa70a306df314eb31ae98fd588e45425[log] [tgz]
authorYou Wang <you@opennetworking.org>Mon Sep 11 13:26:42 2017 -0700
committerYou Wang <you@opennetworking.org>Mon Sep 11 13:26:42 2017 -0700
tree22948aae9e9fa0735b66f033ecfeeac57e531dc7
parent5a7e7e3eef1424c8b8c84cd4979c4070d292ec50 [diff]
Update Jenkins file for the new build system

Change-Id: I466b916efd7226fb8b16f740e6a020791f1b0bb8
1 file changed
tree: 22948aae9e9fa0735b66f033ecfeeac57e531dc7
  1. .gitignore
  2. .gitmodules
  3. Jenkinsfile
  4. Jenkinsfile.ciab
  5. Jenkinsfile.imagebuilder
  6. Jenkinsfile.newBuildSystem
  7. LICENSE.txt
  8. Makefile
  9. README.md
  10. Vagrantfile
  11. ansible.cfg
  12. ansible/
  13. build.gradle
  14. buildSrc/
  15. config/
  16. docker_images.yml
  17. docs/
  18. elk-logger/
  19. genconfig/
  20. gradle.properties
  21. gradle/
  22. gradlew
  23. gradlew.bat
  24. image_logs/
  25. logs/
  26. milestones/
  27. podconfig/
  28. scenarios/
  29. scripts/
  30. settings.gradle
  31. utils/
README.md

Building and Installing CORD

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: