Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
Change-Id: I6387ca1f7eaf107f735eab82917d77b2f3a3d90a
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: Iccd7ef674c9b80daba511f45cc48f403ca0f3e0b
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: Ia2caeef24a199580a9eeb2ba6214fa2008f65c1c
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
When a patch comes in for an external scenario, Gerrit Trigger injects
refs for that patch for the corresponding project. With the previous
configuration, job attempts to get that patch for releng-xci instead
of the actual project.
But switching to the right project causes Jenkins jobs to fail since
the releng-xci will not be checked out to WORKSPACE.
This change makes the clone for the repo/patch work and then it wipes
out the WORKSPACE and clones releng-xci there to get the actual script
parts to work.
Change-Id: Ide31c21a209dff953118f51e9b09de1d206a3085
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: Ib58ff1a8b093af550f86d337327114df50da4ae7
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: Ic706c120ac879741d5562427a6c3e90162223762
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
|
|
fix the error Unrecognized macro 'DEPLOY_SCENARIO' and deploy failed.
Change-Id: Ic34a0d99c2a6026303046c2b350da205372ec78e
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
|
|
|
|
Time to go live.
If this breaks I have shell on these machine and can fix
but should be fine
Change-Id: I616797cd3512b594d1daa846308e7a8643fb9cb0
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
must be run on the same builder each time.
output goes to /tmp/ its just a textfile per slave.
hasetbin stopped working, so I turend off the silly graphs.
Change-Id: I7300710c338f74e5426ab3cd2e2707ac2553f982
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
|
|
This reverts commit 7b9734aaca2fb04d1d8750b755a2880d60176889.
Change-Id: I5926d8013e57f2f0a68985b91aa8ab746bbbf1ab
|
|
In commit I77d5d66c0146f943d805612ca5b47e2eed3ffc41 the 'ts' utility
was added in order to print timestamps for deployment. However, this
breaks the exit code since 'pipefail' was not set so every job was
returning 'success'.
Change-Id: I2625a655a7334b1e43b690618821e69377075ed1
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
1. Download 3 extra images for functest snaps_smoke and cloudify_ims
2. Remove the modification of fuel openrc file because of this patch has
added a function to check cacert file
https://gerrit.opnfv.org/gerrit/#/c/52021/
Change-Id: I2cab3bf11231d5d6ad39dca6d2d833355b1e6679
Signed-off-by: xudan <xudan16@huawei.com>
|
|
|
|
I set -x in a test and then it did report.
not sure what's going on here,
I thought this was fixed.
May as well cat the violation log as we debug
Change-Id: I142fb3855ebc000ee90aa24e0ecb336bb9b313df
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
Add support for functest tier with multijob
Add publishers separate for fetures and
all other functest tiers
Run functest features suits in a mutijob
Since there are no arm specific requirements,
remove arm-daily builders and jobs
JIRA: FUNCTEST-917
Change-Id: I92e3d7ca378dd6d293520c679c741de4bf336639
Signed-off-by: Delia Popescu <delia.popescu@enea.com>
|
|
Includes the name of the PTL but should be just the email.
Change-Id: If6ef3b7c15defd44c6f86a24d6250840c37dd24b
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Copying the keys required for talking to JIRA and disabling the job
until chages can be tested to ensure a deploy runs successfully.
Change-Id: Ib3602338cfe06d5507f5d3f5b853906feb39f4c5
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Move generation of artifacts.opnfv.org/index.html
and sub pages into a jenkins job.
Script was run on cron on master previously.
run on lf-build2
Run job once per hour (it takes a long time to run)
Block if job is already running
Change-Id: Icc03cac61a802e036e4af8a9b9e3a244e147abea
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
We can use the 'ts' utility to print timestamps on every executed
command so we can keep track on the duration of each task and the
job overall.
Change-Id: I77d5d66c0146f943d805612ca5b47e2eed3ffc41
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
|
|
|
|
|
|
Change-Id: Ia1e05db344e6e6b4a773bf17157488716ac0c305
Signed-off-by: Jose Lausuch <jalausuch@suse.com>
|
|
The bifrost regexp was wrong leading to conflicts betwen the XCI
and bifrost jobs. Moreover, we need to add the same restrictions for
jobs/node on bifrost jobs similar to the XCI ones. This finally fixes
the 'throttle' property to use the 'xci-verify-virtual' category.
Change-Id: I6d3f8fdd82738c1d079b1a3fdef134753eb4281a
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
|
|
These are no longer needed since the server has been migrated, and a git
clone already exists in the workspace.
Change-Id: I07b5ff9185323d7295578b23a634e2d0e03afcd7
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
The bifrost jobs could run in parallel with the XCI ones so it may take
longer than 90 minutes to complete. Lets double the timeout value in
order to ensure that we don't fail due to a Jenkins timeout.
Change-Id: I53a442f434d839d891bf03e41ba1a6a4459fd878
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
We shouldn't allow the merge jobs to run in parallel with the verify
ones when both are testing the same distro since one may wipe the
'clean VM' of the other one. Moreover, we should restrict the number of
jobs allocated on nodes in order to avoid overloading them.
Change-Id: I9c0b9b5061e41b21c01789fc4676e72e0e082f17
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
This change extracts the scenario that is impacted by the patch
which triggered the verify jobs and saves the scenario name into
java properties file. This file will then be used by envInject
plugin to inject the scenario name into the build environment.
If the triggering change impacts multiple scenarios, the build
will result in failure and the developer will be informed about
a possible way to rectify the issue.
Support for generic scenarios will be introduced in subsequent changes.
Change-Id: I6406299c1352b6e9b8a9297c5441adf03445be33
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
Change-Id: If5c5b828312dc588515589b8075b9754537b8f86
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: I3fd11c6efb13f46ec74a0237a180497397cdfefe
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
We were missing concurrent on this job which was preventing parallel
execution.
Change-Id: I4d1ea62aef2a321220799cebee008f494490886c
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Remove passing node params and enable global queue scanning. Hopefully
this will allow 2 apex-virtual jobs to run at the same time (1 per each
slave).
Change-Id: I310dbc477e267c302d50599bab2a933ce988dba7
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Scenario list for Fraser:
https://wiki.opnfv.org/display/SWREL/Fraser+Scenario+Status
Change-Id: I083dc5b0b9cea9f91d7a9568a05df5865aeafa05
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: Ied442837e4e9fd25946590d3dbada6ff2cbe7fc3
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|