Hi everybody
I'm experimenting to move some jobs from Travis to a Jenkins pipeline
running in the Apache infra.
The PR with the changes is here:
https://github.com/apache/netbeans/pull/2443 and this is the Jenkins job:
https://ci-builds.apache.org/job/Netbeans/job/netbeans-github/
The CloudBees
Hi, I created another PR to move the MacOS job from Travis to the GitHub
action: https://github.com/apache/netbeans/pull/2180
The current GitHub action environment for macOS builds has the JDK 1.8
installed by default in comparison with Travis CI that needs a work around
to install an older java ve
Hi,
I created a draft PR to start testing GitHub actions:
https://github.com/apache/netbeans/pull/2158
It runs build and test platform/core.network module in a Windows machine.
After 12.0 release I would like merge it in the main repo and check how
it's working with new PR and commits.
El dom.,
Hi,
I don't mind using a different service, but let me point out the build
currently consumes quite some resources (and is likely to consume more in
the future[1]). I believe ASF is contributing to Travis, so that there are
more concurrent builds available on Travis for us[2]. We should check that
A while ago, I migrated the CI service for my NetBeans plugin from Travis
CI to GitHub Actions. The setup for the new pipeline was quite easy.
I decided for it because:
- It felt natural to have everything in one place.
- No need to give permissions to an app outside.
- You can have several workflo
