Update Jenkinsfiles to use buildNode instead of TestNodeName

Change-Id: Ifd68d1f67d88ebf7190e733311bfc8f8f1a59a06
14 files changed
tree: 1efaf2990c239694d4c4ff6dc65d8b90e3eaad0c
  1. .gitignore
  2. .gitreview
  3. CODE_OF_CONDUCT.md
  4. COPYRIGHT.txt
  5. JenkinsFile-verify-api-tests
  6. Jenkinsfile-attworkflow-build
  7. Jenkinsfile-attworkflow-build-released-ver
  8. Jenkinsfile-attworkflow-test
  9. Jenkinsfile-comac-release-build
  10. Jenkinsfile-mcord-license-check
  11. Jenkinsfile-mcord-local-build
  12. Jenkinsfile-mcord-release-build
  13. Jenkinsfile-mcord-remote-build
  14. Jenkinsfile-rcordlite-control-plane
  15. Jenkinsfile-rcordlite-topdown-build
  16. Jenkinsfile-rcordlite-topdown-test
  17. Jenkinsfile-rcordlite-zerotouch-build
  18. Jenkinsfile-rcordlite-zerotouch-test
  19. LICENSE.txt
  20. Makefile
  21. README.md
  22. VERSION
  23. cord-robot/
  24. docs/
  25. requirements.txt
  26. roles/
  27. scripts/
  28. src/
README.md

Cord-Tester

CORD Automated Tester Suite

The CORD Automated Tester Suite (CATS) is an extensible end-to-end system test suite targeting CORD PODs. It is typically deployed as one or more Docker containers, either on the CORD POD or adjacent to the POD and interacts with the POD through the PODs interfaces.

Its intended use includes:

  • Regression testing for CORD related component development
  • Acceptance testing of a deployed CORD POD
  • Health-testing of an existing CORD POD (including non-service-impacting and possibly service-impacting tests)

The strength of the CATS will come from the collaboration of the whole CORD/ONOS community, and as such we welcome contributions.

For further information, please browse in the ~/docs directory.