RHPAM-4779: SLA due date value in ProcessInstanceLog table is not upd… #2396
Conversation
|
|
jenkins run fdb |
|
jenkins do fdb |
gmunozfe
added
backport-7.67.x
|
jenkins do fdb |
|
@nmirasch could you fix this compilation error in droolsjbpm-integration repository?
|
@nmirasch I've just made a first approach in case you want to review and reuse it bf6bf43a2584d7135305ca4c5481fc1c3d102dee |
…ated after updating process SLA
nmirasch
force-pushed
the
RHPAM-4779_7.x
branch
from
795c216
to
c563d25
Compare
|
jenkins do fdb |
|
|
Full downstream build has only 1 failure, and it seems unrelated |
#2396) * RHPAM-4779: SLA due date value in ProcessInstanceLog table is not updated after updating process SLA * Add test for coverage --------- Co-authored-by: gmunozfe <[email protected]>
#2396) * RHPAM-4779: SLA due date value in ProcessInstanceLog table is not updated after updating process SLA * Add test for coverage --------- Co-authored-by: gmunozfe <[email protected]>
#2396) (#2437) * RHPAM-4779: SLA due date value in ProcessInstanceLog table is not updated after updating process SLA * Add test for coverage --------- Co-authored-by: nmirasch <[email protected]> Co-authored-by: gmunozfe <[email protected]>
#2396) (#2436) * RHPAM-4779: SLA due date value in ProcessInstanceLog table is not updated after updating process SLA * Add test for coverage --------- Co-authored-by: nmirasch <[email protected]> Co-authored-by: gmunozfe <[email protected]>
… not upd… (kiegroup#2396) (kiegroup#2436)" This reverts commit 2d8b32b.
…earch for rem… (#2446) * Revert "RHPAM-4779: SLA due date value in ProcessInstanceLog table is not upd… (#2396) (#2436)" This reverts commit 2d8b32b. * [JBPM-10242] Allow the possibility of disabling linear search for removeJob and getTimerByName operations (#2441) * Try to cancel timer always, and only search if timer cancellation fails * Skipping list search completely if !searchIfFailed * [JBPM-10242] Always skipping linear search Unless explicilty stated with property org.jbpm.ejb.timer.linear.search * [JBPM-10242] Disable linear search on condition Setting org.jbpm.ejb.timer.disable.linear.search and org.jbpm.ejb.timer.disable.linear.remove to true * [JBPM-10242] Fixing integration tests --------- Co-authored-by: krisv <[email protected]> --------- Co-authored-by: Francisco Javier Tirado Sarti <[email protected]> Co-authored-by: krisv <[email protected]>
…ated after updating process SLA
JIRA: https://issues.redhat.com/browse/RHPAM-4779
referenced Pull Requests:
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
a full downstream build please add comment: Jenkins 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
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.xto backport the original PR to the7.67.xbranch).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.