Revert "[JBPM-9549] Upgrade SpringBoot to 2.3.4 (#1565)" #1578
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
This reverts commit 9a1b93b.
|
Jenkins run fdb. |
|
I agree that the issue needs to be solved, now we saw only problems in optaweb's repositories. And the FDB failed due not able download cypress docker image AFAIK. |
|
please link here also related merged PRs like kiegroup/jbpm-work-items#171 and kiegroup/droolsjbpm-integration#2370 |
|
Did the same #1579 but added two commits on droolsjbpm-integration and jbpm-work-items. For having all PR on the branch with the same name. I will close this. |
|
Sorry, I wasn't aware this should be a cross-repo PR because #1565 didn't list the dependent PRs. |
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.
This reverts commit 9a1b93b.
#1565 was merged without green FDB and causes several issues. I'm opening a reverting PR to see whether all of the issues seen after #1565 was merged will go away. If yes, I suggest to merge this to reach a safe restore point. Then the Spring Boot upgrade should be done again. All issues discovered by FDB must be resolved before the Spring Boot upgrade PR is merged.
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