Skip to content

Commit

Permalink
[CI] Update jfrog cli to v3
Browse files Browse the repository at this point in the history
Update setup-jfrog-cli to use `JF_ENV_SPRING` instead of `JF_ARTIFACTORY_SPRING`
Added `JF_URL`
Added reference to `${{ vars.JF_SERVER_ID }}` in place of `repo.spring.io`
Remove maven setup and add --use-wrapper
  • Loading branch information
corneil committed Nov 20, 2024
1 parent 7d895e7 commit b459008
Show file tree
Hide file tree
Showing 4 changed files with 1 addition and 13 deletions.
5 changes: 1 addition & 4 deletions .github/workflows/ci-pr.yml
Original file line number Diff line number Diff line change
Expand Up @@ -20,13 +20,10 @@ jobs:
with:
java-version: 1.8
# maven version
- uses: jvalkeal/setup-maven@v1
with:
maven-version: 3.6.2
# build
- name: Build
run: |
mvn -U -B clean package
./mvnw -U -B clean package
# clean m2 cache
- name: Clean cache
run: |
Expand Down
3 changes: 0 additions & 3 deletions .github/workflows/milestone-worker.yml
Original file line number Diff line number Diff line change
Expand Up @@ -16,9 +16,6 @@ jobs:
- uses: actions/setup-java@v1
with:
java-version: 1.8
- uses: jvalkeal/setup-maven@v1
with:
maven-version: 3.6.3
- uses: jfrog/setup-jfrog-cli@v3
env:
JF_URL: 'https://repo.spring.io'
Expand Down
3 changes: 0 additions & 3 deletions .github/workflows/next-dev-version-worker.yml
Original file line number Diff line number Diff line change
Expand Up @@ -16,9 +16,6 @@ jobs:
- uses: actions/setup-java@v1
with:
java-version: 1.8
- uses: jvalkeal/setup-maven@v1
with:
maven-version: 3.6.3
- uses: jfrog/setup-jfrog-cli@v3
env:
JF_URL: 'https://repo.spring.io'
Expand Down
3 changes: 0 additions & 3 deletions .github/workflows/release-worker.yml
Original file line number Diff line number Diff line change
Expand Up @@ -16,9 +16,6 @@ jobs:
- uses: actions/setup-java@v1
with:
java-version: 1.8
- uses: jvalkeal/setup-maven@v1
with:
maven-version: 3.6.3
- uses: jfrog/setup-jfrog-cli@v3
env:
JF_URL: 'https://repo.spring.io'
Expand Down

0 comments on commit b459008

Please sign in to comment.