-
Notifications
You must be signed in to change notification settings - Fork 572
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
Bump org.apache.santuario:xmlsec from 2.1.7 to 2.2.6 in /kie-osgi/kie-karaf-features #2998
Conversation
Bumps org.apache.santuario:xmlsec from 2.1.7 to 2.2.6. --- updated-dependencies: - dependency-name: org.apache.santuario:xmlsec dependency-type: direct:production ... Raised by dependabot
what's the diff to #2992 ? or you have somewhere linked another related change? |
jenkins retest this please |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
@mareknovotny Thank you for merging.
The fix is the same as #2992 . The reason why I created a PR by myself is that we cannot re-trigger GHA when it's dependabot PR, right? I wanted to rerun GHA Java 8 tests for kie-karaf-itests with the latest 7.x. |
we can re-trigger GHA and Jenkins CI just by comments ;) There should not be any problem with that. Only problem is if you want to add more changes to the dependabot's PR from other repositories to fix tests or additional changes for other cross repository PRs ;) |
) (#2999) Bumps org.apache.santuario:xmlsec from 2.1.7 to 2.2.6. --- updated-dependencies: - dependency-name: org.apache.santuario:xmlsec dependency-type: direct:production ... Raised by dependabot Co-authored-by: Toshiya Kobayashi <[email protected]>
) (#3000) Bumps org.apache.santuario:xmlsec from 2.1.7 to 2.2.6. --- updated-dependencies: - dependency-name: org.apache.santuario:xmlsec dependency-type: direct:production ... Raised by dependabot Co-authored-by: Toshiya Kobayashi <[email protected]>
Replaces #2992
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.x
to backport the original PR to the7.67.x
branch).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.