Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: Ia9939f489320b95bd417d3e25b2a5b99644f549f
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
|
|
|
|
JIRA: BOTTLENECK-85
Change-Id: I6ec45a7fa292ee69a75820d1ed9ce3fd82aebe5d
Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
|
|
|
|
forget to swagger-ize TestResult model"
|
|
JIRA: FUNCTEST-278
Change-Id: I53fa2eca6476c07ad513e72241d9715431cbdee8
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
and forget to swagger-ize TestResult model
JIRA: FUNCTEST-277
Change-Id: I5d8ddd9983484a61df9b77392d5ae24bde6a16dc
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
esp for heading spaces and if/else/fi
JIRA:RELENG-113
Change-Id: I9009cfec71be653e1009d8d59aec2f27d7206a8d
Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
|
|
Change-Id: I709dbf36667202ed0e1feb4793aa10071dc137c4
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: FUNCTEST-276
Change-Id: I2e40e12bc5b472aae88d294fb11dc479d5dd538c
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
|
|
JIRA: FUNCTEST-274
Change-Id: I64e5e1c0d1165ac7ad7ff59dfd824dc00e131cdc
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
JIRA: FUNCTEST-275
At least until we fix the issue with the python logger showing
the output twice.
Change-Id: I121b6164cd9dc263b0c6f87afb661f853bcca708
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
JIRA: FUNCTEST-273
Change-Id: I6f2b1de5488ba684d0c00e9f40daee2487a011cc
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
|
|
Change-Id: Ia56ceefe5bf93cf15f89133c40f0e23c678e11d3
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Also adds ODL_L2 to daily
Change-Id: Ic9e29d440988ff2eba42ae314cfc0f86313092f2
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: FUNCTEST-270
Change-Id: I82b1e3acee82d9b4931531c9404e13a663ff32de
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
|
|
Change-Id: Ib56f4675e840c05ab2ed331efef553362cd16fb3
Signed-off-by: meimei <meimei@huawei.com>
|
|
Change-Id: If9de486a95ed7a890d23abfe88f6eb70803d2cae
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
Change-Id: Ic18bafda91538d93ba66ee2969fec2949cecdb52
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Fixes include:
- SRPM extension was wrong, causing SRPMs to not be uploaded correctly
- No more redirecting stderr to stdout
- More print statements to Jenkins
Change-Id: Ib96bb1efd967d9510d14a2e63bdf7d97b5d07cb2
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
Add daily, verify and merge jobs for fastpath metrics project.
Change-Id: Ieeca12b0743cc4387ce6725b018360627b5164e7
Signed-off-by: Maryam Tahhan <maryam.tahhan@intel.com>
|
|
Change-Id: Ibe4b068fd667b796455be3fd4d9701d50879aace
JIRA: FUNCTEST-266
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
|
|
JIRA:RELENG-110
Change-Id: I7cf0a79cd7046878de50c0214837d266770560c1
Signed-off-by: zhifeng.jiang <jiang.zhifeng@zte.com.cn>
|
|
Change-Id: I2d27170c3797b1191dd39c3c9f6741a343acf70d
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Changes Include:
- Combined apex-deploy-baremetal and apex-deploy-virtual into the
apex-deploy.sh
into functions
- JJB modified to only use single builder for deploy
Change-Id: Ia129d8d6004b36c09bdb01685f2a0fced13bccea
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
- change POD names
- remove branch for local results
Change-Id: I8749cfe34e9819c42f859c9a1f2f5d5cce5ccbb1
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
rename pod_handler.py to pod_handlers.py
JIRA: FUNCTEST-264
Change-Id: I8699999776bdb238f680a128b83cea0a098534c5
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
JIRA: FUNCTEST-263
Change-Id: I293e05f565f882ea39bbf6368405f10241269716
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
|
|
|
|
This change switches compass jobs to use labels instead of tying
jobs to slaves.
The changes in detail are:
- Compass jobs can roam on any pod that is labelled with compass-baremetal
and compass-virtual.
- Above means that there is no branch/pod allocation anymore.
- New jobs are created in order to get rid of pod names from them and just
use baremetal or virtual in names.
- Old jobs are removed.
- Related test jobs are updated.
- huawei-virtual label is renamed to compass-virtual since we still have
installer specific slaves, not company specific. In future the job
might end up on a none-Huawei slave too.
- huawei-pod2 is not a CI POD so it is left in none-CI PODs section.
- block relations and triggers might require fine tuning and left to compass
project to decide how to adjust
Job structure remains same; one parent job calling 3 downstream jobs:
deploy, functest, yardstick.
The OS to deploy (trusty or centos7) needs to be solved in a separate patch
in a sustainable way.
Change-Id: I22bfaff36640667b6764f0e303a3286af0eb41b2
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
JIRA: FUNCTEST-262
Change-Id: Ib77bb080111392b8e3248c5e6152f55c12b8c67c
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
This change switches joid jobs to use labels instead of tying
jobs to slaves.
The changes in detail are:
- Joid jobs can roam on any pod that is labelled with joid-baremetal
and joid-virtual.
- Above means that there is no branch/pod allocation anymore.
- New jobs are created in order to get rid of pod names from them and
just use baremetal or virtual in names.
- Old jobs are removed.
- Related test jobs are updated.
- POD specific parameters are updated and instead of adding pod
specific parameters, they now become parameters for all the pods
labelled with same label. It is not a problem at the moment as
both Intel PODs (pod5, pod6) have same parameters but a different
pod with different parameters will require alignment between pods.
Job structure remains same; one parent job calling 3 downstream jobs:
deploy, functest, yardstick.
Change-Id: I30d270cd05ba3756f6f161d65ee5160eab6b80f4
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
|
|
JIRA:RELENG-110
Change-Id: I5c877d558bb04255a9e99dbe3459fba40217232c
Signed-off-by: zhifeng.jiang <jiang.zhifeng@zte.com.cn>
|
|
version - /versions
api - /api/v1/pods(projects/results)
dashboard - /dashboard/v1/results
I tried to make the code smart, but in vain, sad......
JIRA: FUNCTEST-261
Change-Id: I3e9e3ad7180a6c6349fd743e24eafea07bdefd1d
Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
|
|
Change-Id: I2e02f16173ec495e250bc60bc225ad1bb6a91828
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Having builders embedded in jjb makes maintenance harder than what
it could be and error prone so the builders have been taken out.
Apart from this, the upcoming change proposals will split yml files
in 2, aligning with the rest and jobs in these files can reuse same
builders when they are converted in shell scripts.
This is the first change in series, trying to align job structure
with the rest in order to ease the effort required to troubleshoot
the deployments during release verification. The changes are
- take builders out of jjb (this patch)
- align the main CI jobs with the rest; 1 parent job per scenario/branch
which controls triggering and execution of 3 downstream jobs;
deploy, yardstick, functest
- split yml file in 2; ci jobs ending in apex-ci-jobs.yml (daily) and
project jobs ending in apex-project-jobs.yml. (verify, merge, build)
Change-Id: I01f8bf351f0cbafbee1f41ec24ad5c2c6f21316f
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
This change switches fuel jobs to use labels instead of tying
jobs to slaves.
The possibilities and changes introduced with this approach are
- If things do not work as expected, slave-label parameter can
be set to certain slave name to get back to old way of
tying jobs to slaves.
- If a scenario requires a different slave, it can still be
created using baremetal or virtual but the label can be
different, pointing to a slave that is capable of running
that scenario. (fuel-baremetal-multisite, etc.)
- The auto-trigger-name for brahmaputra is moved under the
branch anchor and can be used like this if triggers for all
all the jobs for a certain branch need not to be triggered
automatically but job is still kept enabled in case if some
crucial bug needs to be tested.
- No of max concurrent builds stepped to 4 in order to use
all the labelled slaves available. This will require some
adjustments before colorado jobs start to run in order to
share resources between branches fairly.
- All the fuel CI PODs except lf-pod1 have been removed.
Change-Id: I91eca6743bb3d34263e634f9b74550efa1e2ddbe
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: I8c8c5b1d82e447fb7a7413368a919b3d3c7b99a6
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
its response"
|
|
|