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/CONTROLLER-665 controller <p>Note: This is the wrong place for this bug, but we don't have anywhere better right now. Further note this is a placeholder bug to give us something to talk about.</p> <p>We know that we need a number of improvements to autorelease, including:</p> <p>1) Find a way to get a consistent suffix to replace SNAPSHOT for ODL artifacts in he weeklies so folks can easily consume them. Possible example:</p> <p>foo-x.y.z-SNAPSHOT becomes foo-x.y.z--HELIUM.PRE-vYYYYMMDDMMSS<br/> where the vYYYYMMDDMMSS is the same across all artifacts built by the autorelease.</p> <p>2) Have the autorelease job dump a simple text file with the tags of the commits its built against as an artifact to the job in a format something like:</p> <p>&lt;gitrepo&gt; &lt;commitid&gt; &lt;buildtag&gt;</p> <p>Example</p> <p>controller 2a7de8c0a2804a981a739ed85a96f190306f47a8 HELIUM.PRE-vYYYYMMDDMMSS<br/> sfc 2a7de8c0a2804a981a739ed85a96f190306f47a8 HELIUM.PRE-vYYYYMMDDMMSS</p> <p>So that the projects can build very very simple Jenkins jobs to pull tags.</p> <p>Please don't take the suggestions here as prescriptive, just examples... and more are welcome.</p> <p>3) Add all of the Helium Projects to autorelease.</p> <p>Operating System: Mac OS<br/> Platform: PC</p> CONTROLLER-665

Milestone: autorelease improvements

Improvement Resolved Won't Do Unassigned Ed Warnicke Wed, 6 Aug 2014 19:36:55 +0000 Thu, 19 Oct 2017 21:29:13 +0000 Tue, 5 May 2015 07:19:33 +0000 Helium adsal 0 4 <p>I'm going to post two comments. This is the first and I think should be done with or very soon after the 3 things Ed says above.</p> <p>4.) Provide a script (or other easy to use instructions) that will allow a project to convert all dependencies outside of the project to the latest weekly release.</p> <p>(In reply to Colin Dixon from comment #1)<br/> &gt; I'm going to post two comments. This is the first and I think should be done<br/> &gt; with or very soon after the 3 things Ed says above.<br/> &gt; <br/> &gt; 4.) Provide a script (or other easy to use instructions) that will allow a<br/> &gt; project to convert all dependencies outside of the project to the latest<br/> &gt; weekly release.</p> <p>I should note that this clearly is lower priority than getting the auto-release to work for Helium with all projects such that we can have a fighting chance at releasing Helium on time with minimal pain.</p> <p>This is my second post. These features are things that I think it would be incredibly handy to have and rely on getting the autorelease working and building weekly releases, but are still related.</p> <p>I think we should have a central place which tracks the current versions for all projects. It seems to me like the odlparent project's pom file would be an ideal place.</p> <p>In this pom file we would have properties defined for every project like:<br/> &lt;project&gt;.snapshot.version<br/> &lt;project&gt;.weekly.version</p> <p>The weekly version would be updated by the weekly run of the auotrelease, presumably by Jenkins pushing a patch back to odlparent. The snapshot would be set by the project itself when they mean to update the version they're exporting to the rest of the world.</p> <p>We could even add versions like:<br/> &lt;project&gt;.snapshot.stable.version<br/> &lt;project&gt;.weekly.stable.version</p> <p>which would be pushed by integration jenkins jobs that make sure the whole of ODL builds and passes system tests with that version.</p> <p>Once you've done this, it makes it pretty easy for projects to pick what version(s) they want to use because they can do so with semantically meaningful strings rather than versions. If done right most projects could just put one like in their pom files that said something like:<br/> &lt;desiredVersion&gt;weekly.stable&lt;/desiredVersion&gt;</p> <p>And then have that be picked up as the default version for every bundle they pull in.</p> <p>As a side note, if you do this, the odlparent project's commits would become something of a universal version number for the whole of OpenDaylight and you would be able to go back and forward in time by just changing how you build the one bundle.</p> <p>This bug is part of the project to Move all ADSAL associated component bugs to ADSAL</p> <p>The releng/autorelease project is taking care of this.</p> Development External issue ID 1494 External issue URL Rank 0|i02lsv: