[DROOLS-6961] NullPointerException in LambdaConsequence with global i… #4397
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
…n executable-model
|
Note, the test is TurtleTest so you need to have the |
mariofusco
approved these changes
May 19, 2022
hellowdan
approved these changes
May 19, 2022
tkobayas
added a commit
to tkobayas/drools
that referenced
this pull request
May 23, 2022
apache#4397) * [DROOLS-6961] NullPointerException in LambdaConsequence with global in executable-model * change Suppliers order instead of boolean flag
tkobayas
added a commit
to tkobayas/drools
that referenced
this pull request
Jul 21, 2022
apache#4397) * [DROOLS-6961] NullPointerException in LambdaConsequence with global in executable-model * change Suppliers order instead of boolean flag
mariofusco
pushed a commit
that referenced
this pull request
Jul 25, 2022
#4397) * [DROOLS-6961] NullPointerException in LambdaConsequence with global in executable-model * change Suppliers order instead of boolean flag
tkobayas
added a commit
to tkobayas/drools
that referenced
this pull request
Jul 25, 2022
apache#4397) * [DROOLS-6961] NullPointerException in LambdaConsequence with global in executable-model * change Suppliers order instead of boolean flag
mariofusco
pushed a commit
that referenced
this pull request
Jul 25, 2022
#4397) * [DROOLS-6961] NullPointerException in LambdaConsequence with global in executable-model * change Suppliers order instead of boolean flag
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.
…n executable-model
Ports
This PR is for 7.x
for main -> https://github.com/kiegroup/drools/pull/4402
JIRA:
https://issues.redhat.com/browse/DROOLS-6961
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|optaplanner|kogito-apps|kogito-examples|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] tests
for a full downstream build
run_fdba 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|optaplanner|kogito-apps|kogito-examples|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] 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|optaplanner|kogito-apps|kogito-examples|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] quarkus-branch
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|optaplanner|kogito-apps|kogito-examples|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] native
for mandrel checks
Run native checks against Mandrel image
Please add comment: Jenkins run mandrel
for a specific mandrel check
Run native checks against Mandrel image
Please add comment: Jenkins (re)run [drools|kogito-runtimes|optaplanner|kogito-apps|kogito-examples|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] mandrel