Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: If6d4f6b2ac0266af35b150159a752b8b6f48ad83
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Add slave params for flex-pod1
Change-Id: I25e93fe2231e604321f8ea7ca18eba45ecc3ee13
Signed-off-by: Siddharth Gogar <siddharth.gogar@flex.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fuel@OPNFV mcpcontrol network (equiv to old admin/PXE net) has been
configured to use 192.168.10.0/24 during E release cycle.
However, due to overlapping with Ericsson-pod1 networks, we decided
to re-use the old CIDR Fuel used before E release (10.20.0.0/24).
This allows reusing the INSTALLER_IP param instead of recently added
SALT_MASTER_IP param.
Current change refactors all usage of SALT_MASTER_IP in favor of old
INSTALLER_IP, thus reducing complexity and providing a familiar env
to leagcy Fuel users.
JIRA: FUEL-285
Change-Id: I1e89cca08ce4cb9bf3a82a06043c91ee26aa0794
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
JIRA: RELENG-254
Change-Id: I8c644ac0bce05f66b1b878e39a00342c857d23f0
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
JIRA: RELENG-254
Change-Id: If4bfdc2ddaadb4e17d0bc0dc2948780bcbbb10ae
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
JIRA: RELENG-254
Change-Id: I118b0dc0bb58919bc7d25f5d6a8247731e58c409
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
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>
|
|
JIRA: RELENG-254
Change-Id: Iab88e0adffb84b5eead7991035dc064b6017b5b5
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
JIRA: RELENG-254
Change-Id: I0e168d0ce619df20480f6da92cdfa470dca713b1
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
JIRA: RELENG-254
Change-Id: I9a68c230464bb60087e8a909a2d59021f3acd272
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
JIRA: RELENG-254
Change-Id: Ibfda27a637ee448862ae2df5884b88093210ed4d
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
JIRA: RELENG-254
Change-Id: If3c2d8b469c97997a3fdcbcaf4750acb61c82d75
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
JIRA: RELENG-254
Change-Id: I73fa2c56f7adf2a5dabcc9c0fd9db85c2cfa82a0
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
JIRA: RELENG-254
Change-Id: Ib7a7db3dc0d463bae6fc159a7c0ade7be51f4e1b
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
JIRA: RELENG-254
Change-Id: I56e1b6e776cac44afc17cf73db09cf8220d1b5f0
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
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>
|