-
Notifications
You must be signed in to change notification settings - Fork 277
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
Promote min and bundle artifacts to release-candidate after every bundle build #1378
Promote min and bundle artifacts to release-candidate after every bundle build #1378
Conversation
Signed-off-by: Yilin Zhang <yilizhan@amazon.com>
Codecov Report
@@ Coverage Diff @@
## main #1378 +/- ##
============================================
- Coverage 94.45% 94.38% -0.07%
Complexity 11 11
============================================
Files 140 140
Lines 3085 3101 +16
Branches 10 10
============================================
+ Hits 2914 2927 +13
- Misses 164 167 +3
Partials 7 7
Continue to review full report at Codecov.
|
Please make sure that the new output will handle these cases:
I think we've got the first case, but we need the snapshot ones too |
src/jenkins/BuildManifest.groovy
Outdated
public String getPackageName(String productName) { | ||
String packagePrefix = [ | ||
productName, | ||
this.build.version, | ||
this.build.platform, | ||
this.build.architecture, | ||
].join('/') | ||
return packagePrefix + '.tar.gz' | ||
} |
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.
Can we use the name with version, platform, architecture and distribution from here?
Can we try to move this forward, please? |
Signed-off-by: Yilin Zhang <yilizhan@amazon.com>
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.
Add tests for the new functions at least, please.
…oduct name from manifest Signed-off-by: Yilin Zhang <yilizhan@amazon.com>
@zylzulu will review when the build is green and the CR is ready |
Signed-off-by: Yilin Zhang <yilizhan@amazon.com>
… into artifacts_snapshot_publish
Signed-off-by: Sayali Gaikawad <gaiksaya@amazon.com>
Hi @peternied , @dblock, |
Check out https://github.com/opensearch-project/opensearch-build/blob/main/jenkins/opensearch/distribution-build.jenkinsfile#L50, which calls publish-snapshot to Maven. You'll probably want to publish around there. |
Looking at the above code: Should we directly upload from here (jenkins local) to snapshots (prod) s3? Also what about arm64? While I executed the jenkinfile to see the generated artifacts, I did not see anything generated for arm64 here.
|
@gaiksaya I think it's perfectly OK to do the snapshot uploading as part of another PR, and we can discuss options there; (2) seems like the better thing to do |
Signed-off-by: Sayali Gaikawad <gaiksaya@amazon.com>
Signed-off-by: Sayali Gaikawad <gaiksaya@amazon.com>
Signed-off-by: Sayali Gaikawad <gaiksaya@amazon.com>
…dle build (opensearch-project#1378) * Promote to release candidate after every bundle build Signed-off-by: Yilin Zhang <yilizhan@amazon.com> Signed-off-by: Sayali Gaikawad <gaiksaya@amazon.com> Co-authored-by: Sayali Gaikawad <gaiksaya@amazon.com>
Signed-off-by: Yilin Zhang yilizhan@amazon.com
Description
Uploads min and bundle artifacts for both opensearch and dashboards to the below location on every build:
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.