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

Adding a workflow to automatically publish releases after a tag is pushed #3813

Conversation

saratvemulapalli
Copy link
Member

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

  • New functionality includes testing.
    • All tests pass
  • New functionality has been documented.
    • New functionality has javadoc added
  • Commits are signed per the DCO using --signoff

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.

Signed-off-by: Sarat Vemulapalli <vemulapallisarat@gmail.com>
@saratvemulapalli saratvemulapalli requested review from a team and reta as code owners July 7, 2022 20:37
@github-actions
Copy link
Contributor

github-actions bot commented Jul 7, 2022

Gradle Check (Jenkins) Run Completed with:

@saratvemulapalli
Copy link
Member Author

Gradle Check (Jenkins) Run Completed with:

Flaky test

Tests with failures:
 - org.opensearch.cluster.routing.allocation.decider.DiskThresholdDeciderIT.testHighWatermarkNotExceeded

@saratvemulapalli saratvemulapalli added CI CI related release documentation Improvements or additions to documentation labels Jul 7, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Jul 7, 2022

Gradle Check (Jenkins) Run Completed with:

@github-actions
Copy link
Contributor

github-actions bot commented Jul 7, 2022

Gradle Check (Jenkins) Run Completed with:

@github-actions
Copy link
Contributor

github-actions bot commented Jul 8, 2022

Gradle Check (Jenkins) Run Completed with:

@codecov-commenter
Copy link

Codecov Report

❗ No coverage uploaded for pull request base (main@eaab798). Click here to learn what that means.
The diff coverage is n/a.

@@           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.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update eaab798...281aef1. Read the comment docs.

@saratvemulapalli saratvemulapalli merged commit a2dac25 into opensearch-project:main Jul 8, 2022
@saratvemulapalli saratvemulapalli deleted the auto-tagged-release branch July 8, 2022 00:43
@saratvemulapalli 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
@saratvemulapalli saratvemulapalli mentioned this pull request Aug 8, 2022
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI CI related documentation Improvements or additions to documentation release
Projects
Status: Planned work items
Development

Successfully merging this pull request may close these issues.

5 participants