On 07.10.21 15:34, Neil C Smith wrote:
On Thu, 7 Oct 2021 at 10:56, Eric Barboni <[email protected]> wrote:
I would prefer to go to Apache Jenkins,

The aim here is not  for PR validation it's more a "nightly" verification ?
...
My "release manager" POV on why jenkins for that particular aspect.

(I'm not against travis (I prefer it greeeen :D)  or github action. GA may have 
some limitation, AFAIK Airflow own private repo on github to make their 
workflow.)
Yes, think we'd all prefer those be greeeen! :-)

I think we have to be careful with our CI usage, on whatever platform.
And it might be time to consider dropping Travis - interesting stuff
from Airflow around all this, eg. at
https://cwiki.apache.org/confluence/display/INFRA/Github+Actions+to+DockerHub

GitHub Actions also gives us the widest OS coverage?

My thought would be -

* Migrate important and stable tests to GitHub Actions for PR validation.
* Drop Travis CI.
* Switch on option for tests to pass before PR merge is enabled.
* Look at a nightly verification step on Jenkins for wider testing,
making sure we have good reporting from it.
* Be more proactive about reverting problem PRs (eg. revert, fix,
re-review rather than fix in place in most cases).

github actions make it also easy to selectively trigger certain test jobs. E.g it could trigger via PR labels, slash commands or parameters entered in the PR text. There is no need for nodes testing the php cluster for almost 2x 2h when something in the java editor changes.

i feel like every time i push to a PR someone has to cut down a tree somewhere and feed it to the testing cluster :)

whatever the new setup will be, a basic requirement for the usefulness of a CI server is to be able to actually display what failed. Having to go through a few meters of logs (in a browser) should not be acceptable for a CI server - it wastes simply too much time over the long term (and is no fun). I have a PR somewhere with a test failing on travis and there is no stack trace in the log of that failed test - its certainly somewhere in a xml but the current travis setup does not display those.

-michael

---------------------------------------------------------------------
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



Reply via email to