summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2016-12-01Functest jjob: add the option to provide the rc file as parameterjose.lausuch2-18/+38
Change-Id: Icb5dd3f0f46eb4891609d1f0e4d868e84fe49a14 Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
2016-12-01Merge "doctor: drop postbuilders"Ryota Mibu1-14/+1
2016-12-01Merge "prototypes: bifrost: Increase default provision timeout to 3600 seconds"Fatih Degirmenci1-1/+1
2016-12-01doctor: drop postbuildersRyota MIBU1-14/+1
Change-Id: I228619470b4baace4acbc53e0bd710dd0aea7c4b Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
2016-12-01prototypes: bifrost: Increase default provision timeout to 3600 secondsMarkos Chandras1-1/+1
Sometimes, the current '2400 seconds' timeout is not enough to all 3 VMs to become reachable especially when the qcow2 images are becoming bigger and bigger. This leads to spurious CI failures. Increase the timeout to 3600 seconds which should be enough for VMs boot properly Change-Id: I06942952667df28341e5ce43d30619fe2e30326b Signed-off-by: Markos Chandras <mchandras@suse.de>
2016-12-01Merge "Add parameters in init function"Morgan Richomme1-1/+2
2016-12-01Merge "doctor: fix file paths"Ryota Mibu1-4/+20
2016-11-30Merge "Apex: Adds odl_l2-fdio-ha to daily"Tim Rozet1-1/+2
2016-11-30Merge "armband: Enable deploy-cache"Aric Gardner1-1/+14
2016-11-30doctor: fix file pathsRyota MIBU1-4/+20
- fix file path to mount doctor code under review - re-add workaround to archive functest suite log - drop unnecessary params for jobs Change-Id: I51ed4dbd7178c875cb6b047f26ae4c1db3d94687 Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
2016-11-30Merge "doctor: fix parameter setting"Ryota Mibu1-22/+30
2016-11-30doctor: fix parameter settingRyota MIBU1-22/+30
In the current doctor jenkins jobs, default parameters for functest are used. This patch updates parameter settings, and also simplifies archive instruction. Change-Id: I6940d323271bc9492eeb5e9f8ca9faf02612f483 Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
2016-11-30Merge "Fix the non-virtual node error for virtual-deploy job"Serena Feng1-1/+3
2016-11-30Add parameters in init functionrohitsakala1-1/+2
Change-Id: I8ce5219251ff21f2cf3a554d275b4d2584d70e0b Signed-off-by: rohitsakala <rohitsakala@gmail.com>
2016-11-30Fix the non-virtual node error for virtual-deploy jobzeyu zhu1-1/+3
Change-Id: I617849b23aca515525f7e2219c3f268cbda80e43 Signed-off-by: zeyu zhu <zhu.zeyu@zte.com.cn>
2016-11-30Merge "Rearrange Releng Job and Parameter Files"Ryota Mibu11-1/+1
2016-11-30Merge "update doctor CI job"Ryota Mibu1-23/+25
2016-11-30armband: Enable deploy-cacheAlexandru Avadanii1-1/+14
This enables the mechanism added in [1]. Armband just added support for caching deploy artifacts, like bootstraps and target images, which take a lot of time at each deploy to be built, considering it requires a cross-debootstrap via qemu-user-static and binfmt. For easier setup, the deploy cache depends on the local ISO storage mechanism (/iso_mount/opnfv_ci), and reuses the same storage pool. To enable deploy caching, just create the deploy-cache directory at: /iso_mount/opnfv_ci/<branch>/deploy-cache JIRA: ARMBAND-172 [1] https://gerrit.opnfv.org/gerrit/#/c/25191 Change-Id: I161205a87f13cd78e79b96bfc37a5f68aba093cc Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-11-29Rearrange Releng Job and Parameter FilesTrevor Bramwell11-1/+1
Individual project jobs can now be tested using: jenkins-jobs test -r jjb/global:jjb/$project - Rename '.yaml' files to '.yml' so they get checked by the verify-releng.sh script, and update the script to include checking of '.yaml' files. - Move parameter and macro files under new 'global' directory. Change-Id: I6b74f5d8af2bced3256a7f4a33983df5310511a2 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2016-11-29Apex: Adds odl_l2-fdio-ha to dailyTim Rozet1-1/+2
Trades noha for ha scenario Change-Id: I595766b8a06b115e0453c593c728c85e5a648e3d Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-11-29Merge "Remove trailing slash in example"Fatih Degirmenci1-1/+2
2016-11-29Merge "Refactor Docker build jobs"Fatih Degirmenci3-299/+42
2016-11-29Merge changes from topic 'fix-monit-script'Aric Gardner1-25/+22
* changes: utils: jenkins-jnlp-connect.sh: Make monit actions conditional utils: jenkins-jnlp-connect.sh: Fix start up script
2016-11-29Merge "jjb: infra: Fix and enable the SUSE job for bifrost"Aric Gardner1-4/+29
2016-11-29Merge "bifrost: Make use of the new 'openssh-server' dib element"Aric Gardner3-3/+13
2016-11-29utils: jenkins-jnlp-connect.sh: Make monit actions conditionalMarkos Chandras1-21/+20
When executing the connection testing command as indicated in [1], -t is added to the monit start-up script parameters. This prevents the jenkins service from running in the background and create the pid file. Because of that, monit is confused and reports the service as failed. We fix this by moving all the monit related actions inside the 'monit' conditional block. [1]: http://artifacts.opnfv.org/octopus/brahmaputra/docs/octopus_docs/opnfv-jenkins-slave-connection.html#connecting-slaves-from-community-labs-to-opnfv-jenkins Change-Id: I7371c4560311b84f56eff3461254264e1769ff7e Signed-off-by: Markos Chandras <mchandras@suse.de>
2016-11-29Merge "bug Fix: adapt reporting to merge of smoke+sdn tiers"Morgan Richomme1-4/+4
2016-11-29Merge "Add Escalator CI job"Serena Feng4-0/+453
2016-11-29Merge "Enable Flake8 Checks on Escalator"Serena Feng1-1/+1
2016-11-29Merge "set "opnfv-lint-verify" as the basic verify of compass"Jun Li1-1/+1
2016-11-28jjb: infra: Fix and enable the SUSE job for bifrostMarkos Chandras1-4/+29
Fix SUSE parameters for os, release, packages and elements and enable the job. Change-Id: I0fc0fbc5fcf8df04186d6c19aaf363020d31a44c Signed-off-by: Markos Chandras <mchandras@suse.de>
2016-11-28bifrost: Make use of the new 'openssh-server' dib elementMarkos Chandras3-3/+13
Make use of the new 'openssh-server' dib element to achieve a consistent behavior of ssh server across all distributions. Change-Id: Ib10066a244fe44530969702cd465cdd79454b8fe Signed-off-by: Markos Chandras <mchandras@suse.de>
2016-11-28Merge "Add jobs for ARM virtual POD"Aric Gardner2-7/+11
2016-11-28Remove trailing slash in exampleAric Gardner1-1/+2
also add caveat note Change-Id: Ie662ffb9240c3ffdbc4c7317d63744a8beedec4a Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
2016-11-28bug Fix: adapt reporting to merge of smoke+sdn tiersMorgan Richomme1-4/+4
Change-Id: I74d9834b609797f85d52e97ccdfeab614c1c07bf Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
2016-11-28Merge "Apex using a different network settings file for master"Tim Rozet1-0/+2
2016-11-28Merge "Enable qtip verify job"Fatih Degirmenci1-1/+6
2016-11-28Refactor Docker build jobsjose.lausuch3-299/+42
- Remove incremental tags for stable branches - Use "latest" or "stable" tags only - Have a single job template for all projects More info here: https://wiki.opnfv.org/display/INF/Docker+handling+in+CI Change-Id: Ibce3ef2faee136f56f0eab12dfe7a93c267db854 Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
2016-11-28update doctor CI jobRyota MIBU1-23/+25
Doctor has an experimental CI job. It has three parts (builders in jjb / runners in CI). The main job will trigger two runner jobs which will run 'test/run.sh' in the same CI pod with different inspector (sample and congress). While executing those two children jobs, the main job will block CI pipline on that pod. In order to avoide deadlock and sequencial runner job execution, we set two pipelines for the pod. But, it still allow deadlock when we trigger two main jobs at the same time. This patch simplify the job definition by splitting two runner jobs and removing the main job. Change-Id: I4fadd58cc827a41927940c38cf05ed105c6f243c Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
2016-11-28Make the requirements.txt compatible with Coloradochenjiankun1-1/+1
JIRA: YARDSTICK-428 Now in master, we move the requirements.txt from tests/ci/ to yardstick root path. But in colorado, this has yet to be done.If we cherry pick from master to colorado, it will encounter error. So we must make it compatible. Change-Id: I0537d989e677b73e19a1e093166493f3f6d25783 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2016-11-27Add jobs for ARM virtual PODcristinapauna2-7/+11
Pod virtual1 was added in the ENEA-ARM lab This commit adds the jobs for it JIRA: ARMBAND-162 Change-Id: Icaa798691f5ff60a58ae083eb1c366170c464b92 Signed-off-by: cristinapauna <cristina.pauna@enea.com>
2016-11-25multisite: Use correct names for the generated filesFatih Degirmenci1-2/+2
Change-Id: I030dbca1a44231ae0548a5b17cd2f419ec7a4289 Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2016-11-25Enable qtip verify jobYujun Zhang1-1/+6
Change-Id: I15be7c9cab2ffa471a828b3295051cbd423988f5 Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
2016-11-25Merge "Adding GS_PROXY prefix to GS_URL in proxy scenario"Serena Feng1-1/+1
2016-11-24multisite: Run jobs on right nodesFatih Degirmenci1-0/+6
Change-Id: Ia681d629eb685ed1186be2bb74e42e2067b48aa2 Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2016-11-24multisite: Adjust archival of generated filesFatih Degirmenci1-13/+51
Change-Id: I1e9236d04143c87bb85d15b05b6e42ea34438f8b Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2016-11-24utils: jenkins-jnlp-connect.sh: Fix start up scriptMarkos Chandras1-4/+2
The jenkins-jnlp-connect.sh script is meant to be executed from the $jenkinshome directory. The monit script was configured to enter a different directory before starting the jenkins script which always resulted in a broken start-up phase like this: "This script needs to be run from the jenkins users home dir" We fix this by entering the $jenkinshome directory before starting up the jenkins script. Change-Id: If0f65417f07a7fa9328f9adcd1ca1a1a3bc530ed Signed-off-by: Markos Chandras <mchandras@suse.de>
2016-11-24Create kingbird jobs to run on multi nodeFatih Degirmenci2-0/+213
Change-Id: I73cec4d39f5a3119c1cc7f86b7919a0431f8f653 Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2016-11-24Add Escalator CI jobzeyu zhu4-0/+453
Change-Id: Ia2dafa452fb0512b04766fae92a97eff59db888b Signed-off-by: zeyu zhu <zhu.zeyu@zte.com.cn>
2016-11-24Adding GS_PROXY prefix to GS_URL in proxy scenarioJulien1-1/+1
${GS_PROXY} does not include branch name in the URL, when use it to download the latest.properties, it always downloads the master branch file, not the current release defined in ${gs-pathname}. In this patch, no longer directly use ${GS_BASE_PROXY}, but join them. JIRA: FUEL-225 Change-Id: I2566036c174b2f03997669d25a37f1de21ffeac6 Signed-off-by: Julien <zhang.jun3g@zte.com.cn>