Drools is a rule engine, DMN engine and complex event processing (CEP) engine for Java.

Last update: Dec 31, 2022

Overview

An open source rule engine, DMN engine and complex event processing (CEP) engine for Java™ and the JVM Platform.

Drools is a business rule management system with a forward-chaining and backward-chaining inference based rules engine, allowing fast and reliable evaluation of business rules and complex event processing. A rule engine is also a fundamental building block to create an expert system which, in artificial intelligence, is a computer system that emulates the decision-making ability of a human expert.

Be sure to check out the Drools' project website and documentation!

Developing Drools and jBPM

If you want to build or contribute to a kiegroup project, read this document.

It will save you and us a lot of time by setting up your development environment correctly. It solves all known pitfalls that can disrupt your development. It also describes all guidelines, tips and tricks. If you want your pull requests (or patches) to be merged, please respect those guidelines.

Comments

[DROOLS-7037] Moving efesto/pmml-engine to kie-pmml-trusty
@mariofusco @evacchi @danielezonca @tkobayas @tarilabs

This PR

completely remove Assembler, Weaver, and related code

completely remove usage of KieBase/KnowledgeBuilder and relates

remove direct dependency from pmml drools models and rule-engine specific code

implements usage of efesto framework for inter-engine communication

enforce compilation vs runtime separation (split PMMLContext in PMMLCompilationContext and PMMLRuntimeContext)

update DMNKiePMMLTrustyInvocationEvaluator to use the efesto framework

modify some DMN classes that were been tweaked, in the past, to cope with DMN-> PMML invocation inside both Kogito and other context

update kie-maven-plugin to use the new efesto-based pmml implementation

add a utility method to kie-memory-compiler

The signature change of "API" models, together with the split of PMMLContext lead to a lot of modified files.

@tarilabs Could you please take a look at the modification I've done inside DMN ? Thanks!

This PR needs companion ones https://github.com/kiegroup/kogito-runtimes/pull/2347 https://github.com/kiegroup/kogito-examples/pull/1360 https://github.com/kiegroup/kogito-apps/pull/1429

JIRA:

link

referenced Pull Requests:

https://github.com/kiegroup/drools/pull/4511

https://github.com/kiegroup/drools/pull/4513

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

Depends on

https://github.com/kiegroup/drools/pull/4511
opened by gitgabrio 148
Bump postgresql from 42.2.23 to 42.2.25 in /build-parent
Bumps postgresql from 42.2.23 to 42.2.25.

Changelog

Sourced from postgresql's changelog.

Changelog

Notable changes since version 42.0.0, read the complete History of Changes.

The format is based on Keep a Changelog.

[Unreleased]

Changed

Added

Fixed

[42.3.2] (2022-02-01 07:35:41 -0500)

Security

CVE-2022-21724 pgjdbc instantiates plugin instances based on class names provided via authenticationPluginClassName, sslhostnameverifier, socketFactory, sslfactory, sslpasswordcallback connection properties. However, the driver did not verify if the class implements the expected interface before instantiating the class. This would allow a malicious class to be instantiated that could execute arbitrary code from the JVM. Fixed in commit

Changed

