Hi NiFi devs, GitHub recently added a beta of their redesigned CI/CD feature, Actions [1]. It looks like the Apache GitHub organization has this bata feature, which is opt-in, enabled at the org level, and that we have the option to enable it for our NiFi repositories, e.g. [2][3].
Actions, like Travis CI, is free to use for public GitHub repositories. Given that our project's difficulty in getting Travis CI to run reliably for builds, I am wondering if it would be advantageous to evaluate Actions as an alternative. From what I can tell, it should be possible to have both enabled, allowing us to do a trial of Actions while continuing to use Travis CI. Ultimately, I think our CI builds will benefit from breaking up the nifi repository into multiple repositories, as previously discussed [4][5]. In the meantime / in addition to taking this step, I think it would be worthwhile to evaluate alternatives to Travis CI, which many have experienced difficulty using. - Has anyone had a chance to use the new beta of Actions on a project other than NiFi, and if so what has your experience been? - Are there any free to use Travis CI alternatives other than Actions we should also be considering? - Are there any objections to enabling Actions on our Apache NiFi GitHub repositories, and setting up CI builds for PRs and commits on master, similar to how we are using Travis now? [1] https://help.github.com/en/articles/about-github-actions [2] https://github.com/apache/nifi/actions [3] https://github.com/apache/nifi-registry/actions [4] https://lists.apache.org/thread.html/939a7630a2e32594cd10444e48b7a1321fd9ce51834d911a8c04b6a9@%3Cdev.nifi.apache.org%3E [5] https://cwiki.apache.org/confluence/display/NIFI/NiFi+Project+and+Repository+Restructuring Thanks, Kevin
