-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add release workflow #13
Conversation
tags: | ||
- v[0-9]+.[0-9]+.[0-9]+ | ||
branches: | ||
- main |
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.
This workflow will release tagged and SNAPSHOT versions
build.gradle
Outdated
@@ -8,7 +8,7 @@ subprojects { | |||
} | |||
|
|||
group = "com.scalar-labs" | |||
project.version = project.findProperty('projVersion') ?: '1.0.0-SNAPSHOT' | |||
project.version = project.findProperty('projVersion') ?: '1.1.0-SNAPSHOT' |
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.
Since we are ready for 1.0.0, I rename the SNAPSHOT version to 1.1.0.
I would use the rolling release where features and bugfix are managed in the main branch only. There will be no branches to manage minor versions. This is the reason why the SNAPSHOT version in the main branch is not 2.0.0-SNAPSHOT
.
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.
I think we should stick to the same model as the other products like ScalarDB and ScalarDL (i.e., the main branch points to the next major release); otherwise, it's too confusing for developers and users working on both projects.
Does it make things difficult?
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.
I see.
For me, either {next major}.0.0-SNAPSHOT
or 1.{next minor}.0
is reasonable as long as we clearly define the next
is about major or minor.
Using {next major}.0.0-SNAPSHOT
has a benefit of consistency so it's not difficult to me as well.
I changed the versioning in f8c8575
lib/archive.gradle
Outdated
name = 'Scalar Admin for Kubernetes' | ||
description = 'This library provides a fault-tolerant manner to pause Scalar products in Kubernetes environments and ensure the data is transactionally consistent.' |
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.
Please help revise the name and the description.
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.
Could you tell me why you want to publish this to the Maven repository as a library? As far as I understand, this is a CLI application. If so, it's not necessary to publish it to the Maven.
@choplin In the original design, we made scalar-admin-k8s able to be integrated, for example, the Scalar Manager can use this library to pause the products in a Kubernetes cluster. The CLI is mainly for the place that could not use Java library, for example, the CronJob or the non-Java application. |
@@ -83,7 +83,8 @@ done | |||
# This is normally unused |
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.
This file is changed because my local Gradle was upgraded to 8.3 and I regenerate the Gradle wrapper to upgrade the wrapper from 7.6.2 to 8.1.1. Can ignore this diff.
@@ -2,5 +2,6 @@ distributionBase=GRADLE_USER_HOME | |||
distributionPath=wrapper/dists |
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.
This file is changed because my local Gradle was upgraded to 8.3 and I regenerate the Gradle wrapper to upgrade the wrapper from 7.6.2 to 8.1.1. Can ignore this diff.
Thank you for your explanation. Based on that, I'd recommend separating the project into sub-projects of |
@choplin |
Ah, sorry for that. I misunderstood. Thank you for pointing it out. |
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!
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! Thank you!
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.
Left some suggestions. PTAL!
build.gradle
Outdated
@@ -8,7 +8,7 @@ subprojects { | |||
} | |||
|
|||
group = "com.scalar-labs" | |||
project.version = project.findProperty('projVersion') ?: '1.0.0-SNAPSHOT' | |||
project.version = project.findProperty('projVersion') ?: '1.1.0-SNAPSHOT' |
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.
I think we should stick to the same model as the other products like ScalarDB and ScalarDL (i.e., the main branch points to the next major release); otherwise, it's too confusing for developers and users working on both projects.
Does it make things difficult?
Co-authored-by: Hiroyuki Yamada <[email protected]>
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.
Sorry for my late review...
Overall looks good to me, but I left one question.
Please take a look when you have time!
Co-authored-by: kota2and3kan <[email protected]>
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! Thank you!
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! Thank you!
This PR adds a new workflow to release Java package and Docker image.