This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 36
Change release workflow to use new staging bucket for artifacts #358
Merged
gaiksaya
merged 6 commits into
opendistro-for-elasticsearch:master
from
gaiksaya:release-workflow-patch
Feb 1, 2021
Merged
Change release workflow to use new staging bucket for artifacts #358
gaiksaya
merged 6 commits into
opendistro-for-elasticsearch:master
from
gaiksaya:release-workflow-patch
Feb 1, 2021
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
Codecov Report
@@ Coverage Diff @@
## master #358 +/- ##
============================================
+ Coverage 78.65% 78.69% +0.03%
+ Complexity 2465 2462 -3
============================================
Files 224 224
Lines 10995 10995
Branches 943 943
============================================
+ Hits 8648 8652 +4
+ Misses 1907 1902 -5
- Partials 440 441 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Are you using the latest mater branch? The build has tests failure. |
gaiksaya
force-pushed
the
release-workflow-patch
branch
from
January 11, 2021 22:16
03cb8f3
to
7bc0065
Compare
Hi @kaituo , I updated my branch and fork with recent master. Tests seems to be passing now. Thanks! |
kaituo
approved these changes
Jan 13, 2021
ylwu-amzn
approved these changes
Jan 25, 2021
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks for the change!
gaiksaya
changed the title
[WIP] Change release workflow to use new staging bucket for artifacts
Change release workflow to use new staging bucket for artifacts
Feb 1, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Issue #, if available:
Description of changes:
The infrastructure team is separating the production and staging locations into different AWS accounts. Plugins need to modify their workflows to publish to the new locations.
This PR changes the CD workflow to add a build number and write the zip, deb, and rpm plugin artifacts to staging.artifacts.opendistroforelasticsearch.amazon.com.
Test Results:
https://github.com/gaiksaya/anomaly-detection/runs/1684584738?check_suite_focus=true
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.