Hello Devs,
We just merged #4431 which means we migrated 16 more travis jobs to
github actions and made some of the jobs conditional based on PR labels.
most important point first:
Please try to label your PRs before pressing the create button so that
CI can run the right tests for the PR (but it seems like everyone is
doing this already, which is awesome).
But don't worry! NetBeans will be always fully build and there is always
a basic set of tests enabled. The labels only add additional (time
consuming) jobs or steps in their respective category.
more details:
The following labels control CI behavior:
- 'Java', 'JavaScript', 'PHP' and 'Platform' unlock some long running
steps/jobs in their respective category
- 'Ant', 'Gradle', 'Maven' and 'MX' trigger the new "Build Tools" job
which runs all tests which fall in the build tools category
- 'JavaDoc' and 'API Change' runs javadoc steps, since building the
doc can be time consuming
- 'ci:no-build' builds nothing, tests nothing (e.g if you edit a readme)
- 'ci:all-tests' for running all tests (about ~8h total CI time atm)
- https://github.com/apache/netbeans/labels?q=[ci] lists all labels
which influence CI
- if you label a PR you can use "[ci]" to narrow down the search (even
something like "Java ci" works), this will list the relevant labels too
All tests will run if the workflow was not started by a PR sync, e.g. a
PR merge to master will run all tests.
We can adjust this based on feedback (don't reply to this email directly
though).
If you add more PR labels during development, simply sync the PR to
start a fresh run with the new configuration. Restarting the workflow or
individual jobs directly will _not_ take new labels into account since
github takes a snapshot of the PR state when the workflow starts.
tips for reviewers:
- check if the PR was correctly labeled / if the right tests ran
before integrating a PR. In case of doubt, add ci:all-tests
- PR syncs will start a fresh workflow run with updated labels taken
into account, many if not most PRs need changes anyway
- if you don't want to ask the PR owner to sync the PR again (e.g if
there is no need for changes), simply press "lock conversation" and
unlock it again. A new workflow will magically start triggered by the
"unlock" event.
(don't laugh, there are reasons why its the "unlock" event and not
something else, but lets keep this mail concise ;))
- the new "Check Paperwork" job prints some additional info about the
commits, useful for quick commit header validation when reviewing first
time contributions
PR has some screenshots and more info:
https://github.com/apache/netbeans/pull/4431
for questions or feedback start a new thread, don't reply to [NOTICE]
mails directly please,
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