perf: read in_hot_standby GUC on connection [PR #2334](pgjdbc/pgjdbc#2334)

test: materialized view privileges [PR #2209](pgjdbc/pgjdbc#2209) fixes [Issue #2060](pgjdbc/pgjdbc#2060)

docs: add info about convenience maven project [PR #2407](pgjdbc/pgjdbc#2407)

docs: Document timezone reversal from POSIX to ISO [PR #2413](pgjdbc/pgjdbc#2413)

fix: we will ask the server if it supports GSS Encryption if gssEncryption is prefer or require [PR #2396](pgjdbc/pgjdbc#2396) remove the need to have a ticket in the cache before asking the server if gss encryptions are supported

docs: remove Java 6 and 7 references from contributing [PR #2385](pgjdbc/pgjdbc#2385)

style: remove Java 8 / JDBC 4.2 checks [PR #2383](pgjdbc/pgjdbc#2383) Remove all remaining checks whether the source is lower than Java 8 or JDBC 4.2.

fix: throw SQLException for #getBoolean BIT(>1) [PR #2386](pgjdbc/pgjdbc#2386) Throw SQLException instead of ClassCastException when calling CallableStatement#getBoolean(int) on BIT(>1).

style: import java.time types in more classes [PR #2382](pgjdbc/pgjdbc#2382) Use imports for java.time types in all remaining classes.

style: import java.time types in TimestampUtils [PR #2380](pgjdbc/pgjdbc#2380) Use imports for java.time types in TimestampUtils.

refactor: Change internal constructors to pass only connection Properties Changes internal constructors for PgConnection and related classes to only accept the connection properties object and remove the user and password arguments. Any locations that required those fields can retrieve them from the properties map.

test: Fix DatabaseMetadataTest to perform mview tests only on 9.3+

perf: read in_hot_standby GUC on connection [PR #2334](pgjdbc/pgjdbc#2334)

doc: improv doc around binary decoding of numeric data #2331

Add cert key type checking to chooseClientAlias [PR #2417](pgjdbc/pgjdbc#2417)

Added

feat: Add authenticationPluginClassName option to provide passwords at runtime Adds authenticationPluginClassName connection property that allows end users to specify a class that will provide the connection passwords at runtime. Users implementing that interface must ensure that each invocation of the method provides a new char[] array as the contents will be filled with zeroes by the driver after use.Call sites within the driver have been updated to use the char[] directly wherever possible. This includes direct usage in the GSS authentication code paths that internally were already converting the String password into a char[] for internal usage. This allows configuring a connection with a password that must be generated on the fly or periodically changes. [PR #2369](pgjdbc/pgjdbc#2369) original issue [Issue #2102](pgjdbc/pgjdbc#2102)

feat: add tcpNoDelay option [PR #2341](pgjdbc/pgjdbc#2341) fixes [Issue #2324](pgjdbc/pgjdbc#2324)

... (truncated)

Commits

6f64a38 increment version (#2436)

bafcb32 fix checkstyle and javadoc issues (#2434)

8a363a7 Merge pull request from GHSA-v7wg-cpwc-24m4

51c70a9 fix: Issue #2267, version 14 returns UNDEFINED FUNCTION for testInvokeFunctio...

512799b Changelog 42.2.24 (#2258)

88cfcca fix startup regressions caused by PR #1949. Instead of checking all types by ...

2917c1f Backport PR2148 into 42.2.x (#2254)

7bf89c8 backpatch PR#2247 (#2249)

33af6a7 PgDatabaseMetaData.getIndexInfo() cast operands to smallint (#2242) (#2253)

5c6041b test: Handle cleanup of privileged connection in DatabaseMetaDataTest

Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR

@dependabot recreate will recreate this PR, overwriting any edits that have been made to it

@dependabot merge will merge this PR after your CI passes on it

@dependabot squash and merge will squash and merge this PR after your CI passes on it

@dependabot cancel merge will cancel a previously requested merge and block automerging

@dependabot reopen will reopen this PR if it is closed

@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot use these labels will set the current labels as the default for future PRs for this repo and language

@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language

@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language

@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependencies
opened by dependabot[bot] 132
KOGITO-6962 DSL reorganization for flexibility
https://issues.redhat.com/browse/KOGITO-6962

Depends on https://github.com/kiegroup/kogito-pipelines/pull/416

Related PRs:

https://github.com/kiegroup/kogito-pipelines/pull/416

https://github.com/kiegroup/drools/pull/4301

dsl-test
opened by radtriste 121
DROOLS 7003, Refactor addKnowledgeResource
replace xxxToPackageDescr methods by their corresponding "handlers"

remove unused methods from KnowledgeBuilderImpl class

example:

public void addPackageFromDrl(Resource resource) throws DroolsParserException,IOException { addPackageWithResource(new DrlResourceHandler(configuration).process(resource), resource); }

to

public void addPackageFromDrl(Resource resource) throws DroolsParserException,IOException{ DrlResourceHandler handler = new DrlResourceHandler(this.getBuilderConfiguration()); PackageDescr descr = handler.process(resource,null); this.results.addAll(handler.getResults()); addPackageWithResource(descr, resource); }
opened by nprentza 113
[DROOLS-7174] Split API/Core modules
@mariofusco @tkobayas @fjtirado @pibizza

This PR

creates an efesto-common-core module

move jackson-databinding dependency in the efesto-common-core

mode dependent code from efesto-common-api to efesto-common-core

refactor EfestoContext* code to reflect new organization - creating specific Utils in compilation-manager-core and runtime-manager-core modules

propagate the modified dependencies/code down to plugins implementations

JIRA:

DROOLS-7174

Needs: https://github.com/kiegroup/kogito-runtimes/pull/2511

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-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 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

for mandrel lts checks
Run native checks against Mandrel image and quarkus lts branch Please add comment: Jenkins run mandrel-lts

for a specific mandrel lts check
Run native checks against Mandrel image and quarkus lts branch Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] mandrel-lts
opened by gitgabrio 109
DROOLS-6847 Refactor ResourceToPkgDescrMapper

ResourceToPkgDescrMapper is a nested interface within CompositeKnowledgeBuilderImpl class in the drools-compiler module. Each (public static final) field within this interface defines a lambda function of the form: PackageDescr map(KnowledgeBuilderImpl kBuilder, ResourceDescr resourceDescr) throws Exception;, for instance ResourceToPkgDescrMapper DRL_TO_PKG_DESCR = ( kBuilder, resourceDescr ) -> kBuilder.drlToPackageDescr(resourceDescr.resource);.

The dependency on the entire kBuilder object is often unnecessary for most of these methods. In fact, in this case the entire kBuilder is passed, but only the configuration field is really necessary in the drlToPackageDescr method.

Therefore, this method can be moved in a new class, e.g. class ProcessorDrl, that will be instantiated with a reference to the kBuilder.configuration field, and have a process(Resource resource) method implemented to replace the corresponding drlToPackageDescr method of the kBuilder class. Then the entire lambda can be substituted by something in the form: ResourceToPkgDescrMapper DRL_TO_PKG_DESCR = ( kBuilder, resourceDescr ) -> { ProcessorDrl processor = new ProcessorDrl(kBuilder.getBuilderConfiguration()); PackageDescr pkg = processor.process(resourceDescr.resource); processor.getResults().forEach(kBuilder::addBuilderResult); return pkg;};

The goal of this PR is the refactoring of such methods from the KnowledgeBuilderImpl class to a series of Processor classes similar to ProcessorDrl, and update the lambdas in a similar way.

opened by nprentza 105
Bump postgresql from 42.2.23 to 42.3.3 in /build-parent
Bumps postgresql from 42.2.23 to 42.3.3.

Changelog

Sourced from postgresql's changelog.

Changelog

Notable changes since version 42.0.0, read the complete History of Changes.

The format is based on Keep a Changelog.

[Unreleased]

Changed

Added

Fixed

[42.3.3] (2022-02-15 11:32:24 -0500)

Changed

fix: Removed loggerFile and loggerLevel configuration. While the properties still exist. They can no longer be used to configure the driver logging. Instead use java.util.logging configuration mechanisms such as logging.properties.

Added

Fixed

[42.3.2] (2022-02-01 07:35:41 -0500)

Security

CVE-2022-21724 pgjdbc instantiates plugin instances based on class names provided via authenticationPluginClassName, sslhostnameverifier, socketFactory, sslfactory, sslpasswordcallback connection properties. However, the driver did not verify if the class implements the expected interface before instantiating the class. This would allow a malicious class to be instantiated that could execute arbitrary code from the JVM. Fixed in commit

Changed

perf: read in_hot_standby GUC on connection [PR #2334](pgjdbc/pgjdbc#2334)

test: materialized view privileges [PR #2209](pgjdbc/pgjdbc#2209) fixes [Issue #2060](pgjdbc/pgjdbc#2060)

docs: add info about convenience maven project [PR #2407](pgjdbc/pgjdbc#2407)

docs: Document timezone reversal from POSIX to ISO [PR #2413](pgjdbc/pgjdbc#2413)

fix: we will ask the server if it supports GSS Encryption if gssEncryption is prefer or require [PR #2396](pgjdbc/pgjdbc#2396) remove the need to have a ticket in the cache before asking the server if gss encryptions are supported

docs: remove Java 6 and 7 references from contributing [PR #2385](pgjdbc/pgjdbc#2385)

style: remove Java 8 / JDBC 4.2 checks [PR #2383](pgjdbc/pgjdbc#2383) Remove all remaining checks whether the source is lower than Java 8 or JDBC 4.2.

fix: throw SQLException for #getBoolean BIT(>1) [PR #2386](pgjdbc/pgjdbc#2386) Throw SQLException instead of ClassCastException when calling CallableStatement#getBoolean(int) on BIT(>1).

style: import java.time types in more classes [PR #2382](pgjdbc/pgjdbc#2382) Use imports for java.time types in all remaining classes.

style: import java.time types in TimestampUtils [PR #2380](pgjdbc/pgjdbc#2380) Use imports for java.time types in TimestampUtils.

refactor: Change internal constructors to pass only connection Properties Changes internal constructors for PgConnection and related classes to only accept the connection properties object and remove the user and password arguments. Any locations that required those fields can retrieve them from the properties map.

test: Fix DatabaseMetadataTest to perform mview tests only on 9.3+

perf: read in_hot_standby GUC on connection [PR #2334](pgjdbc/pgjdbc#2334)

doc: improv doc around binary decoding of numeric data #2331

Add cert key type checking to chooseClientAlias [PR #2417](pgjdbc/pgjdbc#2417)

... (truncated)

Commits

9effea4 Update version number and create changelog for 42.3.3 (#2455)

12c7fb4 fix javadocs (#2454)

f6d4703 Merge pull request from GHSA-673j-qm5f-xpv8

c03664e Update SECURITY.md

ddc6315 Update SECURITY.md (#2445)

38d9608 add security policy link to index (#2440)

ee23fd0 Create SECURITY.md

728c04e fix javadoc failure to document parameters (#2432)

2de239f Generate changelog (#2431)

f4d0ed6 Merge pull request from GHSA-v7wg-cpwc-24m4

Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR

@dependabot recreate will recreate this PR, overwriting any edits that have been made to it

@dependabot merge will merge this PR after your CI passes on it

@dependabot squash and merge will squash and merge this PR after your CI passes on it

@dependabot cancel merge will cancel a previously requested merge and block automerging

@dependabot reopen will reopen this PR if it is closed

@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot use these labels will set the current labels as the default for future PRs for this repo and language

@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language

@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language

@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependencies
opened by dependabot[bot] 103
Refactoring ResourceToPkgDescrMapper
Thank you for submitting this pull request

NOTE!: Double check the target branch for this PR. The default is main so it will target Drools 8 / Kogito / Optaplanner 8. If this PR is not strictly related to drools and kogito project in drools.git, it should probably target 7.xas a branch

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)

paste the link(s) from GitHub here

link 2

link 3 etc.

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:

a pull request please add comment: Jenkins retest this

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
opened by nprentza 90
Bump postgresql from 42.4.0 to 42.4.1 in /build-parent
Bumps postgresql from 42.4.0 to 42.4.1.

Changelog

Sourced from postgresql's changelog.

Changelog

Notable changes since version 42.0.0, read the complete History of Changes.

The format is based on Keep a Changelog.

[Unreleased]

Changed

Added

Fixed

[42.4.1] (2022-08-01 16:24:20 -0400)

Security

fix: CVE-2022-31197 Fixes SQL generated in PgResultSet.refresh() to escape column identifiers so as to prevent SQL injection.

Previously, the column names for both key and data columns in the table were copied as-is into the generated SQL. This allowed a malicious table with column names that include statement terminator to be parsed and executed as multiple separate commands.

Also adds a new test class ResultSetRefreshTest to verify this change.

Reported by Sho Kato

Changed

chore: skip publishing pgjdbc-osgi-test to Central

chore: bump Gradle to 7.5

test: update JUnit to 5.8.2

Added

chore: added Gradle Wrapper Validation for verifying gradle-wrapper.jar

chore: added "permissions: contents: read" for GitHub Actions to avoid unintentional modifications by the CI

chore: support building pgjdbc with Java 17

Fixed

Commits

bd91c4c Prepare for release (#2580)

739e599 Merge pull request from GHSA-r38f-c4h4-hqq2

736f959 fix: replace syncronization in Connection.close with compareAndSet

4673fd2 feat: synchronize statement executions (e.g. avoid deadlock when Connection.i...

fd31a06 update the website content (#2578)

a6044d0 set a timeout to get the return from requesting SSL upgrade. (#2572)

58d6fa0 test: bump system-stubs-jupiter to 2.0.1 to support Java 16+

b452d8c test: avoid concurrent executions of tests that update environment and system...

aa5758a test: update JUnit to 5.8.2

36cd24c fix: log connection URL when it can't be parsed

Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR

@dependabot recreate will recreate this PR, overwriting any edits that have been made to it

@dependabot merge will merge this PR after your CI passes on it

@dependabot squash and merge will squash and merge this PR after your CI passes on it

@dependabot cancel merge will cancel a previously requested merge and block automerging

@dependabot reopen will reopen this PR if it is closed

@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot use these labels will set the current labels as the default for future PRs for this repo and language

@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language

@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language

@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependencies java
opened by dependabot[bot] 89
Bump spring-core from 5.3.14 to 5.3.18 in /build-parent
Bumps spring-core from 5.3.14 to 5.3.18.

Release notes

Sourced from spring-core's releases.

v5.3.18

:star: New Features

Restrict access to property paths on Class references #28261

Introduce cancel(boolean mayInterruptIfRunning) in ScheduledTask #28233

:lady_beetle: Bug Fixes

Move off deprecated API in SessionTransactionData #28234

:notebook_with_decorative_cover: Documentation

Introduce warnings in documentation of SerializationUtils #28246

Update copyright date in reference manual #28237

@Transactional test does not execute all JPA lifecycle callback methods #28228

:heart: Contributors

We'd like to thank all the contributors who worked on this release!

@izeye

@quaff

v5.3.17

:star: New Features

Using DataClassRowMapper causes "No property found for column" debug messages in logs #28179

Improve diagnostics in SpEL for large array creation #28145

Support custom HTTP status in client-side REST testing support #28105

AsyncRestTemplate logging too verbose #28049

:lady_beetle: Bug Fixes

java.lang.NoClassDefFoundError: org/springframework/cglib/beans/BeanMapEmitter #28110

CronExpression fails to calculate properly next execution when running on the day of winter daylight saving time #28095

Private init/destroy method may be invoked twice #28083

MappingJacksonValue and Jackson2CodecSupport#registerObjectMappersForType do not work together #28045

SpEL fails to recover from error during MIXED mode compilation #28043

When returning a ResponseEntity with a Flux while the function is suspended, it fails to encode the body #27809

:notebook_with_decorative_cover: Documentation

Improve documentation for @EnabledIf and @DisabledIf test support #28157

Links to Spring Security are broken in the reference guide #28135

Document that transaction rollback rules may result in unintentional matches #28125

Improve documentation for TestContext events #27757

Clarify behavior for generics support in BeanUtils.copyProperties #27259

:hammer: Dependency Upgrades

... (truncated)

Commits

707a24c Release v5.3.18

002546b Refine PropertyDescriptor filtering

1627f57 Disable flaky integration tests for now

3811cd4 Introduce warnings in documentation of SerializationUtils

d927e37 Add "Testing ORM entity lifecycle callbacks" note to Testing chapter

1d302bf Introduce tests for gh-28228

4b150fd Update copyright date in reference manual

3a6016d Merge pull request #28238 from izeye

135506f Update copyright year of EvaluationTests

cb36ca3 Upgrade to ASM master

Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR

@dependabot recreate will recreate this PR, overwriting any edits that have been made to it

@dependabot merge will merge this PR after your CI passes on it

@dependabot squash and merge will squash and merge this PR after your CI passes on it

@dependabot cancel merge will cancel a previously requested merge and block automerging

@dependabot reopen will reopen this PR if it is closed

@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot use these labels will set the current labels as the default for future PRs for this repo and language

@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language

@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language

@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependencies run_fdb
opened by dependabot[bot] 88
[DROOLS-6719] MVELDialect.java::loadImportedClass optimization

When doing a KieBuilder::buildAll, mvel dialect tries to import all functions looking for the class in the classpath first, which takes too long, and then in drools, which is pretty faster. I propose to exchange the order in which they are looked for a better performance.

In my tests it's about 33%-50% faster. (in a DRL with 1000 rules and 50 function, ::buildAll goes from 10s to 6s)

Can it be applied to 7.62.0.Final too, please?

First time pulling, sorry in advance for any inconvenience.

opened by HSnicolascerrejon 86
Bump version.com.thoughtworks.xstream from 1.4.19 to 1.4.20 in /build-parent
Bumps version.com.thoughtworks.xstream from 1.4.19 to 1.4.20. Updates xstream from 1.4.19 to 1.4.20

Commits

See full diff in compare view

Updates xstream-hibernate from 1.4.19 to 1.4.20

Commits

See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR

@dependabot recreate will recreate this PR, overwriting any edits that have been made to it

@dependabot merge will merge this PR after your CI passes on it

@dependabot squash and merge will squash and merge this PR after your CI passes on it

@dependabot cancel merge will cancel a previously requested merge and block automerging

@dependabot reopen will reopen this PR if it is closed

@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)

@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot use these labels will set the current labels as the default for future PRs for this repo and language

@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language

@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language

@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

dependencies java
opened by dependabot[bot] 80
[DROOLS-7264] Add ruleunits decisiontable tests
JIRA: https://issues.redhat.com/browse/DROOLS-7264

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-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 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

for mandrel lts checks
Run native checks against Mandrel image and quarkus lts branch Please add comment: Jenkins run mandrel-lts

for a specific mandrel lts check
Run native checks against Mandrel image and quarkus lts branch Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] mandrel-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 the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

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.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.
opened by tkobayas 1
KOGITO-8400 Setup Makefile
Thank you for submitting this pull request

NOTE!: Double check the target branch for this PR. The default is main so it will target Drools 8 / Kogito. If this PR is not strictly related to drools and kogito project in drools.git, it should probably target 7.xas a branch

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)

paste the link(s) from GitHub here

link 2

link 3 etc.

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-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 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

for mandrel lts checks
Run native checks against Mandrel image and quarkus lts branch Please add comment: Jenkins run mandrel-lts

for a specific mandrel lts check
Run native checks against Mandrel image and quarkus lts branch Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] mandrel-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 the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

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.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.
opened by radtriste 3
KOGITO-8387: drools version upgrade in kie-benchmarks when a new bran…
…ch was created

Thank you for submitting this pull request

NOTE!: Double check the target branch for this PR. The default is main so it will target Drools 8 / Kogito. If this PR is not strictly related to drools and kogito project in drools.git, it should probably target 7.xas a branch

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)

KOGITO-8387

referenced Pull Requests: (please edit the URLs of referenced pullrequests if they exist)

paste the link(s) from GitHub here

link 2

link 3 etc.

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-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 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

for mandrel lts checks
Run native checks against Mandrel image and quarkus lts branch Please add comment: Jenkins run mandrel-lts

for a specific mandrel lts check
Run native checks against Mandrel image and quarkus lts branch Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] mandrel-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 the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

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.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.
opened by mbiarnes 0
KOGITO-8115: Deploy jobs should deploy locally and then push to Nexus
Thank you for submitting this pull request

NOTE!: Double check the target branch for this PR. The default is main so it will target Drools 8 / Kogito. If this PR is not strictly related to drools and kogito project in drools.git, it should probably target 7.xas a branch

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)

KOGITO-8115

referenced Pull Requests: (please edit the URLs of referenced pullrequests if they exist)

paste the link(s) from GitHub here

link 2

link 3 etc.

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-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 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

for mandrel lts checks
Run native checks against Mandrel image and quarkus lts branch Please add comment: Jenkins run mandrel-lts

for a specific mandrel lts check
Run native checks against Mandrel image and quarkus lts branch Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] mandrel-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 the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

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.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.
opened by mbiarnes 0
[7.x] [DO-NOT-MERGE] test cases with "contains"
This draft PR is test cases just to demonstrate contains behavior.

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-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 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

for mandrel lts checks
Run native checks against Mandrel image and quarkus lts branch Please add comment: Jenkins run mandrel-lts

for a specific mandrel lts check
Run native checks against Mandrel image and quarkus lts branch Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] mandrel-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 the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

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.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.
opened by tkobayas 0