Age | Commit message (Collapse) | Author | Files | Lines |
|
The external network, docker installation and other parts need
to be fixed in OPNFV host before functest can be enabled.
Change-Id: I42a3adf2e36f91e6425d49e2578003b52ca4f101
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
|
|
The following alpine containers will be launched one after the others:
- healthcheck
- smoke
- features
- vnf
Old container is kept for suite (which could be refactored later)
Jenkins exit condition (return_value) and push_test_logs to be checkeded.
Regarding the return condition, I did not reapply the mechanism that returns false
when one of the test suite is FAIL. This was misleading for lots of people as
for them, red means functest is FAIL.The argument was, if functest jenkins status
is blue, people believe that tests are PASS and do not consider the results, which
may be FAIL, which may be also misleading...
Due to the refactoring I think we can be more Functest Centric and consider
that if we succeeded in running the test, our CI status shall be PASS (same
behavior than other test projects..HA test FAIL in yardstick do not prevent blue
status).
Scenario owner must have a look at the reportign page to get more details.
Functest PASS means that tests have been succesfully launched, so they know that
there are available results
To summarize
previously Functest OK but 1 or more tests FAIL => red status in Jenkins
currently Functest OK but 1 or more tests FAIL => blue status in Jenkins
Regarding the push to artifacts, it should be transparent (volume) but the last
log links listed on huawei-virtual5 are broken [1]
[1]: https://build.opnfv.org/ci/view/functest/job/functest-alpine-compass-huawei-virtual5-daily-master/27/consoleFull
Change-Id: I4ed036dda3daae3d46726e5946f9d04897bab9bb
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
|
|
|
|
|
|
Since landing page have changed from reporting2 to testing,
the nginx configuration need some adoption.
If the pre url change again, we need to config the base_url when start
our docker container. For example:
docker run -itd -p 8084:8000 -e SERVER_URL testresults.opnfv.org/xxx/api opnfv/reporting:latest
Change-Id: If3c9f9af76fcfc8047b5b9559fcc8bd45740d4d2
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
|
|
|
|
Change-Id: I63e361eebe1345a34086ecbe99aba4504cb0f5bc
Signed-off-by: xudan <xudan16@huawei.com>
|
|
pbr can inject requirements into the install_requires, tests_require
and/or dependency_links arguments to setup.
It finishes cleaning the requirements management [1] for all OPNFV
projects integrated by Functest.
[1] https://wiki.opnfv.org/display/functest/Requirements+management
Change-Id: I30b76db8dcaba809e0b314fbd06ae04d24c8baca
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
This change fixes the following issues:
1) 'nounset' will cause the script to fail when activating a virtualenv
since the activation of a virtualenv unsets variables
2) There are not artifacts available from releng-merge-jjb and copying
them would save minimal time over re-running jjb
Change-Id: Ifc4297947c8fe235987a507ead932841480165a7
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
repo [1]"
|
|
Change-Id: I34a555697d963efc38064a7b53f25191d6bf1382
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
|
|
Previous commit extended the SUDO variable to include '-E', but
failed to properly quote the full `sudo -E` string, resulting in
"command not found" errors.
Change-Id: I266aa5259f09c3605e1c5a7ad165397ce83be0bb
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
Due to bug with forbidden file paths conflicting with file paths this
explicitly defines all the file paths in apex. This isn't the greatest
solution in the case where someone adds a new folder, but chances are
they will also modify one of the other files as well. Note it also
fixes a bug where unit tests woudl run twice because it would be
triggered as part of apex-verify-master and apex-unit-tests-master.
Change-Id: I6b10f8eb70c2cd7c8dd5c01363e06b7458c00127
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
|
|
|
|
Functest daily is based on the functest alpine dockers:
- healthcheck
- smoke
- features
- vnf
Change-Id: I922f3a5946e8bc06229fb03a959abd2bfead132b
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
|
|
|
|
|
|
|
|
It has been transfered to sample vnf repo [1]
[1]: https://git.opnfv.org/samplevnf/tree/VNF_Catalogue
Change-Id: I418151bd24517efeb66fc0ae76cb9e091bd130f6
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
1. Jobs on Compass often timeout
2. Apex jobs on huawei-pod4 will trigger 2 jobs at the same time. They will be
conflict.
JIRA: DOVETAIL-491
Change-Id: I5297bfb01c45c15cce7ab1438d8eed3dd9c7ff07
Signed-off-by: xudan <xudan16@huawei.com>
|
|
AArch64 build runs inside a VM, which tends to be slow.
Until we move all AArch64 builders to baremetal, let's increase
the timeout from 30 min to 60.
Change-Id: I0e16d32ac1cbe8f13b24e3cadb87715f12360d7a
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: I19fff409b5e8335ff44f0d9ba8167d3e882a9ad5
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Each time a patchset is created that has an effect on Jenkins jobs, a
non-voting job will trigger that comments to Gerrit which jobs are
added, modified, or deleted.
This should help developers judge the overall impact an individual
patchset may have on Jenkins since JJB macros can be expanded to
any number of jobs.
Change-Id: I99f9b68bc7933abfa39a941d6e65a73f62e58e56
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: Ide3c39d508d26be40e73cec13cd00eace984b6cc
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
SSH_KEY and other env vars set by Jenkins should be preserved
when using sudo to invoke the Fuel deploy script.
JIRA: FUEL-280
Change-Id: I495589a4a0519b3a5052cd5e5dc3122f9e49c215
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
JIRA: FUEL-280
Change-Id: I95559dcafbd179e5b7305dd0f23a7b3d89056888
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
|
|
|
|
|
|
Changing the url of the reporting to the original one.
Change-Id: I2973a4b7d28cbdd725a4764dffbf777c3fc2e937
Signed-off-by: Sakala Venkata Krishna Rohit <rohitsakala@gmail.com>
|
|
this should make forbidden-file-paths work
Change-Id: I18d63bffb92abd916eae54c7aafe9a8e1e98926f
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
Change-Id: I360cd5ba894022cd30cf7237e8338ab2e213c940
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Functest CI logs have been FAIL with compass but the CI logs are not
explicit. Remove a redirection to /dev/null to get something more
explicit
Change-Id: Icdf17595b051ccba6c58cbe86ab546e5693375ab
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
JIRA: BOTTLENECK-158
It seems the build_tag is not automatedly passed to docker.
This patch is to try to pass build_tag to Bottlenecks docker.
Change-Id: I783d6f0702040449b0385d11bca709f8cdbdd58a
Signed-off-by: Yang Yu <Gabriel.yuyang@huawei.com>
|
|
Temporary solutions relied on ollivier/functest-* but
now opnfv/functest-* are well produced and can be used as official
reference for CI
Change-Id: I02b5a03929d5b31df0db2a6c4722edf62b920df9
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
very basic approach based on 1 case posca_factor_ping
Give a feedback on the CI activity of bottlenecks
Change-Id: Iaa84abac6b00ba48a771250433a9f9a068de453f
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
|
|
|
|
|
JIRA: FUEL-279
Change-Id: Ie87ecaee17d6bb29776c3056274c59c1264762de
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|