Skip to content
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

[7.67.x] Backport JIRAs [RHDM-1910][RHDM-1908][RHDM-1920][RHDM-1940][RHPAM-4444] #4559

Conversation

tkobayas
Copy link
Contributor

@tkobayas tkobayas commented Jul 21, 2022

PLEASE DO NOT SQUASH WHEN MERGING

Ports
This is a PR to backport 5 commits to 7.67.x
Relevant 7.x PRs:

JIRA:
https://issues.redhat.com/browse/RHDM-1910 -> DROOLS-6920
https://issues.redhat.com/browse/RHDM-1908 -> DROOLS-6936
https://issues.redhat.com/browse/RHDM-1920 -> DROOLS-6961
https://issues.redhat.com/browse/RHDM-1940 -> DROOLS-7017
https://issues.redhat.com/browse/RHPAM-4444 -> DROOLS-7062

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

    • for jenkins job: please add comment: Jenkins run fdb
    • for github actions job: add the label 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-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|kogito-apps|kogito-examples] 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|kogito-apps|kogito-examples] mandrel

tkobayas and others added 5 commits July 21, 2022 16:21
apache#4341)

* [DROOLS-6920] Fails to parse a constraint connected with OR with a bind variable on right side in executable-model

* - Additional test
apache#4397)

* [DROOLS-6961] NullPointerException in LambdaConsequence with global in executable-model

* change Suppliers order instead of boolean flag
apache#4461)

* [DROOLS-7017] "_this cannot be resolved" in LambdaExtractor when involving a declaration in pattern

* - fix Boolean to primitive boolean
@tkobayas
Copy link
Contributor Author

tkobayas commented Jul 25, 2022

PLEASE DO NOT SQUASH WHEN MERGING

Hi @mariofusco Please merge these backport commits without squash, thanks! (Will do for 7.67.x-blue)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants