We also have a Jenkins instance at the EF. I think going that is the only way to publish to staging and maven central since that is where the credentials are, so I guess we will need that for the release builds. Might as well set up the snapshot builds there as well?
Totally agree on the importance of CI jobs. The platform is of
secondary importance to me. I've recently helped out configuring
some of the CI jobs for Apache Maven to GitHub Actions and it was
rather easy to do. It may be convenient to have it all on one
platform, but that also makes us a bit more dependent on that one
platform. I don't think that's a problem - if needed we could
always move away.
Maarten
On 02/07/2020 07:34, Christian
Kaltepoth wrote:
Hi all,
I guess we should add CI builds for our GitHub repos really
soon to catch errors as early as possible.
I was wondering if we should stay we Travis or if we should
use GitHub Actions instead. AFAIK the latter one is better
integrated into GitHub and easy to set up.
Any thoughts? I could prepare the GitHub Actions setup if
we agree to use it.