I still have the original problem: e.g. I can't run the Travis jobs for my PR and without all of them passing, I am hesitating to integrate my change: https://github.com/apache/netbeans/pull/2707 - how do you guys do it, that your Travis checks run?
Anyway few thoughts, with respect to switching to GitHub actions: - 1st and foremost, ASF has to have a contract with provider of the CI solution! Unless I am mistaken ASF pays to Travis and as such we can run such a huge NetBeans loads on Travis. ASF needs to do the same with GitHub before we can fully use Actions. > I thing we need to define which checks must be run for every PR and > which are needed on daily basis. - preferrably all of them, before the PR is merged. However, we don't have to run them with every commit automatically. Simple `ant build` would be enough for an automatic "ready to go" check. Lars wrote: > Manually triggered workflows for now. The person who wishes to merge > can then trigger the workflow on a need basis. (obviously not a good > long term solution) +1 yes, the person that is about to merge shall trigger the full check. Or it could run automatically at the end of a day (24h after last change to a PR), so it is ready to merge by others the next day. > Some jobs seems that they can be merged together - "Test java.hints > batch 1 with nb-javac on Java 13" and "Test java.hints batch 2 with > nb-javac on Java 13" use same setup. By merging them together we can > save one build step. - using pipelines. E.g. we shall built NetBeans IDE just once and then distribute the ZIP accross other jobs to do the testing. It is a huge change (as such not many projects do that), but it would save 10min of CPU for each job. The general problem is how to distribute the bits between the running nodes - each CI has its own solution (as far as I know the Travis solution is nasty/ugly/primitive). `Jenkinsfile` seems to do it relatively well. - btw. shall not we reuse the ASF's own build infrastructure (e.g. `Jenkinsfile`) to run our pipeline tests? In general whoever donates a CPU is a friend, right? > I added Windows build to test PHP modules because of some issues in > handling different path separator. It can be run on schedule just to > verify it still works. versus Lars's: > never ever use Windows or MacOS unless you _absolutely_ need to. - we certainly need to test on Windows and Mac. At least filesystem behavior is different on those OSes. With (Jenkins) pipelines we could build once (on Docker Linux) and then just reuse the bits and lower the load on other systems. Just my 2Kč. But my main problem remains: Shouldn't we get our existing Travis jobs running first? -jt --------------------------------------------------------------------- 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
