I was curious if someone can expand a little on our CI build and test strategy
I believe there is Github Action (for build and unit tests from the source in some context), Travis CI (using tests from the travis file on travis ci servers) in some context, and Jenkin CI on Apache site in other contexts. I believe some of these are constrained by the amount of "resources" available for given test/build environments (i.e. Github limits, Travis CI limits, apache limits, etc.) I know this is not a simple task but, is the plan to continue mixing build and test environments or at some point will all of this get migrated towards one environment. I believe some aspect of this was discussed previously (1), so I'm wondering if it's worth bringing it back up again. Eric Bresie ebre...@gmail.com (1) Using test distribution & Apache's Jenkins pipelines was: Time it takes for Test PHP Cluster (mail-archive.com) <https://www.mail-archive.com/dev@netbeans.apache.org/msg08296.html>
