https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/DOCS-113 docs <p>Now that project-specific docs have moved out of the docs project and to individual projects, each project has a docs/conf.yaml with a version name that needs to match the branch (Neon for master at the moment, Fluorine for stable/fluorine, etc). It's not great to have to manually do this for all the projects. Maybe we can pull it from a central place, or at least add some scripting/automation. Should also doc/handle this is in the normal branch cutting process.</p> DOCS-113

Find way to avoid need for docs/conf.yaml version maintenance per-project

Improvement Medium Closed Won't Do Thanh Ha (zxiiro) Daniel Farrell Thu, 11 Oct 2018 15:50:33 +0000 Tue, 13 Apr 2021 15:29:51 +0000 Tue, 13 Apr 2021 15:27:06 +0000 Aluminium 0 2 <p>Using `git describe` does not work for us because our tags are not reachable from the master branch due to them being on forked branches. Unfortunately this prevents us from using the same solution as LF uses in global-jjb to handle automated versioning.</p> <p>For ODL we can parse pom.xml instead with the following code:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>import xml.etree.ElementTree as ET version = ET.parse('pom.xml').getroot().find('*//{http://maven.apache.org/POM/4.0.0}version').text release = version </pre> </div></div> <p>At least for MRI projects we can use this method.</p> Relates MDSAL-489 Development Rank 0|i03jjr: