Sync main branch with Apache main branch #31
Merged
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
Signed-off-by: Jason Porter <[email protected]>
* kie-issues#1165 Missing Apache headers. * kie-issues#1165 Missing Apache headers. # Conflicts: # .asf.yaml
…memory` & `jobs-service-embedded` (apache#2042) * NO_ISSUE: fixing named datasource's configuration for `data-index-inmemory` & `jobs-service-embedded` * - Disabling oidc in tests - Formatting classes
…es from NPM package to OS-specific Maven modules (apache#2041) * Add jitexecutor-native module * Revert unnecessary changes * Adding headers * Place binary inside JAR with classifier 'binaries' * Remove new modules from bom * Reverting some changes * Prevent jitexecutor-native-linux from building on macOS * Dry-run for publish-jitexecutor-native.yml * Oops --------- Co-authored-by: Luiz João Motta <[email protected]> # Conflicts: # .github/workflows/publish-jitexecutor-native.yml
* kie-issues#1166 Fix apache headers. * kie-issues#1166 Fix apache headers for MD files. # Conflicts: # .github/supporting-files/publish_jitexecutor_native/README.md
* kie-issues#1123:unify maven projects configuration * adjust deploy operation * Revert "adjust deploy operation" This reverts commit 49603f3. * add missing bits --------- Co-authored-by: jstastny-cz <[email protected]>
… when Data Index addon added (apache#2054)
…tor (apache#2057) Co-authored-by: Gabriele-Cardosi <[email protected]>
…pps` to actually publish the binaries JARs to Maven (apache#2049) * Update jitexecutor-native workflow to publish java artifacts * export env vars * Publish jitexecutor-native java artifacts to Apache repository * Fix pull_request trigger * Remove schedule trigger * Retrigger build * Fix Non-resolvable parent POM error * Update pull request trigger code checkout * Add only the Apache snapshots repo back to the pom.xml file --------- Co-authored-by: Tiago Bento <[email protected]> # Conflicts: # .github/workflows/publish-jitexecutor-native.yml
) Signed-off-by: Ricardo Zanini <[email protected]>
…xecutor-bpmn. (apache#2063) Co-authored-by: Gabriele-Cardosi <[email protected]>
…the optaplanner-quarkus. (apache#2067)
rgdoliveira
changed the title
This was referenced Jun 10, 2024
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.
Related 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:
for pull request checks
Please add comment: Jenkins retest this
for a specific pull request check
Please add comment: Jenkins (re)run [kogito-apps|kogito-examples] tests
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 [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 [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 [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 [kogito-apps|kogito-examples] native
for native lts checks
Run native checks against quarkus lts branch
Please add comment: Jenkins run native-lts
for a specific native lts check
Run native checks against quarkus lts branch
Please add comment: Jenkins (re)run [kogito-apps|kogito-examples] native-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.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.
Quarkus-3 PR check is failing ... what to do ?
The Quarkus 3 check is applying patches from the `.ci/environments/quarkus-3/patches`.The first patch, called
0001_before_sh.patch, is generated from Openrewrite.ci/environments/quarkus-3/quarkus3.ymlrecipe. The patch is created to speed up the check. But it may be that some changes in the PR broke this patch.No panic, there is an easy way to regenerate it. You just need to comment on the PR:
and it should, after some minutes (~20/30min) apply a commit on the PR with the patch regenerated.
Other patches were generated manually. If any of it fails, you will need to manually update it... and push your changes.