Github Action - Create Release and Deploy#312
Conversation
JaCoCo code coverage report - Scala 2.11 & Spark 2
|
JaCoCo code coverage report - Scala 2.12 & Spark 2
|
JaCoCo code coverage report - Scala 2.12 & Spark 3
|
.github/workflows/deploy.yml
Outdated
| on: | ||
| workflow_dispatch: | ||
| inputs: | ||
| tag-name: |
There was a problem hiding this comment.
You probably don't need that. You can just select the tag from the dropdown
Then you don't need to validate the input
| description: "Define the release version (e.g., v4.7.0)" | ||
| required: true | ||
| default: "" | ||
| development-version: |
There was a problem hiding this comment.
You can use this to determine the next development version from the release version.
# Assumes semantic versioning and increments the minor version. Adjust the awk command as needed for different versioning schemes.
NEXT_VERSION=$(echo ${VERSION} | awk -F. '{print $1"."$2+1".0-SNAPSHOT"}')
There was a problem hiding this comment.
I like current version, you set what is the release version and what is the development version. Above assumes that we always increment the same digit all the time. But I will remove comment because that is incorrect
There was a problem hiding this comment.
I'm not going to argue about such a thing, but in that case you need to make sure that the development version will end with -SNAPSHOT
There was a problem hiding this comment.
It appends it there
NEXT_VERSION=$(echo ${DEVELOPMENT_VERSION_WITHOUT_V} | awk -F. '{print $1"."$2"."$3"-SNAPSHOT"}')
.github/workflows/deploy.yml
Outdated
| } | ||
| tag-name: ${{ github.event.inputs.tag-name }} | ||
|
|
||
| - name: Define semantic version number |
There was a problem hiding this comment.
Isn't this step unneeded?
2 participants
No description provided.