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.

Sign up for GitHub

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

Jump to bottom

Fix release path on s3 #3598

Closed
exalate-issue-sync bot opened this issue May 22, 2023 · 2 comments
Closed

Fix release path on s3 #3598

exalate-issue-sync bot opened this issue May 22, 2023 · 2 comments
Assignees
@jakubhava
Labels
fixVersion/3.28.1.2-1

Comments

@exalate-issue-sync
Copy link

Due to some recent changes, the release path of artifacts has changed.

release dist, let's say for 2.4 should be uploaded to h2o-releases/sparkling-water/spark-2.4/3.28.1.1-2.4 directly, but right now it is uploaded to h2o-releases/sparkling-water/spark-2.4/rel-3.28.1/3.28.1.1-2.4.

It adds extra branch name. The problem will be in utils.gradle where we define the path (path task)
@DinukaH2O
Copy link

JIRA Issue Migration Info

Jira Issue: SW-2063
Assignee: Jakub Hava
Reporter: Jakub Hava
State: Resolved
Fix Version: 3.28.1.2-1
Attachments: N/A
Development PRs: Available

Linked PRs from JIRA

#1937

@hasithjp
Copy link
Member

JIRA Issue Migration Info Cont'd

Jira Issue Created Date: 2020-03-06T03:39:08.625-0800

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jakubhava jakubhava

Labels
fixVersion/3.28.1.2-1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jakubhava @hasithjp @DinukaH2O