OpenDaylight JIRA

OpenDaylight JIRA https://jira.opendaylight.org This file is an XML representation of an issue en-us

8.20.10

820010

22-06-2022

[RELENG-69] Create autorelease job to verify non SR projects upstream changes https://jira.opendaylight.org/browse/RELENG-69 releng <p>We need an autorelease job to verify non-SR projects (odlparent, yangtools) changes before they get released and consumed by downstream:</p> <ul class="alternate" type="square"> <li>A first attempt of the job could just take a version (SNAPSHOT or release) of odlparent and yangtools and bump all SR projects to use this version instead of existing release. The resulting distribution could be sent to some sanity CSIT for verification. The goal for this first version is to detect breakages before the upstream project releases. This job could run periodically.</li> </ul> <ul class="alternate" type="square"> <li>A second stab on the job could take a patch number for odlparent or yangtools, build the patch and do similar than first. The goal in this case is to verify an upstream patch before it is actually merged. This job could run on-demand.</li> </ul> RELENG-69

Create autorelease job to verify non SR projects upstream changes

Story High Closed Done Anil Belur Luis Gomez Thu, 30 Nov 2017 17:52:05 +0000 Fri, 24 Aug 2018 03:06:16 +0000 Fri, 24 Aug 2018 03:06:16 +0000 Autorelease 0 4 <p>As discussed during integration call, we need this job but we can wait until we get new cloud infra.</p> <p>I start to think this kind of job will be much more stable and usable once we streamline the Core distribution (hopefully in Flourine).</p> <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=askb" class="user-hover" rel="askb">askb</a> The Oxygen release is fast approaching. I think we should try to get this task going if we want to have it available for the upcoming Flourine release.</p> <p>Here is a summary of points as discussed with <a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=ecelgp" class="user-hover" rel="ecelgp">ecelgp</a>:</p> <ul> <li>The job verifies that version bumping to the snapshot version for the list of dependent projects does not break the build. The job is required to change the SR project version to the snapshot version for each of the dependent project and then build the projects to ensure that version bumping the SR projects passes. <ul> <li>Clone all the projects similar to AR.</li> <li>Change the versions in pom files to point to the snapshots for the SR projects. We mostly require to change parent.groupId or dependencies to snapshot version.</li> <li>Build all the projects and verify they are passing </li> </ul> </li> <li>Initially start with minimum number of projects (like controller, mdsal) or with a small distribution patch as provided.</li> </ul> <ul> <li>Creating a single job for all SR project would be ideal such that it take a parameter (project=<version>, where <version> is the version number to build against). Refer <span class="error">[1.]</span> for example: genius=32/53632/9,netvirt:59/50259/47</li> </ul> <ul> <li>Note: if projects are using version numbers from properties then we need to fix them in the projects </li> </ul> <p><span class="error">[1.]</span> <a href="https://jenkins.opendaylight.org/releng/view/integration/job/integration-multipatch-test-oxygen/72/parameters" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/integration/job/integration-multipatch-test-oxygen/72/parameters</a></p> <p> </p> <p> </p> <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=ecelgp" class="user-hover" rel="ecelgp">ecelgp</a> Here is an initial version (WIP) of the job being tested on the sandbox</p> <p><a href="https://jenkins.opendaylight.org/sandbox/job/autorelease-verify-sr-projects-oxygen/9" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/sandbox/job/autorelease-verify-sr-projects-oxygen/9</a></p> <p>Here is the link to log server which is working</p> <p><a href="https://logs.opendaylight.org/sandbox/vex-yul-odl-jenkins-2/autorelease-verify-sr-projects-oxygen/11/" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/sandbox/vex-yul-odl-jenkins-2/autorelease-verify-sr-projects-oxygen/11/</a></p> <p>Tested with the change <span class="error">[x.]</span> which bumps yangtools to 2.0.3-SNAPSHOT</p> <p><span class="error">[x.]</span> <a href="https://git.opendaylight.org/gerrit/#/c/69366/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/69366/</a></p> <p><span class="error">[WIP]</span> Verify non SR projects changes upstream<br/> <a href="https://git.opendaylight.org/gerrit/69596" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/69596</a></p> <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=ecelgp" class="user-hover" rel="ecelgp">ecelgp</a> Please provide a odlparent version bump change for testing the job. </p> <p>I think for oxygen you can try any odlparent patch in 3.0.x branch (3.0.3-SNAPSHOT):</p> <p>For example: <a href="https://git.opendaylight.org/gerrit/#/c/69609/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/69609/</a></p> <p>For master (fluorine) you can try any odlparent patch in 3.1.x branch (3.1.0-SNAPSHOT) but I do not see any opened patch right now. Would it be possible to build the 3.1.x branch head instead?</p> <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=ecelgp" class="user-hover" rel="ecelgp">ecelgp</a> I tried with both the patches, but unfortunately the pom files are not standard between the SR projects which makes it difficult to read the SR SNAPSHOT VERSION. For ex odlparent has:</p> <p><a href="https://jenkins.opendaylight.org/sandbox/job/autorelease-verify-sr-projects-oxygen/14/consoleText" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/sandbox/job/autorelease-verify-sr-projects-oxygen/14/consoleText</a></p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> <parent> <groupId>org.opendaylight.odlparent</groupId> <artifactId>odlparent-lite</artifactId> <version>4.0.0-SNAPSHOT</version> <relativePath>odlparent-lite</relativePath> </parent> </pre> </div></div> <p>While yangtools has:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> <project xmlns=<span class="code-quote">"http:<span class="code-comment">//maven.apache.org/POM/4.0.0"</span> xmlns:xsi=<span class="code-quote">"http://www.w3.org/2001/XMLSchema-instance"</span> </span> xsi:schemaLocation=<span class="code-quote">"http:<span class="code-comment">//maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"</span>> </span> <parent> <groupId>org.opendaylight.odlparent</groupId> <artifactId>odlparent-lite</artifactId> <version>3.0.2</version> <relativePath/> </parent> <modelVersion>4.0.0</modelVersion> <groupId>org.opendaylight.yangtools</groupId> <artifactId>yangtools-aggregator</artifactId> <version>2.0.3-SNAPSHOT</version> <name>yangtools</name>  <packaging>pom</packaging> </pre> </div></div> <p>Retrigger the job along with handling diff pom file structures.</p> <p><a href="https://jenkins.opendaylight.org/sandbox/job/autorelease-verify-sr-projects-oxygen/14" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/sandbox/job/autorelease-verify-sr-projects-oxygen/14</a></p> <p>I guess if it is difficult to extract odlparent/yangtools version from a patch, we could pass those directly to the job as the most important thing (at least in the beginning) is to do the version bump and build of all projects that are in AR.</p> <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=ecelgp" class="user-hover" rel="ecelgp">ecelgp</a> No worries, I have made some improvement to the scripts to handle that part too.</p> <p>However, I am unable to figure some inconsistencies in the pom.xml in controller project <span class="error">[x.]</span> file which is causing parsing errors in <span class="error">[y.]</span>:</p> <p><span class="error">[x.]</span>https://github.com/opendaylight/controller/blob/master/opendaylight/archetypes/opendaylight-startup/src/main/resources/archetype-resources/artifacts/pom.xml</p> <p><a href="https://logs.opendaylight.org/sandbox/vex-yul-odl-jenkins-2/autorelease-verify-sr-projects-oxygen/16" class="external-link" target="_blank" rel="nofollow noopener">[y.]https://logs.opendaylight.org/sandbox/vex-yul-odl-jenkins-2/autorelease-verify-sr-projects-oxygen/16</a></p> <p>`controller/opendaylight/archetypes/opendaylight-startup/src/main/resources/archetype-resources/artifacts/pom.xml`</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> #set( $symbol_pound = <span class="code-quote">'#'</span> ) #set( $symbol_dollar = <span class="code-quote">'$'</span> ) #set( $symbol_escape = <span class="code-quote">'\'</span> ) <?xml version=<span class="code-quote">"1.0"</span> encoding=<span class="code-quote">"UTF-8"</span>?> <!-- Copyright © ${copyrightYear} ${copyright} and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies <span class="code-keyword">this</span> distribution, and is available at http:<span class="code-comment">//www.eclipse.org/legal/epl-v10.htm</span> </pre> </div></div> <p> </p> <p> </p> <p> </p> <p>So today in Kernel call Robert brought a totally different approach on how to do the verification of Release-Integrated project (odlparent, yangtools) changes before they get released and consumed by downstream: </p> <p>Instead of straight build an odlparent/yangtools patch and then bump all Managed projects to use this version, we could simply:</p> <p>1) download odlparent/yangtools patch.<br/> 2) downgrade odlparent/yangtools version to match desired stream (oxygen, fluorine, etc).<br/> 4) clone all Managed projects and build normally.</p> <p>This way we do not need to change version in all AR projects but just the ones we want to test (odlparent/yangtools).</p> <p>As discussed over the int-dist call, this is implemented in the multipatch job, therefore not required any longer. </p> Development Rank 0|i038n3: