Age | Commit message (Collapse) | Author | Files | Lines |
|
MCP does not have a self-test healtcheck suite, similar to old
Fuel, so we dropped the "-H" deploy argument (which used to disable
healtcheck autorun).
Adjust deploy command to reflect this installer change.
While at it, fix leftover "pxebr" default installer parameter,
which we missed in the previous commit where we changed the
default only in releng deploy scripts.
Change-Id: I55e1f5cad17687bdf304fbf04d67366dd32ed42a
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Fuel and implicitly Armband switched to a newer format for parsing
the "-B" deploy arg, used to pass bridge(s) information.
For now, we will default to ",,,", which is equivalent to not
setting any default value for any of the 4 possible bridges.
NOTE: Armband overrides this on a per-pod basis, since bridge
information is POD specific in our lab.
Change-Id: I3635b0eb6f8233cf99022a97d5642f2e49197e3b
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
- delete fuel ci jobs on zte-pod2
- according to Euphrates scenario fuel supports[1], disable kvm scenario
on zte-pod3, and enable ovs scenario on zte-pod1.
[1] https://wiki.opnfv.org/display/SWREL/Euphrates+Scenario+Status
Change-Id: Ia84e11d52583a477a105a00691e07eb765f1fae3
Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
|
|
|
|
JIRA: RELENG-277
dovetail run against ZTE-pod1 od-odl_l2-nofeature-ha scenario
weekly, every Sunday
ZTE-pod1 od-odl_l2-nofeature-ha scenario already exists, see the time trigger "0 2 * * *"
dovetail-fuel zte-pod1 job already exists
Change-Id: Ic870a78623873ce2f717477dcb09f18794651899
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
* os-nosdn-ovs-noha (dpdk)
* os-odl_l2-nofeature-noha
* os-odl_l3-nofeature-noha
Change-Id: Ic18f13ea4b23ab5bacb5418a6756bedf9e5fc242
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
|
|
Change-Id: I142961d06b312cc5f43a18f25410236fa67cbcb1
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
Adjusts retrieving OS credentials for MCP (master branch in fuel repo)
Also removes legacy admin_ip and public_ip retrieving.
Change-Id: Ib7781a3701c7281b781872b18150332b94298260
Signed-off-by: Andrii Ostapenko <aostapenko@mirantis.com>
|
|
|
|
* turn off non-existent artifacts upload
* use latest commit in master since there is no iso/image
for mcp based deployments yet
Change-Id: Ib92680ef9838fc2e11d61c806dfd9728514c364e
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
Change-Id: Id523ea140cb8fad92126f2ecb178d3b182ff022f
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
In order to bring in mcp based deployments, turn off for
awhile all master jobs except nofeature one.
Change-Id: I4aa27ab0407e3f32caeba72323ad9511d981a6b8
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
JIRA: DOVETAIL-432
1, only run against fuel os-odl_l2-bgpvpn-ha scenario
this can reduce the CI/pod time resource
dovetail test cases by now (refstack, ha, ipv6, bgpvpn)
2, the conditional steps have been successed tested on compass
to remove the introduce of
https://gerrit.opnfv.org/gerrit/#/c/34327/
conditonal steps look more simple and understandable
Change-Id: I315a789160b8173274b1c1ef916073ced7d5e91b
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
JIRA: DOVETAIL-424
the principle is
1) not disturb the original work flow
2) after vpn testcases integrated into dovetail, i.e, CVP tool,
there is a need to find a POD has bgpvpn feature which is
suitable to validate bgp vpn test cases in proposed_tests.
3) only add dovetail proposed_tests into bgpvpn scenario deploy-test loop
to reduce unnecessary time consuming.
4) further, should consider to add dovetail job in os-nosdn-nofeature loop
Change-Id: Iad6ae1e44470c8e9d49a25980d292ba3871bd6a4
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
zte pod2 will be provided to daisy to run CI job.
Change-Id: I9e0eee1bab4a949f6434850dcbd9624ac6476344
Signed-off-by: wu.zhihui <wu.zhihui1@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>
|
|
|
|
This patch includes resource allocation/time-slots for kvmfornfv
os-nosdn-kvm_ovs_dpdk-ha, os-nosdn-kvm_ovs_dpdk_bar-ha,
os-nosdn-kvm_ovs_dpdk-noha and os-nosdn-kvm_ovs_dpdk_bar-noha
scenarios on Danube branch.
Change-Id: Ib8250075a43dec60be398ce9ee4152b97b7c6796
Signed-off-by: Navya Bathula <navyax.bathula@intel.com>
|
|
Change-Id: I52bc5bc4c8207b71ebad038c584874adebad3ec5
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|
|
For the first time the daily build is ran, the properties file
for the latest ISO built is not present.
JIRA: FUEL-262
Change-Id: I842668bfde4c84cd3ba31571df274633ae238a90
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
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>
|
|
Change-Id: I8b1a4291cd1e0167aad3e9341bb95c42f338caeb
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
Here are the projects that were branched:
I will double check against this list that these changes make sense
and that no one is missing as I go forward.
wiki page of participating projects, and their jobs:
https://wiki.opnfv.org/display/SWREL/Milestone+Compliance+for+Danube
apex - already enabled
armband - done
availability - already enabled
barometer - done
bottlenecks - already enabled
compass4nfv - done
copper - already enabled
daisy - (not participating -- keep jobs disabled?)
doctor - already enabled
domino - already enabled
fds - N/A
fuel - done
functest - already enabled
ipv6 - already enabled
joid - done
kvmfornfv - already enabled
models - already enabled
multisite - done
netready - NOT DONE
opera - NOT DONE
opnfvdocs - done
orchestra - Not participating
onosfw - done
ovsnfv - done
parser - N/A
promise - already enabled
qtip - already enabled
sdnvpn - N/A
snaps - done
securityscanning - N/A
sfc - N/A
storperf - done
ves - already enabled
vswitchperf - already enabled
yardstick - already enabled
Change-Id: I803662faf05c8554cfe7fa5f85da9521f72b03ff
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
Change-Id: I465de0d1e7fec4f8e9b03762adff0049a22f05ef
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Fuel weekly jobs are created, calling fuel-deploy and functest weekly
jobs.
Experimental scripts have also been removed.
Change-Id: If492443e26248731df35e6b6cb5239fb2ae9a86a
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
This patch includes implementation of jobs and triggers for
kvmfornfv os-nosdn-kvm_ovs_dpdk-noha and
os-nosdn-kvm_ovs_dpdk_bar-noha scenarios.
Change-Id: I1e0afd460f42a69b4618b73d032cd4e899e9cb54
Signed-off-by: Navya Bathula <navyax.bathula@intel.com>
|
|
- activate baremetal runs
- disable onos related runs (plugin ain't ready yet)
Change-Id: I89c9cc0a9eafeff698112cdfb4654f4f7852d014
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
This patch includes implementation of jobs and triggers for
kvmfornfv ovs+dpdk+barometer HA scenario test case.
Change-Id: I1b8e4a660f18b479631ea30df80d66c0d75a1bcd
Signed-off-by: Navya Bathula <navyax.bathula@intel.com>
|
|
GIT_BRANCH parameter is different; master or stable/danube in daily
jobs, but 'refs/changes/57/27657/6' in verify jobs. This breaks some
job builders triggered by the both types of jobs. We have GERRIT_BRANCH
parameter for verify jobs to identify stream and expected branch into
the patch will be merged after it got +2 and submitted.
To avoid further confusion and to have common job builders for daily
and verify jobs, this patch introduce BRANCH parameter.
GERRIT_BRANCH is now deprecated.
Change-Id: Ibcd42c1cd8a0be0f330878b21d3011f1ec97043b
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
|
|
This patch includes implementation of daily jobs for kvmfornfv
os-nosdn-kvm_ovs_dpdk-ha and os-nosdn-kvm_ovs_dpdk-noha scenarios.
Change-Id: I2f745b26867df743710cedc249d1a4fdd557e859
Co-Authored-By: Navya <b.navya4@tcs.com>
Signed-off-by: Gundarapu Kalyan Reddy <reddyx.gundarapu@intel.com>
|
|
Change-Id: Icebbb7de8d210bdc95e9e8fbc14342be5d88287f
Signed-off-by: Nikolas Hermanns <nikolas.hermanns@ericsson.com>
|
|
Change-Id: I16f8b919159f901cf414d2b7bd25466a3fa2a8ab
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
This patch defines 'logrotate-default' property and replace 'logrotate'
by it, as 'logrotate' is deprecated on jenkins>=1.637 .
Change-Id: I900975e5b3f590bb7a4d430e2f623931ae782bf4
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
Obsolete plugin jobs and scripts are also removed.
Change-Id: I16f8d932a492fdd1d8eb2caa5f8bc4aa9183327b
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
lf-build1 is experiencing issues.
Change-Id: I2253765d9db2e4603b776bbf5841f61da1bb89fe
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: Iad856adf625a56c2f5c366fb414746d1e9e16691
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
This patch makes sure we use 2 types of scm, and allows us to specify
them by adding one line in job-templates.
- git-scm # for daily jobs and merge jobs
- git-scm-gerrit # for verify jobs [New]
Change-Id: Iddc8a5e0e115193c7081a6d6c53da209900e95c8
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
With the addition of ODL and OpenStack Gerrit servers, it's important we
don't generate additional noise by accidentally building against these
Gerrit servers when we don't intend to.
JIRA: RELENG-179
Change-Id: Ia163c6c3eaa58e8e21dc6548a839062fcbde39ed
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
${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>
|
|
same as patch 24385, which just fixed the latest.properties file
curl:
-L, --location
(HTTP/HTTPS) If the server reports that the requested page has moved
to a different location (indicated with a Location: header and a 3XX
response code), this option will make curl redo the request on the
new place.
without -L, curl just download the redirects info not the file.
JIRA: FUEL-225
Change-Id: I20a01b628ca1545def68bd4e0b24594c24ee7f85
Signed-off-by: Julien-zte <zhang.jun3g@zte.com.cn>
|
|
Since ZTE PODs use url http://build.opnfv.org/artifacts.opnfv.org/ to
download files, it should run curl command with parameter L to follow
redirects.
It does not affect PODs which use url http://artifacts.opnfv.org/
JIRA: FUEL-225
Change-Id: I63b808657ee4f26b801e492b53bc8e4b27396587
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|
|
Daily deployment jobs which use master code and require plugins
which are still not uplifted to Newton are temporary disabled
on bare metal pods.
Change-Id: Ifa7e5136adf53e49c922e844c5a7e6789deb6c8e
Signed-off-by: Fedor Zhadaev <fzhadaev@mirantis.com>
|
|
See https://build.opnfv.org/ci/job/fuel-deploy-zte-pod1-daily-colorado/76/console
latest.properties is downloaded under $WORKSPACE.
Use absolute path $WORKSPACE/latest.properties in these two sentence.
local test is OK.
JIRA: FUEL-225
Change-Id: I37cf3835c56f44cee31a8814b4af1e71c8d1cc6a
Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
|
|
"build"-like jobs were matched to both if-statements so ISOs were uploaded
twice.
This patch fixes that behaviour.
JIRA: FUEL-221
Change-Id: I1f6b18339ec742b65de6a3f3c1ae3c9a5009fa4e
Signed-off-by: Fedor Zhadaev <fzhadaev@mirantis.com>
|
|
Since we do not actually parse our build/deploy logs for color chars,
set the terminal to "vt220".
This will silence quite a few of colorization special identifiers,
but NOT all of them (e.g. `tput sgr0` still prints a sequence).
For Fuel@OPNFV build process, we also need to workaround docker
terminal settings not being passed down when using a tty (see [1]),
which will be fixed in Docker 1.13+. This fix is handled in [2].
[1] https://github.com/docker/docker/issues/9299
[2] https://gerrit.opnfv.org/gerrit/#/c/22883/
Change-Id: I5f0c6eae33349ef81b67dd17e6df4e0af6274fab
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Please take a look at fuel-basic-exp.sh for the proposal.
Apart from scenario name input proposal, jobs and script templatest have
been created as well.
Change-Id: I53b74b2e1ed34acb1f54b7ab21823227fff86d10
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Due to having this experimental, it is needed to set different branches
for upstream and opnfv until the things settle.
Apart from this, the builders also converted to scripts so we don't need
to touch the job yml if scripts need updates.
Change-Id: I65a334bd6f51b558eb6ce69b15bb18405ef28049
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|