CI pipeline improvements (more label control)

[mbien]

A few tweaks in anticipation to the policy changes:

https://infra.apache.org/github-actions-policy.html

restructuring:

• refactored the env vars into 'outputs' of the base-build job since env vars can't be used everywhere but outputs can
• more jobs are now opt-in and can be activated with labels
  (enterprise, db, javafx, profiler, versioning, web...)
• moved web related steps into the webcommon job to shrink ide job
• activate LSP tests also when 'Gradle' or 'Maven' label was set
• matrix got further reduced for runs outside of PRs
• combine some jobs into single build-system / misc job

other changes:

• fail CI if PR is not labeled
• fixed issue where paperwork job couldn't be cancelled
• bumped CV tests to JDK 22

full set of variables (or see labels with [ci] marker in their description):

netbeans/.github/workflows/main.yml

Lines 58 to 113 in 1a4519c

	# labels are mapped to env vars for pipeline customization. If this is not a PR, (almost) everything will run, but with a reduced matrix.
	# note: env vars don't work in the job's 'if' field but do work within jobs ( https://github.com/actions/runner/issues/1189 ), the whole expression must be duplicated
	# labels for special commands:
	# 'ci:all-tests' enables everything
	# 'ci:no-build' disables the build job (and test jobs too)
	# 'ci:dev-build' produces an artifact containing a runnable NetBeans zip distribution
	# 'Java' label
	test_java: ${{ contains(github.event.pull_request.labels.*.name, 'Java') || contains(github.event.pull_request.labels.*.name, 'ci:all-tests') || github.event_name != 'pull_request' }}
	# 'JavaFX' label
	test_javafx: ${{ contains(github.event.pull_request.labels.*.name, 'JavaFX') || contains(github.event.pull_request.labels.*.name, 'ci:all-tests') || github.event_name != 'pull_request' }}
	# 'JavaDoc' or 'API Change' labels
	test_javadoc: ${{ contains(github.event.pull_request.labels.*.name, 'JavaDoc') || contains(github.event.pull_request.labels.*.name, 'API Change') || contains(github.event.pull_request.labels.*.name, 'ci:all-tests') || github.event_name != 'pull_request' }}
	# 'JavaScript' label
	test_javascript: ${{ contains(github.event.pull_request.labels.*.name, 'JavaScript') || contains(github.event.pull_request.labels.*.name, 'ci:all-tests') || github.event_name != 'pull_request' }}
	# 'PHP' label
	test_php: ${{ contains(github.event.pull_request.labels.*.name, 'PHP') || contains(github.event.pull_request.labels.*.name, 'ci:all-tests') || github.event_name != 'pull_request' }}
	# 'Groovy' label
	test_groovy: ${{ contains(github.event.pull_request.labels.*.name, 'Groovy') || contains(github.event.pull_request.labels.*.name, 'ci:all-tests') || github.event_name != 'pull_request' }}
	# 'Rust' label
	test_rust: ${{ contains(github.event.pull_request.labels.*.name, 'Rust') || contains(github.event.pull_request.labels.*.name, 'ci:all-tests') || github.event_name != 'pull_request' }}
	# 'Platform' label
	test_platform: ${{ contains(github.event.pull_request.labels.*.name, 'Platform') || contains(github.event.pull_request.labels.*.name, 'ci:all-tests') || github.event_name != 'pull_request' }}
	# 'LSP' label for enabling Language Server Protocol tests
	# 'Gradle' or 'Maven' will activate lsp tests too due to test dependencies on project API (ProjectViewTest, LspBrokenReferencesImplTest, ...)
	test_lsp: ${{ contains(github.event.pull_request.labels.*.name, 'LSP') || contains(github.event.pull_request.labels.*.name, 'Gradle') || contains(github.event.pull_request.labels.*.name, 'Maven') || contains(github.event.pull_request.labels.*.name, 'ci:all-tests') || github.event_name != 'pull_request' }}
	# 'GraalVM' label for tests requirering GraalVM
	test_graalvm: ${{ contains(github.event.pull_request.labels.*.name, 'GraalVM') || contains(github.event.pull_request.labels.*.name, 'ci:all-tests') || github.event_name != 'pull_request' }}
	# 'VSCode Extension' label for building and testing the VSCode Extension
	test_vscode_extension: ${{ contains(github.event.pull_request.labels.*.name, 'VSCode Extension') || contains(github.event.pull_request.labels.*.name, 'ci:all-tests') || github.event_name != 'pull_request' }}
	# 'Ant', 'Gradle', 'Maven' and 'MX' labels trigger the build-tools job
	test_build_tools: ${{ contains(github.event.pull_request.labels.*.name, 'Ant') || contains(github.event.pull_request.labels.*.name, 'Gradle') || contains(github.event.pull_request.labels.*.name, 'Maven') || contains(github.event.pull_request.labels.*.name, 'MX') || contains(github.event.pull_request.labels.*.name, 'ci:all-tests') || github.event_name != 'pull_request' }}
	# 'git', 'subversion' and 'mercurial' labels trigger the versioning job
	test_versioning: ${{ contains(github.event.pull_request.labels.*.name, 'git') || contains(github.event.pull_request.labels.*.name, 'subversion') || contains(github.event.pull_request.labels.*.name, 'mercurial') || contains(github.event.pull_request.labels.*.name, 'ci:all-tests') || github.event_name != 'pull_request' }}
	# 'Java EE/Jakarta EE', 'Micronaut' and 'enterprise' labels trigger the enterprise job
	test_enterprise: ${{ contains(github.event.pull_request.labels.*.name, 'Java EE/Jakarta EE') || contains(github.event.pull_request.labels.*.name, 'Micronaut') || contains(github.event.pull_request.labels.*.name, 'enterprise') || contains(github.event.pull_request.labels.*.name, 'ci:all-tests') || github.event_name != 'pull_request' }}
	# 'JavaScript', 'TypeScript', 'HTML', 'CSS', 'CSL' and 'web' labels the trigger web job
	test_web: ${{ contains(github.event.pull_request.labels.*.name, 'JavaScript') || contains(github.event.pull_request.labels.*.name, 'TypeScript') || contains(github.event.pull_request.labels.*.name, 'HTML') || contains(github.event.pull_request.labels.*.name, 'CSS') || contains(github.event.pull_request.labels.*.name, 'CSL') || contains(github.event.pull_request.labels.*.name, 'web') || contains(github.event.pull_request.labels.*.name, 'ci:all-tests') || github.event_name != 'pull_request' }}
	# 'tests' label activates an extra step which builds all tests
	test_tests: ${{ contains(github.event.pull_request.labels.*.name, 'tests') || contains(github.event.pull_request.labels.*.name, 'ci:all-tests') || github.event_name != 'pull_request' }}

