<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:37:29 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[RELENG-92] new integration/distribution job that will build final release using managed release and unmanaged projects from staging repos</title>
                <link>https://jira.opendaylight.org/browse/RELENG-92</link>
                <project id="10164" key="RELENG">releng</project>
                    <description>&lt;p&gt;Thanh has idea about having projects create their own staging repos, link RelMang team to that as &quot;this is my release, please include it&quot;, we aggregate that into a release repo and release it. This set of URLs to staging repos will live in an Int/Dist POM. Int/Dist will build with these, the existing MR distro, produces the final distro.&#160;These resulting artifacts would go to Int/Dist&apos;s staging repo.&lt;/p&gt;

&lt;p&gt;Projects would get their artifacts into the staging repos they want to produce using maven-staging job. Not sure if all projects have this, need all of them to. This could replace the merge job.&lt;/p&gt;

&lt;p&gt;MR staging -&amp;gt; Int/Dist staging -&amp;gt; all unmanaged staging repos&lt;/p&gt;</description>
                <environment></environment>
        <key id="29751">RELENG-92</key>
            <summary>new integration/distribution job that will build final release using managed release and unmanaged projects from staging repos</summary>
                <type id="10100" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10310&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="3" iconUrl="https://jira.opendaylight.org/images/icons/priorities/major.svg">Medium</priority>
                        <status id="1" iconUrl="https://jira.opendaylight.org/images/icons/statuses/open.png" description="The issue is open and ready for the assignee to start work on it.">Open</status>
                    <statusCategory id="2" key="new" colorName="blue-gray"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="jluhrsen">Jamo Luhrsen</reporter>
                        <labels>
                    </labels>
                <created>Thu, 12 Apr 2018 02:57:22 +0000</created>
                <updated>Thu, 12 Apr 2018 23:35:10 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="62389" author="zxiiro" created="Thu, 12 Apr 2018 23:34:49 +0000"  >&lt;p&gt;This is the workflow I&apos;m currently thinking although it will likely change as we start deploying and writing the new jobs and hitting issues:&lt;/p&gt;


&lt;p&gt;Phase 1:&lt;/p&gt;

&lt;p&gt;1. autorelease produces the managed release (same as today, nothing is changed) and produces staged repo&lt;br/&gt;
2. New int/dist job takes managed release staging repo, and runs a release build against it depending on snapshot versions of unmanaged projects.&lt;/p&gt;

&lt;p&gt;Phase 2:&lt;/p&gt;

&lt;p&gt;1. autorelease produces the managed release (same as today, nothing is changed) and produces staged repo&lt;br/&gt;
2. unmanaged projects produce staged release repos similar to autorelease&lt;br/&gt;
3. New int/dist job has a pom.xml that pulls in all of the unmanaged project staged repos and builds against the combination of all staged repos, produces a new int/dist staged repo containing the final karaf distro&lt;/p&gt;

&lt;p&gt;Release time:&lt;/p&gt;

&lt;p&gt;1. each project will contribute to int/dist&apos;s pom.xml file containing the staged repos with their final staged repo URL&lt;br/&gt;
2. int/dist will produce the final build and staged repo&lt;br/&gt;
3. all of the staging repos including int/dist and projects will be released simultaneously upon TSC approval &lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10002" key="com.pyxis.greenhopper.jira:gh-epic-link">
                        <customfieldname>Epic Link</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>RELENG-93</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i03d8f:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>