Akraino JIRA https://jira.akraino.org This file is an XML representation of an issue en-us 9.4.5 940005 11-04-2023 [VAL-78] Push CI logs to nexus https://jira.akraino.org/browse/VAL-78 Validation <p>The CI templates to run validation have been submitted in ci-management by <a href="https://gerrit.akraino.org/r/c/ci-management/+/1657" class="external-link" target="_blank" rel="nofollow noopener">https://gerrit.akraino.org/r/c/ci-management/+/1657</a></p> <p>The jobs also need to push the logs in Nexus</p> VAL-78 Push CI logs to nexus Task Medium Done Done Valentin Radulescu Cristina Pauna Tue, 29 Oct 2019 13:36:34 +0000 Tue, 18 Feb 2020 15:06:18 +0000 Tue, 18 Feb 2020 15:04:31 +0000 0 3 <p>Hi,</p> <p>Logs are now pushed in nexus.</p> <p>Valentin Radulescu</p> <p>Hello,</p> <p>please be aware of the following requirements:</p> <ul> <li>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.</li> <li>The &lt;Lab silo, timestamp&gt; pair produced by each test validation execution should be unique. It is the lab owner's responsibility to guarantee this.</li> <li>Every lab owner must push results to nexus using a specific URL format, that is <a href="https://nexus.akraino.org/content/sites/logs/" class="external-link" target="_blank" rel="nofollow noopener">https://nexus.akraino.org/content/sites/logs/</a>&lt;lab silo&gt;/bluval_results/&lt;blueprint name&gt;/&lt;blueprint version&gt;/&lt;timestamp&gt;/results/&lt;layer&gt;/&lt;test suite name&gt;/</li> <li>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.</li> <li>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</li> <li>The level of depth of suites inside the 'output.xml' must be 3, for example s1(root test suite) -&gt; s1 (test suite) -&gt; t1 (test case 1). So, the lab owners must run the bluval robot tests from a specific directory.</li> <li>The test_info.yaml (contains the tested layers and whether optional test cases have been used) must be stored in the location <a href="https://nexus.akraino.org/content/sites/logs/" class="external-link" target="_blank" rel="nofollow noopener">https://nexus.akraino.org/content/sites/logs/</a>&lt;lab silo&gt;/bluval_results/&lt;blueprint name&gt;/&lt;blueprint version&gt;/&lt;timestamp&gt;/results/</li> <li>Old results stored in Nexus should not be changed</li> </ul> <p>Here is the link of the abandoned patch that was used in order to run validation results and push results to Nexus:</p> <p><a href="https://gerrit.akraino.org/r/#/c/validation/+/1647/2/utils/validation_jenkins_job.xml" class="external-link" target="_blank" rel="nofollow noopener">https://gerrit.akraino.org/r/#/c/validation/+/1647/2/utils/validation_jenkins_job.xml</a></p> <p>We should use this patch as a guide and extract all the necessary info.</p> <p>Also, the script used by the aforementioned job in order to push results in Nexus can be found in </p> <p><a href="https://gerrit.akraino.org/r/gitweb?p=validation.git;a=blob;f=utils/send_logs.sh;h=5a26da59acd548ae60d54850fc4a8d684389940c;hb=refs/heads/master" class="external-link" target="_blank" rel="nofollow noopener">https://gerrit.akraino.org/r/gitweb?p=validation.git;a=blob;f=utils/send_logs.sh;h=5a26da59acd548ae60d54850fc4a8d684389940c;hb=refs/heads/master</a></p> <p>It is under the validation repo. Maybe we should consider moving it under the ci-management repo.</p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> Development Rank 0|i002jo: