-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Sync GitHub workflows from main branch #13790
Conversation
Gradle Check (Jenkins) Run Completed with:
|
I see the same reason why the gradle checks are failing. |
Gradle Check (Jenkins) Run Completed with:
|
@prudhvigodithi do you need to rabase? (incorporating #13787 (comment)) |
This has to be force merged @reta and existing PR's (to execute gradle check) should be rebased. |
The lastest build still fails with:
|
Ya thats because I'm trying to test (re-run the gradle check) with old open PR's to see if there is any way to avoid rebase for folks who have the PR open :). For any PR's that created after this was merged (example on |
@reta just added |
Gradle Check (Jenkins) Run Completed with:
|
Gradle Check (Jenkins) Run Completed with:
|
Gradle Check (Jenkins) Run Completed with:
|
@prudhvigodithi sorry about that:
it seems like 8 is no go :( my apologies |
Gradle Check (Jenkins) Run Completed with:
|
Updated to only 11 @reta, also for assemble task to work on windows, do we need to backport this PR #1412 ? As I see the run passed https://github.com/opensearch-project/OpenSearch/actions/runs/9181040634/job/25246840531?pr=13754 skipped the following tasks
|
Also FYI @bbarani @dblock @reta for now I have created 2 new branch protection rules for |
Gradle Check (Jenkins) Run Completed with:
|
Signed-off-by: Prudhvi Godithi <pgodithi@amazon.com>
Gradle Check (Jenkins) Run Completed with:
|
I was able to handle this within the |
Chatted with @prudhvigodithi , the Gradle check fails with because the original branch (1.x) does not have the ENV variable populated.
|
943870a
into
opensearch-project:1.x
Thanks @reta will wait for a backport PR for 1.3, else I will create it manually. |
The backport to
To backport manually, run these commands in your terminal: # Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch/backport-1.3 1.3
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch/backport-1.3
# Create a new branch
git switch --create backport/backport-13790-to-1.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 943870a644b10abdb25492a538c2925272adae0a
# Push it to GitHub
git push --set-upstream origin backport/backport-13790-to-1.3
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch/backport-1.3 Then, create a pull request where the |
Added the backport workflow but since this still failed to backport raised a manual backport PR #13804. |
Description
While working on this failed backport #13786 (comment), I have noticed majority of the existing workflows are either not backported, synced or updated, I have tried to find what ever I can and updated through this PR.
Related Issues
Part of: #3713
Check List
New functionality has been documented.New functionality has javadoc addedAPI changes companion pull request created.Commit changes are listed out in CHANGELOG.md file (See: Changelog)Public documentation issue/PR createdBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.