forked from apache/incubator-kie-drools
-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sync main branch with Apache main branch #80
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Migrating to JUnit5. Using good use of parametrized tests * Reverted changes in pom
apache#6080) * [incubator-kie-issues#1474] Fix NPE when loading multiple Signavio MID * [incubator-kie-issues#1474] Add debugging logs for skipping MID callback * [incubator-kie-issues#1474] Use Assertj fluent interface
* matches and replace using saxon * saxon usage simplified and modified tests * clean up code as per standards * changes as per suggestions * changes as per suggestions and restored the earlier tests * changes as per suggestions and restored the earlier tests * changes as per suggestions * exceptions handled and changes to util class * wip * wip * wip * wip * wip * CR * CR * CR * CR * Notice updated * CR --------- Co-authored-by: bncriju <[email protected]>
Bumps [com.google.protobuf:protobuf-java](https://github.com/protocolbuffers/protobuf) from 3.25.0 to 3.25.5. - [Release notes](https://github.com/protocolbuffers/protobuf/releases) - [Changelog](https://github.com/protocolbuffers/protobuf/blob/main/protobuf_release.bzl) - [Commits](protocolbuffers/protobuf@v3.25.0...v3.25.5) --- updated-dependencies: - dependency-name: com.google.protobuf:protobuf-java dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…ontests.TimerAndCalendarFireUntilHaltTest (apache#6096)
* Cache compiled dtables during the building of a KieProject * wip * wip
apache#6102) * [incubator-kie-drools-6098] apache-rat-plugin license check for drools (apache#6099) * Add missing license headers
* [DROOLS-7635] ansible-rulebook : Raise an error when a condition compares incompatible types * - Add beta index support - Add unit test * changed method names
…OGITO_GENERATE_DI properties (apache#6107) Co-authored-by: Gabriele-Cardosi <[email protected]>
…ble modules based on only.reproducible flag (apache#6108) * [incubator-kie-issues#1504] Conditionally build all or only reproducible modules based on only.reproducible flag * [incubator-kie-issues#1504] Conditionally build all or only reproducible modules based on only.reproducible flag - only for release build --------- Co-authored-by: Gabriele-Cardosi <[email protected]> # Conflicts: # .ci/jenkins/Jenkinsfile.deploy
…yInjectionAnnotator (apache#6090) * [incubator-kie-issues#1473] Add withTransactional method to DependencyInjectionAnnotator * [incubator-kie-issues#1473] Refactoring DependencyInjectionAnnotator. Add "Patch" annotation to RestAnnotators * [incubator-kie-issues#1473] Restore formatting --------- Co-authored-by: Gabriele-Cardosi <[email protected]>
This was referenced Oct 3, 2024
rgdoliveira
added
the
hacktoberfest-accepted
Included in https://hacktoberfest.digitalocean.com/hacktoberfest-update event
label
Oct 3, 2024
rgdoliveira
removed
the
hacktoberfest-accepted
Included in https://hacktoberfest.digitalocean.com/hacktoberfest-update event
label
Oct 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related PRs:
Thank you for submitting this pull request
NOTE!:
kiegroup/drools
is maintained only for old branches e.g.7.x
,7.67.x
,7.67.x-blue
.If you are submitting a PR for
main
branch, please useapache/incubator-kie-drools
instead.Ports If a forward-port or a backport is needed, paste the forward port PR here
link
JIRA: (please edit the JIRA link if it exists)
link
referenced Pull Requests: (please edit the URLs of referenced pullrequests if they exist)
How to replicate CI configuration locally?
Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.
build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.
How to retest this PR or trigger a specific build:
for pull request checks
Please add comment: Jenkins retest this
for a specific pull request check
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] tests
for a full downstream build
run_fdb
a compile downstream build please add comment: Jenkins run cdb
a full production downstream build please add comment: Jenkins execute product fdb
an upstream build please add comment: Jenkins run upstream
for quarkus branch checks
Run checks against Quarkus current used branch
Please add comment: Jenkins run quarkus-branch
for a quarkus branch specific check
Run checks against Quarkus current used branch
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] quarkus-branch
for quarkus main checks
Run checks against Quarkus main branch
Please add comment: Jenkins run quarkus-main
for a specific quarkus main check
Run checks against Quarkus main branch
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] quarkus-main
for quarkus lts checks
Run checks against Quarkus lts branch
Please add comment: Jenkins run quarkus-lts
for a specific quarkus lts check
Run checks against Quarkus lts branch
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] quarkus-lts
for native checks
Run native checks
Please add comment: Jenkins run native
for a specific native check
Run native checks
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] native
for native lts checks
Run native checks against quarkus lts branch
Please add comment: Jenkins run native-lts
for a specific native lts check
Run native checks against quarkus lts branch
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] native-lts
How to backport a pull request to a different branch?
In order to automatically create a backporting pull request please add one or more labels having the following format
backport-<branch-name>
, where<branch-name>
is the name of the branch where the pull request must be backported to (e.g.,backport-7.67.x
to backport the original PR to the7.67.x
branch).Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.
If something goes wrong, the author will be notified and at this point a manual backporting is needed.