You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here leveraging on Xtesting will ease building CI/CD toolchains in few commands mixing Functest and StorPerf-based testcases. It also simplifies any validation process as it avoids extra logics per test frameworks (jenkins job templates, certification, etc.) https://wiki.opnfv.org/pages/viewpage.action?pageId=32015004
The text was updated successfully, but these errors were encountered:
@rabi-abdel @mf4716 I would appreciate a quick clarification about the RC1 Co-Lead scope.
From my understanding here, the issue must be assigned to StorPerf PTL or contributors, any CNTT-OPNFV liaisons or RC1 leader. On the other hand, this role raises side effects vs my Functest PTL role regarding the false RC tables introduced in OPNFV TSC meeting (and possibly in CNTT governance?).
To avoid a lots of spams as it happened in December, I would suggest to close this issue and the similar ones per OPNFV projects. Agree?
Xtesting allows a smooth integration of sparsed testcases and ease building CI/CD toolchains via an Ansible role.
http://testresults.opnfv.org/functest/stockholm/
Here leveraging on Xtesting will ease building CI/CD toolchains in few commands mixing Functest and StorPerf-based testcases. It also simplifies any validation process as it avoids extra logics per test frameworks (jenkins job templates, certification, etc.)
https://wiki.opnfv.org/pages/viewpage.action?pageId=32015004
The text was updated successfully, but these errors were encountered: