Skip to content

Conversation

@gnodet
Copy link
Contributor

@gnodet gnodet commented Dec 4, 2025

Add a new workflow to validate commits pushed to main and LTS branches:

  • Runs full build and tests on push to main, camel-4.4.x, camel-4.8.x, camel-4.10.x, and camel-4.14.x branches
  • Tests with both Java 17 and Java 21
  • Includes build artifact archival for debugging

Add concurrency control to PR workflows to prevent resource waste:

  • pr-build-main.yml: Cancel in-progress runs when PR is updated
  • pr-comment.yml: Cancel in-progress runs for same issue
  • pr-doc-validation.yml: Cancel in-progress runs when PR is updated
  • depsreview.yaml: Cancel in-progress runs when PR is updated

This ensures the main branch is always validated after merges and reduces CI queue times by cancelling obsolete workflow runs.

Add a new workflow to validate commits pushed to main and LTS branches:
- Runs full build and tests on push to main, camel-4.4.x, camel-4.8.x,
  camel-4.10.x, and camel-4.14.x branches
- Tests with both Java 17 and Java 21
- Includes build artifact archival for debugging

Add concurrency control to PR workflows to prevent resource waste:
- pr-build-main.yml: Cancel in-progress runs when PR is updated
- pr-comment.yml: Cancel in-progress runs for same issue
- pr-doc-validation.yml: Cancel in-progress runs when PR is updated
- depsreview.yaml: Cancel in-progress runs when PR is updated

This ensures the main branch is always validated after merges and
reduces CI queue times by cancelling obsolete workflow runs.
Copy link
Contributor

@squakez squakez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some minor points you may want to consider.

push:
branches:
- main
- camel-4.4.x
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd keep only last 2 LTS instead. Altough this is not really affecting as we don't merge anything to older branches, it could be perceived as an argument for users which expects longer timeline maintenance for those older branches.

runs-on: ubuntu-latest
strategy:
matrix:
java: ['17', '21']
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For the merge I'd reduce the quantity of resources by only checking against the latest JVM supported instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants