Age | Commit message (Collapse) | Author | Files | Lines |
|
These jobs run periodically against the HEAD of master and stable/ocata
branches in order to attempt provisioning and help us to find more
recent working versions to pin.
In perfect world, these jobs should be run post-merge, helping us
to move faster but lack of resources prevent us doing that.
Change-Id: I6f6b2fcc58eda112b1e811a7b11269e928bbceef
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: Idc5ca86dbc51d83860f26244a4ed7d88015552d0
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I42f8836320e4bce2f890aa4a17d59f53efab7f97
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
By default, if a docker build job triggers and
there is another one running at the same time,
it will abort the job.
This adds a wait method with a timeout to avoid that.
Change-Id: Ica86885c60ce4137c85474ec4b7441ac5bab600c
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
test"
|
|
|
|
|
|
JIRA: DOVETAIL-377
Since there are two wrappers in dovetail-ci-jobs.yml and dovetail-weekly-jobs.yml,
respectively, the first wrapper (build-name and timeout) is disable.
Combine them into one wrapper with build-name, timeout and fix-workspace-permissions.
Change-Id: I4a4f766fc90612be2642bc01708d93392fb163ed
Signed-off-by: xudan <xudan16@huawei.com>
|
|
recently I plan to make some effort on TestAPI,
add scenario processing exceptions, perfect swaggr documents,
refactor unreasonable coding...etc, all of those will not change
the original process or data structure, whilst many patches
will be submitted. Because there is latency during TestAPI update,
and it will cause test results lost, so I think it is better to
disable TestAPI automatic update for now and re-enable it when the
work gets done.
Change-Id: I5ceab808350a1ece500c8743622d197326aa5419
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
- was grabbing stackrc for SDN_CONTROLLER_IP, but it actually in overcloudrc
- need to skip hostkeychecking for scp operations
- change permissions and ownership of /tmp/.ssh/ files so jenkins-ci can
take over as the user
Change-Id: I2d8f3aadfd6eff35a288a4e49eabb035bb2560ef
Signed-off-by: Jamo Luhrsen <jluhrsen@redhat.com>
|
|
JIRA: RELENG-196
JIRA: BOTTLENECK-148
The path for calling docker_cleanup.sh is incorrect which causing
building job fail. This patch is to fix the issue.
Change-Id: I2a8ea79383123f541f4e67bc58a3f2f3e3d9beeb
Signed-off-by: yuyang <Gabriel.yuyang@huawei.com>
|
|
|
|
|
|
/opt/stack is being created by bifrost so the destroy-env.sh
script should be responsible for cleaning up all the remnants.
That way we can use the destroy-env.sh script outside of Jenkins
as well.
Change-Id: I72d9737cf2446ff3ffc02f195337a6873eceb5c0
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
A non-ci pod is made ci-pod for danube release, therefore this patch
modifies the cron jobs to be 4 hours apart instead of 8
This commit should be merged after the lable of the pods are changed
Request: OPNFV Helpdesk #39128
Change-Id: Ic88180d01d9ea03d03b79355cd78891ad612c59b
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
|
JIRA: DOVETAIL-377
workspace wipe clean error log
https://build.opnfv.org/ci/job/dovetail-compass-virtual-debug-master/365/console
this is caused of wrong permissions with files under $WORKSPACE
seems the former method in dovetail-run not take effects(log into host, it's still root:root,
not $USER:$USER_GROUP)
use global fix workspace permission in wrapper to replace former method
Change-Id: I6ceaaf630590666f3b3db5f2628334879df2b8fb
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
|
|
|
|
bifrost-verify jobs have been using this without issues and it is
needed for many other jobs in order to avoid unnecessary failures.
This change makes workspace permission fix prescm step a macro.
Change-Id: Ib5678dbf21c17ce640a600d2a06ebed9674663fa
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
|
|
Change-Id: I1d1b07fa3273a8766e0ec109d89e6c81b2d515d1
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
According to FDS folks, uio_pci_generic (default) should work with UCSB
baremetal. We also hit a bug in UCSB where vfio-pci isn't working with
VPP. Therefore falling back to uio_pci_generic.
Change-Id: Id9a6fe5be91aaf8476292a46c15c6e876616f4a6
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
JIRA: DOVETAIL-377
Change-Id: I55eebdd55c2cf91d74d166b0b31a0601efe0a751
Signed-off-by: zshi <zshi@redhat.com>
|
|
This patch is used to add forbidden-file-paths so that kvmfornfv
verify job will not be triggered if the patch includes changes
only to docs/
Change-Id: I9de20549507be2eadaba7c99bc6de3b28d3c3ce1
Signed-off-by: Gundarapu Kalyan Reddy <reddyx.gundarapu@intel.com>
|
|
JIRA: RELENG-196
JIRA: BOTTLENECK-148
The bottlenecks_cleanup script can not clean some dockers and
their images that created by docker-compose.
This may cause the following test using dockers
created in last test. This patch is to fix this issue.
Change-Id: I83d294020596ad5d04302793084a432cae789685
Signed-off-by: yuyang <Gabriel.yuyang@huawei.com>
|
|
JIRA: RELENG-195
JIRA: BOTTLENECK-143
The name of stress test in Bottlenecks has been changed
due to the new entrance for it.
So CI job for the stress test should be adjusted.
Change-Id: I8432ea1c2dacb6cf42f09a5b74c3c6a93970a242
Signed-off-by: yuyang <Gabriel.yuyang@huawei.com>
|
|
with tag:<None>"
|
|
Change-Id: I9c33e6661b2dce1b0e5a77d3ed47bf7eebd3bb2c
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
Change-Id: I0b0b33cf3021e2c0fb868eca749ab61eed7b3792
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Sometimes 'gsutil rm' may fail for unknown reasons like the following
one:
[...]
/ [7/10 objects] 70% Done
/ [8/10 objects] 80% Done
/ [9/10 objects] 90% Done
Operation completed over 10 objects.
CommandException: 1 files/objects could not be removed.
Try a few more times to remove the objects before giving up.
Change-Id: I6905a806446dac41ddc43d4195514a5233480ccd
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
|
|
Daily jobs will use pinned versions of bifrost and openstack-ansible in
order to make sure we use known good versions for them since focus of
the daily jobs is OPNFV platform testing.
Ansible log can easily become massive depending on the level it is set
and it is not so relevant for daily jobs to have it like this due to
less probability of dailies failing to provision/deploy.
On the other hand, the jobs that verify/test bifrost and openstack-ansible
will have max verbosity enabled to troubleshoot these components themselves.
New set of jobs will be created running periodically against the HEAD
of master for bifrost and openstack-ansible to catch working versions
and help us promote them to use for daily platform jobs. Verbosity of these
jobs will be enabled like how we are doing for bifrost-verify jobs.
Change-Id: Ic9fd2ff418fdaa3ad7fbfc22d8ec2dc1174df65f
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
|
|
This patch will enabled the auto build of K8 scenario in jenkins
for master and Danue.
Change-Id: Ic79b79a298358d932e0162ce1c739008c2f788a4
Signed-off-by: Narinder Gupta <narinder.gupta@canonical.com>
|
|
Change-Id: I3d9d9b8b7c3de0c22a62945de027b9e8994d35e8
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Jobs are adjusted as well.
Change-Id: I0bc5bdda37277053d81d7da394e0156902da817a
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
1. The Dovetail tool itself needs openrc file as the input rather than
INSTALLER_TYPE and INSTALLER_IP.
See JIRA: DOVETAIL-369 and JIRA: DOVETAIL-371
2. Now Dovetail CI jobs just give INSTALLER_TYPE and INSTALLER_IP
to Dovetail tool.
3. So Dovetail CI jobs need to fetch the openrc file before
and run Dovetail tool with the openrc file.
JIRA: DOVETAIL-372
Change-Id: I3a6293da621ae0a2f5d72a297d3d912fd60e05d8
Signed-off-by: xudan <xudan16@huawei.com>
|
|
|
|
- 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>
|
|
tag:<None>
JIRA: RELENG-194
Now, in CI, bottlenecks job will pull yardstick Docker image again, which may
cause the tag of the Docker image previous used by Yardstick changed to 'None'.
Using 'None' tag to remove Docker image will cause error.
Change-Id: I5c63c6c515ede5da4f6a40be6bb22fa6771f8f09
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
|
|
missing \" for if condition
use qtip temp dir for tempfiles
Change-Id: I696b81b2e017f630051353f10b96f07fb85e2ec2
Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
|
|
|
|
|
|
|
|
Change-Id: Iaae8a4b524ae804fd0efd75c656aae94c1c92a7e
Signed-off-by: ShubhamRathi <shubhamiiitbackup@gmail.com>
|
|
|