-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Adding a workflow to automatically publish releases after a tag is pushed #3813
Merged
saratvemulapalli
merged 1 commit into
opensearch-project:main
from
saratvemulapalli:auto-tagged-release
Jul 8, 2022
Merged
Adding a workflow to automatically publish releases after a tag is pushed #3813
saratvemulapalli
merged 1 commit into
opensearch-project:main
from
saratvemulapalli:auto-tagged-release
Jul 8, 2022
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: Sarat Vemulapalli <vemulapallisarat@gmail.com>
dblock
approved these changes
Jul 7, 2022
VachaShah
approved these changes
Jul 7, 2022
Gradle Check (Jenkins) Run Completed with:
|
Flaky test
|
saratvemulapalli
added
CI
CI related
release
documentation
Improvements or additions to documentation
labels
Jul 7, 2022
Gradle Check (Jenkins) Run Completed with:
|
owaiskazi19
approved these changes
Jul 7, 2022
Gradle Check (Jenkins) Run Completed with:
|
Gradle Check (Jenkins) Run Completed with:
|
Codecov Report
@@ Coverage Diff @@
## main #3813 +/- ##
=======================================
Coverage ? 70.37%
Complexity ? 56558
=======================================
Files ? 4557
Lines ? 272681
Branches ? 40038
=======================================
Hits ? 191900
Misses ? 64555
Partials ? 16226 Continue to review full report at Codecov.
|
saratvemulapalli
changed the title
Adding workflow to automatically publish releases after a tag is pushed
Adding a workflow to automatically publish releases after a tag is pushed
Jul 8, 2022
1 task
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
Signed-off-by: Sarat Vemulapalli vemulapallisarat@gmail.com
Description
Release tags are automatically published by https://github.com/opensearch-project/opensearch-build.
Github releases [1] are not published and are manually published after every release.
This workflow automates publishing github releases.
It automatically includes the release notes.
I've tested this manually on my fork:
Release: https://github.com/saratvemulapalli/OpenSearch/releases/tag/5.4.6
Workflow: https://github.com/saratvemulapalli/OpenSearch/actions/runs/2632146820
[1] https://github.com/opensearch-project/OpenSearch/releases
Check List
By 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.