Change workflows for branching 3.2.x

This commit is contained in:
Janne Valkealahti
2022-05-05 14:29:25 +01:00
parent 91edc8be8e
commit 6fc2b0070e
14 changed files with 15 additions and 233 deletions

View File

@@ -37,7 +37,7 @@ jobs:
--server-id-deploy=repo.spring.io \
--repo-resolve=libs-release \
--repo-deploy=libs-staging-local
echo JFROG_CLI_BUILD_NAME=spring-statemachine-main-release >> $GITHUB_ENV
echo JFROG_CLI_BUILD_NAME=spring-statemachine-32x-release >> $GITHUB_ENV
echo JFROG_CLI_BUILD_NUMBER=$GITHUB_RUN_NUMBER >> $GITHUB_ENV
# switch from snapshot to a release version and extract project
# version to get used with tagging
@@ -90,7 +90,7 @@ jobs:
--server-id-deploy=repo.spring.io \
--repo-resolve=libs-release \
--repo-deploy=libs-staging-local
echo JFROG_CLI_BUILD_NAME=spring-statemachine-main-release >> $GITHUB_ENV
echo JFROG_CLI_BUILD_NAME=spring-statemachine-32x-release >> $GITHUB_ENV
echo JFROG_CLI_BUILD_NUMBER=$GITHUB_RUN_NUMBER >> $GITHUB_ENV
# promoting build from staging repo into release
- name: Promote Build
@@ -102,7 +102,7 @@ jobs:
jfrog rt gradle nextVersion
- uses: jvalkeal/build-zoo-handler@v0.0.4
with:
commit-changes-branch: main
commit-changes-branch: 3.2.x
commit-changes-message: Next development version
# gh release before central
@@ -174,7 +174,7 @@ jobs:
# prepare env for cli do download released files
- name: Configure JFrog Cli
run: |
echo JFROG_CLI_BUILD_NAME=spring-statemachine-main-release >> $GITHUB_ENV
echo JFROG_CLI_BUILD_NAME=spring-statemachine-32x-release >> $GITHUB_ENV
echo JFROG_CLI_BUILD_NUMBER=$GITHUB_RUN_NUMBER >> $GITHUB_ENV
# download released files for a build.
# spec file defines files we actually need for central