Automation component release issue: Workflow update #3801
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
prudhvigodithi
requested review from
dblock,
peterzhuamazon,
bbarani,
gaiksaya,
rishabh6788,
zelinh,
jordarlu,
Divyaasm and
tianleh
as code owners
Codecov Report
@@ Coverage Diff @@
## main #3801 +/- ##
=======================================
Coverage 91.54% 91.54%
=======================================
Files 182 182
Lines 5420 5420
=======================================
Hits 4962 4962
Misses 458 458 |
jordarlu
approved these changes
Jul 20, 2023
Signed-off-by: Prudhvi Godithi <[email protected]>
|
Updated the PR keeping the |
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.
Description
Coming from main PR #3708
#3795
#3797
This PR address 2 scenarios:
Error: https://github.com/opensearch-project/opensearch-build/actions/runs/5591220878/jobs/10222005342#step:8:12
This could be a race condition (where issue creation and add label are invoked at same time) or the permission issue, so removing temporarily adding of release label to the created release issue
issue-state: 'open'as I have noticed sometimes a component release issue is closed by a release manager while the global build repo release issue is still open, so having a checkissue-state: 'open'is forcing to create a new issue.Example for
2.9.0release the global build repo release issue is still open [RELEASE] Release version 2.9.0 #3616 the asynchronous-search component repo release issue is closed [RELEASE] Release version 2.9.0 asynchronous-search#299 but withissue-state: 'open'it recreated a new one [RELEASE] Release version 2.9.0 asynchronous-search#319 not honoring the issue that was closed.Issues Resolved
Part of:
#3349
#3676
opensearch-project/.github#167
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.