Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Change-Id: I97631f1d4902f8b8d3c2de8c4b086ffbad40a0f2
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Now it set that only running Dovetail jobs on Fuel fraser.
Remove the check item.
The mandatory test cases will run on all ha scenarios.
The optional test cases only need to run twice a week on ha scenarios
to save the time.
Change-Id: I7f7dd93440bb40e7bc9964fd744bb002ef88f77b
Signed-off-by: xudan <xudan16@huawei.com>
|
|
Adding it back, I removed it from fuel-project-jobs
and forgot to add it back as its own file
Change-Id: I9d84a979cd5323d72ec858b310cb1b786c5f1207
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
JIRA: FUEL-393
This patch enables odl-bgpvpn-noha scenario on daily jjbs for fuel
installer.
Change-Id: I89e85ee004c08aea07714e678fb223a7721b29ec
Signed-off-by: Stamatis Katsaounis <mokats@intracom-telecom.com>
|
|
|
|
Change-Id: Id169e19cd465d264525bfde843e7764d4f4d5d16
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
Change-Id: Ic3c99eee282641eb15880fe18578cbee534308e5
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
RTD jobs for all active projects
All jobs start as non-voting.
All rtd jobs are in their own file to
faciliate future bulk changes:
jjb/$project/$project-rtd-jobs.yaml
All project have rtd pages
https://opnfv-$project.readthedocs.io
Change-Id: I776e41f968d38f08cb3187f743f69d5d6b697e8e
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
A change to the NodeLabelParameter config in JJB caused any jobs using
the plugin to possibly have their jobs triggered on builders which
weren't online.
This in turn caused the queue to backup and newer jobs are blocked
waiting for older ones to complete, which never happens as they're never
queued on an online builder.
The 'all-nodes' parameter ensure jobs that are set to run concurrently
don't trigger across all available nodes at once, as this will include
offline nodes as well. As this is the default of the plugin, projects
which need it can enable it individually.
Change-Id: Ia690eef078209b6b056dad85613dda6868b18271
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
jjb/lf-ci-jobs.yaml has jjb-version: 2.2.1 as a minimum
change block-level to blocking-level:
https://review.openstack.org/#/c/608092/
We will need to change this back once we move past
jenkins-job-builder>2.5.0
Change-Id: I12d0f55ee3c2dad20340ebf0fa8428ee1ad8484c
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
- keep fraser jobs for Dovetail, schedule 4 CI runs / week / arch;
- stop running Functest/Yardstick for fraser to cut down CI time;
- reschedule master/gambia triggers to ensure an uniform CI POD
allocation across the week;
- enable gambia triggers;
Change-Id: I2a66628ff3525cc9cbd4ffbb4b790633257b6cba
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
Change-Id: I70f8e7c9372e22e6f3e357b48a0a49f44a4d9078
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: Ic1430742e98dd0e98ea3456c636a910c22a90e88
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
With the rework of Fuel & Armband repos, the condition for using sudo
got mixed up and alternated between on/off for armband's deploy/verify
jobs. Rewrite it based on lab allocation instead of project.
Change-Id: I428c585142017b170233858ec3160fdaf998db0c
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
==~ and its negative form previously used mean the pattern should
match the whole string, while =~ returns true for partial matches.
Change-Id: Ibdeacb4bc221820175b15a87db343fc950e0f9e8
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
While at it, tweak regex for verify job to match 'recheck' right
before EOF.
Change-Id: I3e8e1eeaf2ca947425fa2443b29e150c808eea07
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
- disable functest smoke on arm-virtual* PODs, since we don't perform
a full deployment on those PODs, only a basic integrity check;
Change-Id: I0bcd6da32118ea256652dc74977ef0ee7f2525ab
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Duplicate fuel-verify jobs based on cluster type (virtual, baremetal)
and allow (re)checking changes using a specific scenario:
- ALL changes will trigger a virtual POD CI cycle (build, deploy,
smoke) on submit, rebase etc., just like they used to;
- change comments containing a substring formatted like:
* `recheck: os-odl-nofeature-ha`
* `reverify: os-odl-nofeature-noha`
* `recheck`
will trigger only virtual or baremetal deployments of the required
scenario (default os-nosdn-nofeature-noha) on:
* virtual PODs if scenario is NOHA;
* baremetal PODs if scenario is HA;
- limit arm64 verify job running on arm-virtual2 to the installation
of infrastructure VMs and skip cluster setup to prevent POD time
starvation;
Limitations:
- HA scenarios can only be verified on manual request via a change
comment (e.g. 'recheck: os-odl-ovs-ha');
JIRA: FUEL-390
Change-Id: I6368cfd045180d6a7202b8d817b17a4b123ba2af
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
- cleanup deploy tooling for old-style artifacts (ISO-based);
- remove danube stream, related jobs and hacks required for them;
Change-Id: Ib2486173df1ec83f2dbc08a5e9faf950bffb4b06
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
We don't currently support ONOS and KVM-based scenarios.
Change-Id: I9869498c1f726293d571562291e850a817bf3e18
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: I64aae5719f1a0a667e56722bab9e5012a813571f
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
This reverts commit b4a65c5e6777a53be5ea817c967caeee51285a7f.
Chain of DOCKER-ISOLATION already has required rule.
Change-Id: Ic7d3e93a2814a42764b4822ef96e0841f68b774d
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
JIRA: ARMBAND-401
Change-Id: Icd32874ecb38c3f7469e71bd461794b65f50494c
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Docker build automatically appends 'amd64-<TAG>' or 'arm64-<TAG>',
which are normally combined using manifest tool. However, for verify
we don't push a manifest, so use the explicit arch-specific tag.
Change-Id: Idc036216919164e71d3da5032a79f7f47d115710
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: I6b641c87e2672a9e879865baebfa3a58129823f7
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
Rework Fuel verify jobs:
- split 'fuel-verify' into per-arch jobs (amd64 and arm64):
* for now, arm64 jobs are non-voting;
- add 'docker-build' phase job:
* the docker build job will run on the same virtual POD jump host
as the deploy, to bypass the need of pushing to a (public)
Docker hub registry - this might be refactored later to resemble
the old Fuel ISO build workflow where the artifacts built during
verify are the ones actually promoted - with the current method
the final build & tag (ran on OPNCI CI build servers) might yield
different results due to different docker build cache states;
* the locally built container image is tagged with the 'verify'
designator and not pushed to a public registry, only consumed
during verify's job 'deploy-virtual' phase;
JIRA: ARMBAND-401
JIRA: FUEL-383
Change-Id: I9b0d8079e759cdc895260219a8a4989411c995ff
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: I2d0a71fc40a4a6cd1f5b1e63ca429c5b83b7ad00
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
|
Keep running Fraser CI scenarios so Dovetail gets to run against its
intended baseline.
To keep POD usage down, schedule only baremetal HA scenarios,
3 Fraser scenarios per week.
JIRA: FUEL-381
Change-Id: I0cedf4ed38a146b4e6ad0e10bd3030ab0c1e833f
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
JIRA: FUEL-383
Change-Id: I80049726c256d2891ae1cfbacbc54781d3d81c70
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Added the triggers for both ha and noha versions of the scenario
Change-Id: Ibba782d82712b69b755592a878fc69bf6696cba7
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
|
Change-Id: I24cc328cdefcd7ac5f34292f0cf1635f797f8f00
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Now healthcheck includes vping_ssh, so remove it as a dedicated test
for verifying patches on gerrit to avoid double checking.
Change-Id: I4daec677e7d1fdc65997f7a9ab580d5f93ece8a8
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
Change-Id: I6a2b571ca2696f9466a4588b7e4deef13b947eae
Signed-off-by: xudan <xudan16@huawei.com>
|
|
JIRA: FUEL-375
Change-Id: I01f17a28fdb1bd692d1997b0a32be66de8856a8b
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Functest Docker has issues connecting to Openstack clusters on
Ericsson virtual PODs due to iptables rules interfering.
Apply old iptables workaround from functest, at least until we
rootcause and fix the issue on those virtual PODs.
JIRA: FUNCTEST-985
Change-Id: I01b6788e5dd7a9fd64e80e3e78d7cd8828570cb1
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
Change-Id: I2946684b8e5941201865c123793b7f5800b5421b
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
We will try to reuse the job template
for deploying from armband project.
Change-Id: I76a783094ce5be1b4aa93585a6b90898d909ca13
Signed-off-by: pava <Paul.Vaduva@enea.com>
|
|
global-jjb only supports the .yaml file ending for jjb jobs. Instead of
waiting for a release we're going to rename the files.
Change-Id: Icf3339eacd2320c583333e02250998cf6b1881f7
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
Using these macros for deployment jobs will report the deployment
results of Fuel to the testresults database[1].
[1] http://testresults.opnfv.org/test/#/deployresults
Change-Id: I353631f073578b4a2da0f08ffba4042931e65dca
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Enable Functest based gating for jobs:
- fuel-verify-*
- armband-verify-*
This includes Functest suite 'healthcheck' and testcase 'vping_ssh',
similar to Compass4NFV verify jobs.
While at it, remove 'basic' phase from verify jobs, as linting is
handled via separate jobs on Jenkins master and there's no other
reason to keep it around.
JIRA: FUEL-340
Change-Id: I11dce6998d7ac16e68cf2b9d72a1ed6b23ca2483
Signed-off-by: ting wu <ting.wu@enea.com>
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: Ib3fba4d6193cfa4dfa422163561cfbc8bcfa087c
Signed-off-by: jenkins-ci <jenkins-opnfv-ci@opnfv.org>
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: I90f42dc36ed0555788b517572088b5f09c1569fb
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
|