Hello,
I tried to create a github actions config which is closer to a classic
CI pipeline.
base-build job (~22 mins):
- JDK 8 on linux
- full build of netbeans + commit-validation task but without zip
distribution
- archives the entire workspace and uploads it as artifact
secondary jobs:
- jdk 11/17 on various OSes etc
- only start if base-build succeeds
- extract the workspace
- run more tests with that workspace
- upload junit results (yey - main reason why i started this)
example run:
https://github.com/mbien/netbeans/actions/runs/1379449244
(note: you can download the entire workspace if you want which might be
useful for debugging purposes, currently retained for 1 day)
(note2: i disabled a lot of tests on the secondary jobs for now to not
waste resources)
(note3: someone has to fix the tests on JDK 17(!))
(note4: php tests don't generate test result xmls, thats why nothing is
uploaded)
My questions for those who are more familiar with the NB build:
Are there any tasks which can be run without having to build anything,
e.g license checks?
Is there anything else i should put on the secondary jobs beside
commit-validation (and the php cluster specific tests)? Reliable tests
which don't break like those on travis - which only leads to devs
completely ignoring them.
What do you think about this in general?
regards,
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
