fixing nightly build after the chameleon escaped...
Chameleon left so to catch him, we had to mount the entire cord
repo to allow voltha to build the chameleon container.
Change-Id: I60db604fd557aa0d6f7d3995951d403af39cb641
diff --git a/Jenkinsfile b/Jenkinsfile
index ab3fc30..ff7b0c3 100644
--- a/Jenkinsfile
+++ b/Jenkinsfile
@@ -8,13 +8,13 @@
sh 'vagrant up voltha'
stage 'Build voltha'
- sh 'vagrant ssh -c "cd /voltha && source env.sh && make fetch && make" voltha'
+ sh 'vagrant ssh -c "cd /cord/incubator/voltha && source env.sh && make fetch && make" voltha'
stage 'Bring up voltha containers'
- sh 'vagrant ssh -c "cd /voltha && source env.sh && docker-compose -f compose/docker-compose-system-test.yml up -d" voltha'
+ sh 'vagrant ssh -c "cd /cord/incubator/voltha && source env.sh && docker-compose -f compose/docker-compose-system-test.yml up -d" voltha'
stage 'Run Integration Tests'
- sh 'vagrant ssh -c "cd /voltha && source env.sh && make smoke-test" voltha'
+ sh 'vagrant ssh -c "cd /cord/incubator/voltha && source env.sh && make smoke-test" voltha'
currentBuild.result = 'SUCCESS'
slackSend channel: '#voltha', color: 'good', message: "${env.JOB_NAME} (${env.BUILD_NUMBER}) Build success.\n${env.BUILD_URL}"