Created an initial blank commit to describe my plan to add support for this feature. https://git.opendaylight.org/gerrit/19644
Heavy modifications will be needed in jjb-init-project and jjb-autoupdate-project script to support this more complex configuration format.
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.
Maybe the configuration file should be switched from a basic key value setup to a yaml?
That way we won't have to deal with reformatting different parts of it later, just handling the keys in different ways.
(In reply to Andrew Grimberg from comment #2)
> Maybe the configuration file should be switched from a basic key value setup
> to a yaml?
>
> That way we won't have to deal with reformatting different parts of it
> later, just handling the keys in different ways.
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)".
(In reply to Thanh Ha from comment #3)
> (In reply to Andrew Grimberg from comment #2)
> > Maybe the configuration file should be switched from a basic key value setup
> > to a yaml?
> >
> > That way we won't have to deal with reformatting different parts of it
> > later, just handling the keys in different ways.
>
> 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)".
Ah silly me. That's what I get for not actually looking at how we load that file 
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.