Skip to content
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

[Backport 1.x]Add windows & mac build (#591) #647

Merged
merged 2 commits into from
Dec 5, 2022

Conversation

ankitkala
Copy link
Member

Backport d12271a from #591

@ankitkala ankitkala requested a review from a team December 5, 2022 08:21
@ankitkala ankitkala force-pushed the backport/backport-591-to-1.x branch from 15c888b to 6e65227 Compare December 5, 2022 08:38
@codecov-commenter
Copy link

codecov-commenter commented Dec 5, 2022

Codecov Report

Merging #647 (95f0402) into 1.x (198e38b) will increase coverage by 1.46%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                1.x     #647      +/-   ##
============================================
+ Coverage     73.28%   74.74%   +1.46%     
- Complexity      984     1001      +17     
============================================
  Files           141      141              
  Lines          4566     4566              
  Branches        507      507              
============================================
+ Hits           3346     3413      +67     
+ Misses          910      836      -74     
- Partials        310      317       +7     
Impacted Files Coverage Δ
...ch/replication/task/CrossClusterReplicationTask.kt 77.92% <ø> (ø)
...cation/action/changes/TransportGetChangesAction.kt 63.49% <0.00%> (-20.64%) ⬇️
...earch/replication/metadata/UpdateIndexBlockTask.kt 74.19% <0.00%> (-3.23%) ⬇️
.../action/status/TransportReplicationStatusAction.kt 97.82% <0.00%> (+1.08%) ⬆️
.../replication/action/index/ReplicateIndexRequest.kt 63.52% <0.00%> (+1.17%) ⬆️
...rch/replication/task/index/IndexReplicationTask.kt 70.99% <0.00%> (+2.78%) ⬆️
...org/opensearch/replication/util/SecurityContext.kt 73.52% <0.00%> (+2.94%) ⬆️
.../replication/repository/RemoteClusterRepository.kt 75.73% <0.00%> (+2.94%) ⬆️
...ation/action/pause/PauseIndexReplicationRequest.kt 74.07% <0.00%> (+3.70%) ⬆️
...ion/action/update/UpdateIndexReplicationRequest.kt 53.84% <0.00%> (+3.84%) ⬆️
... and 13 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@ankitkala ankitkala force-pushed the backport/backport-591-to-1.x branch from a0ae725 to eee372c Compare December 5, 2022 08:59
Signed-off-by: Ankit Kala <ankikala@amazon.com>

Signed-off-by: Ankit Kala <ankikala@amazon.com>
(cherry picked from commit d12271a)
@ankitkala ankitkala force-pushed the backport/backport-591-to-1.x branch from eee372c to d372b17 Compare December 5, 2022 09:20
@ankitkala ankitkala enabled auto-merge (squash) December 5, 2022 10:11
@ankitkala ankitkala merged commit 229ead0 into 1.x Dec 5, 2022
@github-actions github-actions bot deleted the backport/backport-591-to-1.x branch December 5, 2022 10:53
@opensearch-trigger-bot
Copy link

The backport to 1.3 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.3 1.3
# Navigate to the new working tree
cd .worktrees/backport-1.3
# Create a new branch
git switch --create backport/backport-647-to-1.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 229ead061e14e5183394970b48051403fd4904f7
# Push it to GitHub
git push --set-upstream origin backport/backport-647-to-1.3
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.3

Then, create a pull request where the base branch is 1.3 and the compare/head branch is backport/backport-647-to-1.3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants