RHDM-1788: changes related to upgrade of sshd-core 2.9.2 #2202
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 was referenced Jan 27, 2023
|
jenkins do fdb |
RishiRajAnand
approved these changes
Feb 9, 2023
|
jenkins do fdb |
1 similar comment
|
jenkins do fdb |
|
:o now 104 failures completely out of the loop previous failures :) |
|
jenkins do fdb |
|
there are different test failures, but not related to this change
|
domhanak
approved these changes
Feb 27, 2023
|
jenkins do fdb |
2 similar comments
|
jenkins do fdb |
|
jenkins do fdb |
mareknovotny
added
backport-7.67.x
|
jenkins do fdb |
1 similar comment
|
jenkins do fdb |
|
|
jenkins do fdb |
|
jenkins do fdb |
|
Jenkins run fdb |
This reverts commit a1b3a7d.
|
jenkins do fdb |
|
ok we have now green FDB, so as @domhanak stated we can merge and do checks on nightly for backports |
github-actions bot
pushed a commit
that referenced
this pull request
Apr 26, 2023
* Upgrade of sshd-core to 2.7.0 * Another upgrade to 2.9.2 * RHDM-1788: downgraded Wildfly for to 23.0.0.Final * RHDM-1788: removing no-showcase profile from FDB defaults * Revert "RHDM-1788: removing no-showcase profile from FDB defaults" This reverts commit a1b3a7d.
github-actions bot
pushed a commit
that referenced
this pull request
Apr 26, 2023
* Upgrade of sshd-core to 2.7.0 * Another upgrade to 2.9.2 * RHDM-1788: downgraded Wildfly for to 23.0.0.Final * RHDM-1788: removing no-showcase profile from FDB defaults * Revert "RHDM-1788: removing no-showcase profile from FDB defaults" This reverts commit a1b3a7d.
This was referenced Apr 26, 2023
Merged
Merged
Merged
mareknovotny
added a commit
that referenced
this pull request
Apr 27, 2023
* Upgrade of sshd-core to 2.7.0 * Another upgrade to 2.9.2 * RHDM-1788: downgraded Wildfly for to 23.0.0.Final * RHDM-1788: removing no-showcase profile from FDB defaults * Revert "RHDM-1788: removing no-showcase profile from FDB defaults" This reverts commit a1b3a7d. Co-authored-by: Marek Novotný <[email protected]>
mareknovotny
added a commit
that referenced
this pull request
May 4, 2023
* Upgrade of sshd-core to 2.7.0 * Another upgrade to 2.9.2 * RHDM-1788: downgraded Wildfly for to 23.0.0.Final * RHDM-1788: removing no-showcase profile from FDB defaults * Revert "RHDM-1788: removing no-showcase profile from FDB defaults" This reverts commit a1b3a7d. Co-authored-by: Marek Novotný <[email protected]>
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.
Upgrading sshd-core to 2.9.2
https://issues.redhat.com/browse/RHDM-1788 and https://issues.redhat.com/browse/RHPAM-3807
** Dependent PRs **:
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