Hi,

Logs are now pushed in nexus.

Valentin Radulescu

Hello,

please be aware of the following requirements:

• Every lab owner must be provided with a unique lab silo by the LF. All the validation results produced in the owner’s lab must be stored in Nexus using only this silo.
• The <Lab silo, timestamp> pair produced by each test validation execution should be unique. It is the lab owner's responsibility to guarantee this.
• Every lab owner must push results to nexus using a specific URL format, that is https://nexus.akraino.org/content/sites/logs/<lab silo>/bluval_results/<blueprint name>/<blueprint version>/<timestamp>/results/<layer>/<test suite name>/
• Every test validation execution must produce a file with name 'output.xml‘. This feature is supported by the bluval.py. The ‘output.xml’ file must be stored in the URL mentioned in the previous bullet.
• The format of results in the 'output.xml' file must be produced by the bluval robot test execution. This format is a specific one and it must not be changed. This feature is supported by the bluval.py
• The level of depth of suites inside the 'output.xml' must be 3, for example s1(root test suite) -> s1 (test suite) -> t1 (test case 1). So, the lab owners must run the bluval robot tests from a specific directory.
• The test_info.yaml (contains the tested layers and whether optional test cases have been used) must be stored in the location https://nexus.akraino.org/content/sites/logs/<lab silo>/bluval_results/<blueprint name>/<blueprint version>/<timestamp>/results/
• Old results stored in Nexus should not be changed

Here is the link of the abandoned patch that was used in order to run validation results and push results to Nexus:

https://gerrit.akraino.org/r/#/c/validation/+/1647/2/utils/validation_jenkins_job.xml

We should use this patch as a guide and extract all the necessary info.

Also, the script used by the aforementioned job in order to push results in Nexus can be found in 

https://gerrit.akraino.org/r/gitweb?p=validation.git;a=blob;f=utils/send_logs.sh;h=5a26da59acd548ae60d54850fc4a8d684389940c;hb=refs/heads/master

It is under the validation repo. Maybe we should consider moving it under the ci-management repo.