On 26.02.23 20:44, Neil C Smith wrote:
On Sun, 26 Feb 2023, 19:35 Michael Bien, <[email protected]> wrote:
we have to make up our mind how to handle testing :)
...
a) the "rust" branch approach
we switch everything in main.yml to the rust cluster in that branch ...
My suggestion above was to add rust into the release cluster in the rust
branch, then open a long-lived PR from rust branch to master. That PR
should automatically test correctly with every commit into the rust branch?
No change to main.yml required.
i liked that idea too.
btw, Matthias' proposal to use the full config is exactly the same as my
proposal since full would be release + rust which is what I mean :)
the full property is just built differently and has different cluster
ordering.
release:
nb.cluster.cpplite,\
nb.cluster.groovy,\
nb.cluster.php,\
${clusters.config.java.list},\
nb.cluster.apisupport,\
nb.cluster.webcommon,\
nb.cluster.enterprise
nb.cluster.ergonomics
full:
${clusters.config.java.list},\
nb.cluster.apisupport,\
nb.cluster.webcommon,\
nb.cluster.php,\
nb.cluster.groovy,\
nb.cluster.enterprise,\
nb.cluster.cpplite,\
nb.cluster.ergonomics
-mbien
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
