Age | Commit message (Collapse) | Author | Files | Lines |
|
Build and push xtesting images
Create manifests for xtesting images
Build xtesting images for arm
JIRA: FUNCTEST-948
Change-Id: I3fbe6cdfef5b304a45d76533417f3c4bc58dddbe
Signed-off-by: Delia Popescu <delia.popescu@enea.com>
|
|
Change-Id: I454c327f3359688742b5d8c4299efee05d6494a2
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
|
|
It is not always practical to try determining scenario and installer
to run jobs programmatically. This change adds possibility to do that
by parsing commit message and skipping the automatic scenario and
installer extraction.
Change-Id: I10c9620fe8bb69a2d69fceb31d08084265aa1d75
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Fixes the following problem
[description-setter] Description set: Scenario: os-nosdn-nofeature | Node: intel-virtual14
[xci-verify-ubuntu-healthcheck-virtual-master] $ /bin/bash /tmp/jenkins7521920744845291696.sh
/tmp/jenkins7521920744845291696.sh: line 21: GERRIT_TOPIC: unbound variable
Build step 'Execute shell' marked build as failure
Change-Id: Iddf82e6ae6c6c433d941c461953c11935bc45269
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
|
|
Patrole is now integrated in smoke and the dedicated container is
being removed [1]
[1] https://gerrit.opnfv.org/gerrit/#/c/53659/
Change-Id: Ifb1989c5e430a4bf0fdd553f2e3e82f69a704f25
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
Sometimes we make global changes that affect multiple components at
once and splitting that is not possible because it needs to be shipped
as an atomic change. As such, allow topics with 'force-verify' to run
the CI using the default installer and scenario.
Change-Id: Ie4753822111b20c4f479886a55fe569c9b91ccd0
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
|
|
Change-Id: I5312ac784b1621ce968bbdfb1532859dada0e790
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Openstack APIs response call is tacking very long on ARM
Work is being done on fixing the issue
Temporary increase functest timeout on x86 too because of COMPASS
JIRA: ARMBAND-366
JIRA: COMPASS-589
Change-Id: I355500da56c5a040324c0969237ac2decfd29edf
Signed-off-by: Delia Popescu <delia.popescu@enea.com>
|
|
|
|
Variables injected by envInject are set after the job variables
which results in not setting the variable correctly. The Jenkins
test script now uses the variable injected by envInject to set
the INSTALLER_TYPE to XCI_INSTALLER.
Change-Id: Id79281a2ee22d407ffb1bd7c4be1471f6f329803
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
We need to work on functest healthcheck for Kubernetes scenarios.
Until we get it working, healthcheck is disabled.
Change-Id: If470dbe956c5859825f0829d1f8d022bdafcc242
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: Ifbe676cd347c2d3c68f04b5137f3ccaa83a95894
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
The scenarios named os-* are deployed by osa and the ones
named k8-* are deployed by kubespray. This change determines
the installer to use by looking into the scenario name.
The installers are currently hardcoded within xci-set-scenario.sh
script and this needs to be fixed for other installers when they
onboard to xci.
Apart from setting the installer, extraction of generic and external
scenarios are moved into corresponding functions.
Change-Id: I19882bcd2a1260765e601ecbe517551c60401d74
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
|
|
|
|
We do the VM cleanup as part of the postbuild process so we do
not need to have it in the functest jobs anymore.
Change-Id: I64e4b58837090df33ae529232ef15a19de8f198a
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
|
|
In
https://wiki.jenkins.io/display/JENKINS/Plugins+affected+by+fix+for+SECURITY-170,
it indicates that:
only build parameters that have been explicitly defined in a job's
configuration will be available by default at build time. Any other
arbitrary parameters added to a build by plugins will not be
available by default.
It has been tested in sandbox.opnfv.org that only defined parameters can
be passed to the triggered jobs.
For parameters required by TESTAPI are common to all the projectes,
including installers, Functest, and Yardstick, it is convenient to
define a common macro and used by others.
Change-Id: Iac1da85445e1b5d75109ccd64b174f35151b9969
Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
|
|
Change-Id: I44c47347ce8759a545245bf2d3ad6d6657226875
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
|
|
Switching to multijob forces to increase executors which is too risky
so closed to the release.
It basically reverts the previous functest-daily-jobs.yml [1].
[1] git checkout 7f06f9492f4f8dd47669a553ef6e9c967fa29e8e jjb/functest/functest-daily-jobs.yml
7f06f9492f4f8dd47669a553ef6e9c967fa29e8e
Change-Id: I4a461108b11effe59e49108e1d95a9aae6e81ade
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
It bypasses the missing senquential mode.
It also fixes exclusions about fds and patrole.
Several Functest could run in parallel but it's impossible from the
time being due to an xtables lock.
Change-Id: I831a8c995efbf2484afd86785f17f51981c921c1
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
Change-Id: I454ff72c377a96aa769919348b27813ad434eb89
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
Change-Id: I5289fedf52354f2cef6a3202df27d35acccb7c6c
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
|
|
Change-Id: Iaf8918942909e2b4b9608229f3fe0374efbd9d3f
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
|
|
Change-Id: I003f760adc2cb0b4959188b7f7d676d8fdbd8bb9
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
fingers crossed
Change-Id: I220a36ec8a6a0d95e847a5672c4d8e5c0d34c5ac
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
Remove and then re-add to see if we can get jjb merge to work
Change-Id: Iff380b38bbc5a69e2850cd91a99267b6d5b1128f
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
Change-Id: I88f33b7dcdf8f4d0a3aa3f8d46a07f10c62e6ae9
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
|
|
Change-Id: I1ce9e727a7f1448f657652a0f8d4bbab144b3ab9
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: I90f42dc36ed0555788b517572088b5f09c1569fb
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: Iad86593d0b2711505999d5b0446d241cf56d5c8b
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
|
|
|
|
|
|
Functest healthcheck job actually fails but due to not setting
options properly in run-functest.sh, we failed to notice this.
Please note that this patch will enable changes to be blocked
since creation of external network and associated subnet fail,
due to an upstream issue. This causes functest healthcheck to
fail which in turn results in Verified-1 on Gerrit.
Change-Id: I32eeb422895930d039d3289ffb65e10763db9c4b
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: I19e60eea65b01ec22bb32c0efcdc6b071b22ca34
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
We are going to try this again. Once this is merged, I will need
to delete all the jobs that change job type and then re-merge
releng merge will be broken during this short window.
--- original commit message ---
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
Original patch by Delia Popescu <delia.popescu@enea.com>
Change-Id: I43422463c442ff6a18f6a98ab9909fc6c88e0259
JIRA: FUNCTEST-917
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
The clean VM normally stays around after the job is completed or killed
due to timeout. Unless a job for the same distro is scheduled on the
same node, that VM will state around for a while consuming valuable
system resources. As such, we should remove it after the job finishes
to free up resources for the new jobs.
Change-Id: I88b5e32797969d9378588199a7ddb013bbe740c9
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
PostBuildScript plugin's result affects Jenkins pipeline, so we should
return the original job running status in the postbuildscript in the end
Update macros:
1. from $POD_NAME to $NODE_NAME
2. from $SCENARIO to $DEPLOY_SCENARIO
2. {installer} to $INSTALLER_TYPE for {installer} is not existed in
trigger job
3. add parameters definition for they can not be used in trigger jobs by
predefined-parameters
4. missing TIMESTAMP_END
Change-Id: I354be3d5ad02e53bb988995adc09b59e92a1640a
Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
|
|
replace `include-raw-escape` with `include-raw` for no jjb macros in the
bash file.
Change-Id: I6125779f23a5aafd7fed0f5017c4280394624bcd
Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
|
|
|
|
|