mirror of
https://github.com/spring-projects/spring-petclinic.git
synced 2025-04-24 19:32:48 +00:00
frogbot
This commit is contained in:
parent
4b3444bc60
commit
4a7a691821
2 changed files with 92 additions and 0 deletions
42
.github/workflows/frogbot-scan-pull-request.yml
vendored
Normal file
42
.github/workflows/frogbot-scan-pull-request.yml
vendored
Normal file
|
@ -0,0 +1,42 @@
|
|||
name: "Frogbot Scan Pull Request"
|
||||
on:
|
||||
pull_request_target:
|
||||
types: [opened, synchronize]
|
||||
permissions:
|
||||
pull-requests: write
|
||||
contents: read
|
||||
# [Mandatory If using OIDC authentication protocol instead of JF_ACCESS_TOKEN]
|
||||
# id-token: write
|
||||
jobs:
|
||||
scan-pull-request:
|
||||
runs-on: ubuntu-latest
|
||||
# A pull request needs to be approved before Frogbot scans it. Any GitHub user who is associated with the
|
||||
# "frogbot" GitHub environment can approve the pull request to be scanned.
|
||||
environment: frogbot
|
||||
steps:
|
||||
- uses: jfrog/frogbot@v2
|
||||
env:
|
||||
# [Mandatory]
|
||||
# JFrog platform URL
|
||||
JF_URL: ${{ secrets.JF_URL }}
|
||||
|
||||
# [Mandatory if JF_USER and JF_PASSWORD are not provided]
|
||||
# JFrog access token with 'read' permissions on Xray service
|
||||
JF_ACCESS_TOKEN: ${{ secrets.JF_ACCESS_TOKEN }}
|
||||
|
||||
# [Mandatory if JF_ACCESS_TOKEN is not provided]
|
||||
# JFrog username with 'read' permissions for Xray. Must be provided with JF_PASSWORD
|
||||
# JF_USER: ${{ secrets.JF_USER }}
|
||||
|
||||
# [Mandatory if JF_ACCESS_TOKEN is not provided]
|
||||
# JFrog password. Must be provided with JF_USER
|
||||
# JF_PASSWORD: ${{ secrets.JF_PASSWORD }}
|
||||
|
||||
# [Mandatory]
|
||||
# The GitHub token is automatically generated for the job
|
||||
JF_GIT_TOKEN: ${{ secrets.JF_GIT_TOKEN }}
|
||||
|
||||
# [Mandatory if using OIDC authentication protocol instead of JF_ACCESS_TOKEN]
|
||||
# Insert to oidc-provider-name the 'Provider Name' defined in the OIDC integration configured in the JPD
|
||||
# with:
|
||||
# oidc-provider-name: ""
|
50
.github/workflows/frogbot-scan-repository.yml
vendored
Normal file
50
.github/workflows/frogbot-scan-repository.yml
vendored
Normal file
|
@ -0,0 +1,50 @@
|
|||
name: "Frogbot Scan Repository"
|
||||
on:
|
||||
workflow_dispatch:
|
||||
schedule:
|
||||
# The repository will be scanned once a day at 00:00 GMT.
|
||||
- cron: "0 0 * * *"
|
||||
permissions:
|
||||
contents: write
|
||||
pull-requests: write
|
||||
security-events: write
|
||||
# [Mandatory If using OIDC authentication protocol instead of JF_ACCESS_TOKEN]
|
||||
# id-token: write
|
||||
jobs:
|
||||
scan-repository:
|
||||
runs-on: ubuntu-latest
|
||||
strategy:
|
||||
matrix:
|
||||
# The repository scanning will be triggered periodically on the following branches.
|
||||
branch: ["dev"]
|
||||
steps:
|
||||
- uses: jfrog/frogbot@v2
|
||||
env:
|
||||
# [Mandatory]
|
||||
# JFrog platform URL
|
||||
JF_URL: ${{ secrets.JF_URL }}
|
||||
|
||||
# [Mandatory if JF_USER and JF_PASSWORD are not provided]
|
||||
# JFrog access token with 'read' permissions on Xray service
|
||||
JF_ACCESS_TOKEN: ${{ secrets.JF_ACCESS_TOKEN }}
|
||||
|
||||
# [Mandatory if JF_ACCESS_TOKEN is not provided]
|
||||
# JFrog username with 'read' permissions for Xray. Must be provided with JF_PASSWORD
|
||||
# JF_USER: ${{ secrets.JF_USER }}
|
||||
|
||||
# [Mandatory if JF_ACCESS_TOKEN is not provided]
|
||||
# JFrog password. Must be provided with JF_USER
|
||||
# JF_PASSWORD: ${{ secrets.JF_PASSWORD }}
|
||||
|
||||
# [Mandatory]
|
||||
# The GitHub token is automatically generated for the job
|
||||
JF_GIT_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
||||
|
||||
# [Mandatory]
|
||||
# The name of the branch on which Frogbot will perform the scan
|
||||
JF_GIT_BASE_BRANCH: ${{ matrix.branch }}
|
||||
|
||||
# [Mandatory if using OIDC authentication protocol instead of JF_ACCESS_TOKEN]
|
||||
# Insert to oidc-provider-name the 'Provider Name' defined in the OIDC integration configured in the JPD
|
||||
# with:
|
||||
# oidc-provider-name: ""
|
Loading…
Reference in a new issue