<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:15:30 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>[COE-54] COE Gerrits should include a build job that verifies the Go code</title>
                <link>https://jira.opendaylight.org/browse/COE-54</link>
                <project id="10112" key="COE">coe</project>
                    <description>&lt;p&gt;While working on &lt;a href=&quot;https://jira.opendaylight.org/browse/COE-30&quot; title=&quot;Make CNI container image available on the Quay.io container registry&quot; class=&quot;issue-link&quot; data-issue-key=&quot;COE-30&quot;&gt;&lt;del&gt;COE-30&lt;/del&gt;&lt;/a&gt;, it occurred to me that it&apos;s a great basis for adding non-regression to the Go build to all of our Gerrits... AFAIK for the moment the COE verify jobs only build the Java part. &lt;/p&gt;

&lt;p&gt;Based on &lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/79589/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/79589/&lt;/a&gt; (and it&apos;s parent pre-requisites) it may not be hard now to add a new job (via JJB ?) which just does &lt;tt&gt;make&lt;/tt&gt; (or even directly &lt;tt&gt;docker build -t  odlovs-cni .&lt;/tt&gt;) in &lt;tt&gt;coe/odlCNIPlugin/odlovs-cni&lt;/tt&gt; (and after &lt;a href=&quot;https://jira.opendaylight.org/browse/COE-32&quot; title=&quot;Watcher container image, build and push to repository&quot; class=&quot;issue-link&quot; data-issue-key=&quot;COE-32&quot;&gt;COE-32&lt;/a&gt; ditto for the watcher) ... &lt;/p&gt;

&lt;p&gt;All we need is a Build VM which has Docker (or &lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/79589/2/odlCNIPlugin/odlovs-cni/Readme.md&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;even better because much safer and more secure not Docker nor podman or podman-docker but just buildah&lt;/a&gt;).&lt;/p&gt;

&lt;p&gt;NB: The build node VM does NOT, should not, need to have go and dep installed - that&apos;s (now, &lt;a href=&quot;https://jira.opendaylight.org/browse/COE-30&quot; title=&quot;Make CNI container image available on the Quay.io container registry&quot; class=&quot;issue-link&quot; data-issue-key=&quot;COE-30&quot;&gt;&lt;del&gt;COE-30&lt;/del&gt;&lt;/a&gt;) all self contained in the multi stage container build!&lt;/p&gt;

&lt;p&gt;This issue is NOT the same as &lt;a href=&quot;https://jira.opendaylight.org/browse/COE-30&quot; title=&quot;Make CNI container image available on the Quay.io container registry&quot; class=&quot;issue-link&quot; data-issue-key=&quot;COE-30&quot;&gt;&lt;del&gt;COE-30&lt;/del&gt;&lt;/a&gt;, the point here is not the make container images available in a remote container registry (&lt;a href=&quot;https://jira.opendaylight.org/browse/COE-30&quot; title=&quot;Make CNI container image available on the Quay.io container registry&quot; class=&quot;issue-link&quot; data-issue-key=&quot;COE-30&quot;&gt;&lt;del&gt;COE-30&lt;/del&gt;&lt;/a&gt; will do that), but just the build on Gerrit changes.&lt;/p&gt;

&lt;p&gt;I&apos;m unlikely to have the spare cycles to work on this myself, but can answer Qs anyone who would like to take this on may have on how we could best go about this.&lt;/p&gt;</description>
                <environment></environment>
        <key id="31322">COE-54</key>
            <summary>COE Gerrits should include a build job that verifies the Go code</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="prem.sankar.g@ericsson.com">Prem Sankar</assignee>
                                    <reporter username="vorburger">Michael Vorburger</reporter>
                        <labels>
                    </labels>
                <created>Wed, 16 Jan 2019 23:37:59 +0000</created>
                <updated>Sat, 19 Jan 2019 01:03:43 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>0</watches>
                                                                                                                <comments>
                            <comment id="66250" author="vorburger" created="Sat, 19 Jan 2019 01:03:43 +0000"  >&lt;p&gt;It occurred to me that CSIT jobs today probably already build the Go code (and with &lt;a href=&quot;https://jira.opendaylight.org/browse/COE-55&quot; title=&quot;CSIT should use (locally built, not remote fetched) containerized CNI (and later Watcher and ODL)&quot; class=&quot;issue-link&quot; data-issue-key=&quot;COE-55&quot;&gt;COE-55&lt;/a&gt; certainly will), so the point of having such a new job, or even adding this to the existing verify job, would just be to catch anything broken in the Go code (and the container builder) faster - which would be cool &amp;amp; useful IMHO (but it&apos;s not super critical).&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="30965">COE-10</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <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_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i03m67:</customfieldvalue>

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