Hi devs,

at first we weren't sure if we should migrate all travis jobs to github, then we weren't sure if we actually can without using up all of apache's resources. Well, those fears/concerns don't matter anymore since we have to finish migration till the end of this year when travis support for apache projects ends:

https://cwiki.apache.org/confluence/display/INFRA/Travis+Migrations


This PR migrates almost all of the remaining jobs to gh actions:

https://github.com/apache/netbeans/pull/4817

feedback appreciated. Esp if you want to run certain jobs on certain labels. New label additions are: 'Groovy', 'GraalVM', 'VSCode Extension' and 'tests'. Other newly migrated jobs either run always since they don't take much time or were mapped to previously used labels.


One job is missing. It turned out that the LSP job is the final boss of this endeavor. I tried to replicate the travis environment, bumped timeouts, incrementally commented out tests, diffed logs between local runs and gh runs, but the job managed to generate new exceptions to keep things interesting. Migrating unreliable tests is extra painful since you never know if that exception you are looking at is of kind: regular, regular-new, sporadic or sporadic-new :)

So I have given up on that one for now until I regain more willpower for this task.

A test setup is here if anyone is interested to take a look (feel free to push into the PR if you want, its not meant for merging):

https://github.com/apache/netbeans/pull/4921


best regards,

michael


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists



Reply via email to