[mbien]

@sdedic since I believe you asked me about this before: this would change the enterprise job to be also opt-in. It listens to enterprise [ci] enable enterprise job , Java EE/Jakarta EE [ci] enable enterprise job and Micronaut [ci] enable enterprise job after this change. Any other labels to add?

analog to the build-tools, web and versioning jobs

[mbien]

this will fail when PRs are not labeled.

CI did always run some tests outside of the declared categories. The reasoning behind that was because I was worried about unlabeled PRs. Since this PR reduces the amount of testing outside of the declared labels, it will be enforced from now on (was discussed on apache slack with @neilcsmith-net ).

It should be easy to find labels even for trivial PRs, since we have enough labels which are generic and don't do anything. E.g Editor , CI continuous integration changes or Code cleanup . For readme edits we have ci:no-build [ci] disable CI pipeline

The IDE cluster job is always enabled, one day we should make it also configurable but lets do this incrementally.

[mbien]

lsp job is now also active with Gradle [ci] enable "build tools" tests or Maven [ci] enable "build tools" tests due to test dependencies on project API.

This was added to avoid issues like #7267 in future. Anything else to change?

@lkishalmi @sdedic @neilcsmith-net

[mbien]

ran it once with all-all tests and it looks fine, CV on JDK 22 fails since it requires #7268

[mbien]

for future reference: this trick allows us to reduce the test matrix using labels or other properties