Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
This information was previously fetched from securedlab, via a
POD-specific "local_env" file which was sourced at deploy time.
Since this information can't be parametrized via PDF, nor is it
sensitive enough to hide in securedlab, move it to releng.
Change-Id: Ia4e244ceb534c49b1ecda5be798470a81c68b494
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: Icac677ac9e17b4b4ae4e7fc82139587cc201bcb6
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: RELENG-254
Change-Id: I9b6017724ae1566a8651e187d372506ee6bb0373
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
JIRA: RELENG-254
Change-Id: Ia9246b4fee30ea350b57563241fb83c4f03a3b55
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
JIRA: RELENG-254
Change-Id: I48ab499f4f5b70657fa67c9f44ef430fdd1a9e9d
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
JIRA: RELENG-254
Change-Id: I446c7820204757b46866fbff180a83ff2b757c3b
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
JIRA: RELENG-254
Change-Id: I830f05e7b005195580aa1d24e977c132c6278f86
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
This patch should unblock:
https://gerrit.opnfv.org/gerrit/#/c/40533/
Change-Id: I72e827b0feae559e6477d213d0f752ed04cd62b3
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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>
|
|
Remove the '-q' arument to git-branch in the generate-job-diff script
as the git version on Jenkins master is too old.
Change-Id: I869a9713e75604600adf3ee8b8b96386ad4a8ff0
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Add OSA adapter so that we could benefit from it in functest integration
Change-Id: I010a6f2b6c75711d0cc80f8fd130604c41b6d1e6
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
|
|
Handle the error and show appropriate message,
without showing the entire error to the users
Change-Id: Ib5213190efc1e87d56a7329a4572b525a5e16a12
Signed-off-by: thuva4 <tharma.thuva@gmail.com>
|
|
remove the unnecessary "$rootscope" in the controller's parameters.
Change-Id: Ia048af9e146e871003307af27faca24a5ee225ca
Signed-off-by: thuva4 <tharma.thuva@gmail.com>
|
|
Update nightly build to only push the RPMs if they all exist. Also, only
push the properties files if all the RPM pushes are successful.
Change-Id: Ied64e203504ae6092c6ea3d21b474649584860ac
Signed-off-by: Maryam Tahhan <maryam.tahhan@intel.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>
|