Skip to content

Commit 71a147c

Browse files
asafcjfrogasafcjfrog
authored
Update frogbot-config.yml
1 parent bf221fd commit 71a147c

File tree

1 file changed

+5
-112
lines changed

1 file changed

+5
-112
lines changed

‎jfrog-applications/frogbot/templates/.frogbot/frogbot-config.yml

+5-112
Original file line numberDiff line numberDiff line change
@@ -1,113 +1,6 @@
1-
# The "params" section includes the configuration of a single Git repository that needs to be scanned.
2-
# For Azure Repos, Bitbucket Server and GitHub with JFrog Pipelines or Jenkins, you can define multiple "params" sections one after the other, for scanning multiple
3-
# Git repositories in the same organization.
4-
- params:
5-
# Git parameters
6-
git:
7-
# [Mandatory]
8-
# Name of the git repository to scan
9-
repoName: repo-name
1+
**The JFrog Security documentation has a new home!**\
2+
You can now find it [here](https://jfrog.com/help/p/security-home), including sections on:
103

11-
# [Mandatory]
12-
# List of branches to scan
13-
branches:
14-
- master
15-
16-
# [Optional]
17-
# Template for the branch name generated by Frogbot when creating pull requests with fixes.
18-
# The template must include ${BRANCH_NAME_HASH}, to ensure that the generated branch name is unique.
19-
# The template can optionally include the ${IMPACTED_PACKAGE} and ${FIX_VERSION} variables.
20-
# branchNameTemplate: "frogbot-${IMPACTED_PACKAGE}-${BRANCH_NAME_HASH}"
21-
22-
# [Optional]
23-
# Template for the commit message generated by Frogbot when creating pull requests with fixes
24-
# The template can optionally include the ${IMPACTED_PACKAGE} and ${FIX_VERSION} variables.
25-
# commitMessageTemplate: "Upgrade ${IMPACTED_PACKAGE} to ${FIX_VERSION}"
26-
27-
# [Optional]
28-
# Template for the pull request title generated by Frogbot when creating pull requests with fixes.
29-
# The template can optionally include the ${IMPACTED_PACKAGE} and ${FIX_VERSION} variables.
30-
# pullRequestTitleTemplate: "[🐸 Frogbot] Upgrade ${IMPACTED_PACKAGE} to ${FIX_VERSION}"
31-
32-
# [Optional, Default: false]
33-
# If true, Frogbot creates a single pull request with all the fixes.
34-
# If false, Frogbot creates a separate pull request for each fix.
35-
# aggregateFixes: false
36-
37-
# [Optional, Default: eco-system+frogbot@jfrog.com]
38-
# Set the email of the commit author
39-
# emailAuthor: ""
40-
41-
# Frogbot scanning parameters
42-
scan:
43-
# [Default: false]
44-
# Frogbot displays all existing vulnerabilities, including the ones that were not added by the pull request
45-
# includeAllVulnerabilities: true
46-
47-
# [Default: false]
48-
# When adding new comments on pull requests, keep old comments that were added by previous scans.
49-
# avoidPreviousPrCommentsDeletion: true
50-
51-
# [Default: true]
52-
# Frogbot does not fail the task if security issues are found and this parameter is set to false
53-
# failOnSecurityIssues: false
54-
55-
# [Default: false]
56-
# Handle vulnerabilities with fix versions only
57-
# fixableOnly: true
58-
59-
# [Optional]
60-
# Set the minimum severity for vulnerabilities that should be fixed and commented on in pull requests
61-
# The following values are accepted: Low, Medium, High or Critical
62-
# minSeverity: ""
63-
64-
# [Optional]
65-
# List of email addresses to receive emails about secrets that has been detected in a pull request scan.
66-
# Applies only to servers that are entitled to JFrog Advanced Security.
67-
# emailReceivers:
68-
# - user@company.com
69-
70-
# List of subprojects / project dirs inside the Git repository
71-
projects:
72-
# [Mandatory if the two conditions below are met]
73-
# 1. The project uses yarn 2, NuGet or .NET Core to download its dependencies
74-
# 2. The `installCommand` variable isn't set in your frogbot-config.yml file.
75-
#
76-
# The command that installs the project dependencies (e.g "nuget restore")
77-
# - installCommand: ""
78-
79-
# [Default: root directory]
80-
# List of relative path's to the projects directories in the git repository. If left empty (without providing "." yourself as the root directory's path), a recursive scan is triggered from the root directory of the project.
81-
# workingDirs:
82-
# - "."
83-
84-
# [Default: ["*.git*", "*node_modules*", "*target*", "*venv*", "*test*"]]
85-
# List of exclusion patterns (utilizing wildcards) for excluding paths in the source code of the Git repository during SCA scans.
86-
# pathExclusions:
87-
# - "*node_modules*"
88-
# - "*target*"
89-
# - "*venv*"
90-
# - "*test*"
91-
92-
# [Mandatory for pip only if using requirements file, Default: pip install .]
93-
# The requirements file name that is used to install dependencies in case of pip package manager
94-
# pipRequirementsFile: ""
95-
96-
# [Default: true]
97-
# Use Gradle Wrapper (gradlew/gradlew.bat) to run Gradle
98-
# useWrapper: true
99-
100-
# [Optional]
101-
# Name of a Virtual Repository in Artifactory to resolve (download) the project dependencies from
102-
# repository: ""
103-
104-
# JFrog Platform parameters
105-
jfrogPlatform:
106-
# [Optional]
107-
# JFrog project key. Learn more about it [here](https://www.jfrog.com/confluence/display/JFROG/Projects)
108-
# jfrogProjectKey: ""
109-
110-
# [Optional]
111-
# Xray Watches. Learn more about it [here](https://www.jfrog.com/confluence/display/JFROG/Configuring+Xray+Watches)
112-
# watches:
113-
# - ""
4+
* [CLI](https://jfrog.com/help/r/jfrog-security-user-guide/developers/cli)
5+
* [Frogbot](https://jfrog.com/help/r/jfrog-security-user-guide/developers/frogbot)
6+
* [IDEs](https://jfrog.com/help/r/jfrog-security-user-guide/developers/ides)

0 commit comments

Comments
 (0)