Age | Commit message (Collapse) | Author | Files | Lines |
|
The test execution time for VM costs around 1hr
and 30 min. Need to extend the timeout.
Change-Id: I6f83dc5ed8c5c1ae76b6e6e33758bfdb254aef23
Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
|
|
Change-Id: I0913e115951aa48eb99366125292772f4fc6d93e
Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
|
|
The parameter 'SUT' is meaningless to storage job and experiment
job.
Change-Id: I40322962111896773821b8ef2f05e6f330d7da00
Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
|
|
QTIP test runs against with host and vnf.
Change-Id: I863cb48356f6ba74043b51ebfae8e5ff2f241abc
Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
|
|
Delete Euphrates CI jobs.
JIRA: QTIP-292
Change-Id: I6ab6055fccc2bb7de299bab5732f97565ecef808
Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
|
|
GERRIT_REFSPEC is always passed by the gerrit-trigger plugin when a job
is triggered by Gerrit. Because it is not explicily defined, there is no
way to manually trigger jobs, as the git clone looks up the list of refs
by GERRIT_REFSPEC.
Being able to manually trigger jobs (with node parameters so they can be
restricted) is very helpful in debugging CI issues.
Change-Id: I8a1d9ea380902fc95f30482e5acb616347709ab1
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
- the job does not work for patch with *.ipynb deletion
- qtip has migrated to rst for formula display
Change-Id: I4882f55ac7d9d4430a15c1f0237e0b9d6e223f47
Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
|
|
|
|
deleted file can not be previewed
Change-Id: Ic860baf0deeb574e20067bdae230cb7ef22d7458
Signed-off-by: Yujun Zhang <zhangyujun@gmail.com>
|
|
Same with the patch https://gerrit.opnfv.org/gerrit/#/c/47541/
Change-Id: Ide8e125731de046793326e5a8d8ef373b4fdad19
Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
|
|
|
|
It seems we need to give more time for storage test.
That job has been aborted by timeout those days.[1]
[1]
https://build.opnfv.org/ci/view/qtip/job/qtip-storage-apex-master/97/console
Change-Id: Iafef11d38a83c95e8bf82c4b6664716f4e8de535
Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
|
|
Since fetch_os_creds.sh has a judgement with BUILD_TAG,
I add the pod info for it.
Change-Id: I248be530d15bb807dcf9fec1fe924d698a8f56ab
Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
|
|
Change-Id: I14dc0f19014a0f320ccf1a05c14e387b61294d8d
Signed-off-by: Taseer Ahmed <taseer94@gmail.com>
|
|
JIRA: QTIP-282
Change-Id: If765bfa01a1dab987409c311f3a718bffea76797
Signed-off-by: Taseer Ahmed <taseer94@gmail.com>
|
|
JIRA: QTIP-280
Change-Id: Ie588c3e38af82fe9b2de8bb01549a1c9249d54ff
Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
|
|
not enough valid data in history for elastic check
Change-Id: Ie3bcd7cc186605a31a857130646468e6f1ca7dde
Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
|
|
Change-Id: I81b1cf1492d215c934e148eba5eba7535d38cfd0
Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
|
|
Change-Id: I67a96819d4cf5c6c2b18267f97728aaeda1b188a
Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
|
|
Change-Id: Ied35e58137fb8040779fe038626facd684a935dd
Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
|
|
Change-Id: Ib4b07e23a81718e759ed43ff7fa2882735804afc
Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
|
|
JIRA: QTIP-273
Change-Id: I8d192c70b881cc826fa37d15eec7eb4173a51e35
Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
|
|
|
|
Change-Id: I8a138d6cdcfa055260fc25fa909b28d192d5c98f
Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
|
|
Change-Id: Ia705bd9c16ca934bc781e558b27feafa89b3bff0
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
JIRA: RELENG-254
Change-Id: I07318b8077d46e5d716f0ac42453ab999e5c76d9
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
- manage help scripts in qtip repo instead of releng
- call entry script in qtip from releng
JIRA: QTIP-268
Change-Id: Ibd0d2c2533c1a7f1963f6c3214c563499cce8b22
Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
|
|
Change-Id: I6c3fa3aaaf6f017a014a9e2294995e5a915fdbe8
Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
|
|
|
|
|
|
Change-Id: Ida62e630c1f26ed4058eb34dbd9d438fb6071387
Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
|
|
Adds the 'email-jenkins-admins-on-build-failures' publishers for jobs
which have overridden the default list of publishers.
This will provide Jenkins administrators a time-series list of build
failures to assist in debugging issues with the master and agents.
JIRA: RELENG-257
Change-Id: I28f12877562113c9197ed6429ee2a7f3cdbaf346
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Note that
- experimental trigger is modified to allow trigger the build from
changes outside `tests` folder
- doctor jobs modified to adapt the change in common trigger
Change-Id: Iaaa26651f9ea1d14cb6c77a713ff657c330dce6e
Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
|
|
Got an SSL error when loading content from https://artifacts.opnfv.org [1]
HTTPS is not a must for this use case, so use http instead to solve this issue.
[1] https://nbviewer.jupyter.org/urls/artifacts.opnfv.org/qtip/review/37731/compute-qpi-report/report.ipynb
Change-Id: I8b09eb2d1da234c17843f2cb7504a3b1ded9017e
Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
|
|
- missing '/' in upload path
- missing build result report to gerrit
- notebook review job should be limited for changes in example/** folder
Change-Id: I83d09157077306128a6db66429d8a402f2e7c69e
Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
|
|
It is done by uploading the notebook under reviewer to artifacts
and add the nbviewer link in gerrit comments
It is needed because reviewing jupyter notebook[1] directly in
gerrit is very difficult. See example in [2]. It will be much
easier if we can preview the result in nbviewer. See example in [3]
[1]: http://jupyter.org/
[2]: https://gerrit.opnfv.org/gerrit/#/c/37227/
[3]: https://nbviewer.jupyter.org/urls/git.opnfv.org/qtip/plain/examples/storage-qpi-report/storage-qpi.ipynb
Change-Id: I3e4c301f362ff6ac97aebc9d09c7103278efb136
Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
|
|
Change-Id: I5e9ee5bf45f4f349dc178ce7062610469c8de008
Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
|
|
Use new CI script run_ci.sh to trigger QTIP test.
Change-Id: I1e9b0628d3dde64dca9d6e8b3d9bad9f31ff3f3a
Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
|
|
|
|
- delete container and image based with branch
- adjust builder sequence
Change-Id: Id365d2358195ae690d9a4d5ae8bd1a5adfcc7046
Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|
|
missing \" for if condition
use qtip temp dir for tempfiles
Change-Id: I696b81b2e017f630051353f10b96f07fb85e2ec2
Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
|
|
ansible can not run correctly in qtip docker currently in centos.
Change-Id: I3295b358e43026e10ed7421196d88305a11ed877
Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
|
|
|
|
- only keep the builder "qtip-validate-deploy", remove the others
- add scenario info in qtip-validate-jobs.yaml
- add some print info in validate-deploy.sh
- a related modification in fuel jjb file
Change-Id: Iff884f273eea5c6aac64e09cfffcedc7481b47e9
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|
|
otherwise the insecure key will be left in server
Change-Id: I2bae0c16e8da05d68d53cb5624a6660053c80756
Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
|
|
Parameter BRANCH is not correct in danube daily job[1]: expected `stable/danube`, actual `danube`
The following corrections are made as an attempt to fix this issue
- enable CI_DEBUG for additional information
- inline qtip-common-parameters
[1]: https://build.opnfv.org/ci/view/qtip/job/qtip-daily-fuel-zte-pod3-danube/7/parameters/
Change-Id: Ia892371925ffdb817d663c134d16e4568c07dff7
Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>
|
|
- since zte pod2 is used for daisy, move qtip job to zte pod1
- add danube trigger
Change-Id: Id0bdc5e791d3ed33a4f48d46b51823672794d2dc
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|
|
|
|
|
|
Previously, if an upstream patchset contained a change for a file
listed in 'forbidden-file-paths' the job would not be triggered. This
is not desirable since such a patchset may contain important changes so
we enable the 'disable-strict-forbidden-file-verification' option which
triggers the job unless the patchset only contains changes for the
files listed in 'forbidden-file-paths'.
Note: The diff was generated using the following script:
for i in $(grep -l -r forbidden-file-paths *);do sed -i "s/\(^.*\)forbidden-file-paths/\1disable-strict-forbidden-file-verification: \'true\'\n&/" $i; done
Please double check that the changes look sensible for each team's project.
Change-Id: Ifa86d3a39b36375b2fd52b449e29c8dc757499b4
Signed-off-by: Markos Chandras <mchandras@suse.de>
|