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/RELENG-12 releng <p>We need a way to enable JDK8 on projects that have branches that can't do JDK8. Otherwise we end up with projects disabling the auto job management for any branch that they want to do JDK8 on.</p> <p>For instance: <a href="https://git.opendaylight.org/gerrit/#/c/19329/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/19329/</a></p> <p>Operating System: All<br/> Platform: All</p> RELENG-12

Allow JDK8 to be enabled on select branches in auto-jjb scripts

Bug Resolved Done Unassigned Andrew Grimberg Tue, 5 May 2015 13:56:06 +0000 Thu, 19 Oct 2017 21:29:02 +0000 Thu, 7 May 2015 19:44:27 +0000 unspecified Jenkins Job Builder 0 3 <p>Created an initial blank commit to describe my plan to add support for this feature. <a href="https://git.opendaylight.org/gerrit/19644" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/19644</a></p> <p>Heavy modifications will be needed in jjb-init-project and jjb-autoupdate-project script to support this more complex configuration format.</p> <p>We'll need to refactor the parsing of the CFG file into jjb-init-project so that it is capable of reading the new configuration for BRANCHES. Due to this configuration being more complex we'll also lose support for setting the "-b" branches argument in init-project, or keep it simple but document that it is not possible to set the JDK this way.</p> <p>Maybe the configuration file should be switched from a basic key value setup to a yaml?</p> <p>That way we won't have to deal with reformatting different parts of it later, just handling the keys in different ways.</p> <p>(In reply to Andrew Grimberg from comment #2)<br/> &gt; Maybe the configuration file should be switched from a basic key value setup<br/> &gt; to a yaml?<br/> &gt; <br/> &gt; That way we won't have to deal with reformatting different parts of it<br/> &gt; later, just handling the keys in different ways.</p> <p>It's actually already YAML format. We just happened to use it as a basic key-value store but the code that reads this file is actually a call to "yaml.load(stream)".</p> <p>(In reply to Thanh Ha from comment #3)<br/> &gt; (In reply to Andrew Grimberg from comment #2)<br/> &gt; &gt; Maybe the configuration file should be switched from a basic key value setup<br/> &gt; &gt; to a yaml?<br/> &gt; &gt; <br/> &gt; &gt; That way we won't have to deal with reformatting different parts of it<br/> &gt; &gt; later, just handling the keys in different ways.<br/> &gt; <br/> &gt; It's actually already YAML format. We just happened to use it as a basic<br/> &gt; key-value store but the code that reads this file is actually a call to<br/> &gt; "yaml.load(stream)".</p> <p>Ah silly me. That's what I get for not actually looking at how we load that file <img class="emoticon" src="https://jira.opendaylight.org/images/icons/emoticons/wink.png" height="16" width="16" align="absmiddle" alt="" border="0"/> Though I think I remember talking about it when you set the extension to .cfg instead of .yaml since a .yaml would have caused jjb to pick up the file during processing.</p> Development External issue ID 3122 External issue URL Issue Type Rank 0|i01m07: