Update workflows with Gradle Enterprise credentials

Only workflows that do not build PRs have been configured with
credentials.
This commit is contained in:
Eric Haag
2023-07-27 16:28:24 -05:00
committed by Janne Valkealahti
parent 8194d8da45
commit 33d68e7878
4 changed files with 32 additions and 1 deletions

View File

@@ -49,6 +49,10 @@ jobs:
run: |
jf gradle milestoneVersion -PstatemachineMilestone=${{ github.event.inputs.milestone }}
echo PROJECT_VERSION=$(cat gradle.properties | grep "version=" | awk -F'=' '{print $2}') >> $GITHUB_ENV
env:
GRADLE_ENTERPRISE_CACHE_USERNAME: ${{ secrets.GRADLE_ENTERPRISE_CACHE_USER }}
GRADLE_ENTERPRISE_CACHE_PASSWORD: ${{ secrets.GRADLE_ENTERPRISE_CACHE_PASSWORD }}
GRADLE_ENTERPRISE_ACCESS_KEY: ${{ secrets.GRADLE_ENTERPRISE_SECRET_ACCESS_KEY }}
# build and publish to staging repo.
# we've allready tested with snapshots so no need to test
# with a release build as we are not a release train.
@@ -56,6 +60,10 @@ jobs:
run: |
jf gradle clean build artifactoryPublish
jf rt build-publish
env:
GRADLE_ENTERPRISE_CACHE_USERNAME: ${{ secrets.GRADLE_ENTERPRISE_CACHE_USER }}
GRADLE_ENTERPRISE_CACHE_PASSWORD: ${{ secrets.GRADLE_ENTERPRISE_CACHE_PASSWORD }}
GRADLE_ENTERPRISE_ACCESS_KEY: ${{ secrets.GRADLE_ENTERPRISE_SECRET_ACCESS_KEY }}
# we've now done a release build, branch and tag it in github
- name: Tag Release
uses: jvalkeal/build-zoo-handler@v0.0.4