Skip to content

Overview

A quick example:

node {
    sh 'echo hello world'
}

You can write any Groovy code you need, using Java API calls plus the GDK. You can also call Jenkins APIs and APIs in Jenkins plugins. (If Use Groovy Sandbox is checked, or you are not an administrator, not all APIs will be available.)

There are many special build steps available, like node and sh in the example. Below is a reference listing all steps available with your current set of plugins; other plugins offering Pipeline integration may be available on the update center.

Step parameters are given as key-value pairs; if there is just one mandatory parameter the name may be omitted, so

readFile 'build.properties'

is a shortcut for

readFile file: 'build.properties'

but if you specify multiple parameters they must all be named:

readFile file: 'build.properties', encoding: 'ISO-8859-1'

Many steps require complex nested configuration for a parameter. (And some nested configuration objects in turn have object-typed parameters.) There are three ways these nested objects may be specified, in decreasing order of preference:

  1. Some configuration objects define custom symbols. These are used with a notation looking like a step call, or other function call taking a map of named parameters:

    splitTests count(3)

    or to spell out the mandatory parameter names:

    splitTests parallelism: count(size: 3)

    Compare to the equivalent using the older second syntax option:

    splitTests parallelism: [$class: 'CountDrivenParallelism', size: 3]

    Some Pipeline steps delegating to a single object allow the actual step name to be omitted where unambiguous, so you can write simply:

    archiveArtifacts '**.txt'

    rather than:

    step([$class: 'ArtifactArchiver', artifacts: '**.txt'])

    The nested configuration is an actual value which can be saved into variables etc.:

    def parallelism(deterministic) {
        deterministic ? count(3) : time(15)
    }
    splitTests parallelism(true)
  2. As maps of parameters. Default values may be omitted. (Note that [1, 2, 3] is a list in Groovy whereas [a: 1, b: 2, c: 3] is a map.)

    The special map key $class is used to represent the simple or (where necessary) fully-qualified class name of the object being requested. $class may be omitted where the containing parameter allows only a single kind of nested object (or list of them):

    checkout([$class: 'GitSCM', userRemoteConfigs: [[url: 'git://…'], extensions: [[$class: 'CleanBeforeCheckout']]])

    In this example, GitSCM must be specified to distinguish the kind of SCM used by the delegate of checkout (the single mandatory parameter name delegate can be omitted), and CleanBeforeCheckout must be specified to distinguish the kind of GitSCMExtension used by the extensions of GitSCM—a “heterogeneous” list; but $class: 'UserRemoteConfig' may be omitted since the userRemoteConfigs of GitSCM are defined to contain only UserRemoteConfigs—it is a “homogeneous” list. (No such omission is permitted for homogeneous lists in the first syntax.)

    Note that in cases where a single parameter is given, with the name omitted, and that parameter is a map, it must be enclosed in parentheses to avoid a syntactic ambiguity.

  3. As actual Java objects:

    import hudson.plugins.git.*
    import hudson.plugins.git.extensions.impl.*
    checkout(new GitSCM([new UserRemoteConfig('git://…', null, null, null)], null, false, [], null, null, [new CleanBeforeCheckout()]))

    Besides the verbosity, such scripts cannot generally run in the Groovy sandbox without numerous signature approvals, making this mode unusable in typical secured Jenkins installations.

The Snippet Generator tool will produce the first syntax when possible, falling back to the second syntax using $class where necessary. Symbols are available in Jenkins core 2.2 and later, and some plugins.

DSL Reference

Steps

acceptGitLabMR: Accept GitLab Merge Request
mergeCommitMessage (optional)
Type:String
removeSourceBranch (optional)
Type:boolean
useMRDescription (optional)
Type:boolean
addGitLabMRComment: Add comment on GitLab Merge Request
comment (optional)
Type:String
archiveArtifacts: Archive the artifacts
Archives the build artifacts (for example, distribution zip files or jar files) so that they can be downloaded later. Archived files will be accessible from the Jenkins webpage.
Normally, Jenkins keeps artifacts for a build as long as a build log itself is kept, but if you don't need old artifacts and would rather save disk space, you can do so.

Note that the Maven job type automatically archives any produced Maven artifacts. Any artifacts configured here will be archived on top of that. Automatic artifact archiving can be disabled under the advanced Maven options.

The Pipeline Snippet Generator generates this example when all arguments are set to true (some arguments by default are true):
archiveArtifacts artifacts: '**/*.txt',
                   allowEmptyArchive: true,
                   fingerprint: true,
                   onlyIfSuccessful: true

artifacts
You can use wildcards like 'module/dist/**/*.zip'. See the includes attribute of Ant fileset for the exact format -- except that "," ( comma ) is the only supported separator. The base directory is the workspace . You can only archive files that are located in your workspace.

Here are some examples of usage for pipeline:

  • How to archive multiple artifacts from a specific folder:
    archiveArtifacts artifacts: 'target/*.jar'

  • How to archive multiple artifacts with different patterns:
    archiveArtifacts artifacts: 'target/*.jar, target/*.war'

  • How to archive multiple nested artifacts:
    archiveArtifacts artifacts: '**/*.jar'

Type:String
allowEmptyArchive (optional)
Normally, a build fails if archiving returns zero artifacts. This option allows the archiving process to return nothing without failing the build. Instead, the build will simply throw a warning.
Type:boolean
caseSensitive (optional)
Artifact archiver uses Ant org.apache.tools.ant.DirectoryScanner which by default is case sensitive. For instance, if the job produces *.hpi files, pattern "**/*.HPI" will fail to find them.

This option can be used to disable case sensitivity. When it's unchecked, pattern "**/*.HPI" will match any *.hpi files, or pattern "**/cAsEsEnSiTiVe.jar" will match a file called caseSensitive.jar.
Type:boolean
defaultExcludes (optional)
Type:boolean
excludes (optional)
Optionally specify the 'excludes' pattern, such as "foo/bar/**/*". Use "," to set a list of patterns. A file that matches this mask will not be archived even if it matches the mask specified in 'files to archive' section.
Type:String
fingerprint (optional)
Type:boolean
followSymlinks (optional)
By disabling this option all symbolic links found in the workspace will be ignored.
Type:boolean
onlyIfSuccessful (optional)
Type:boolean
bat: Windows Batch Script
script
Executes a Batch script. Multiple lines allowed. When using the returnStdout flag, you probably wish to prefix this with @, lest the command itself be included in the output.
Type:String
encoding (optional)
Encoding of process output. In the case of returnStdout, applies to the return value of this step; otherwise, or always for standard error, controls how text is copied to the build log. If unspecified, uses the system default encoding of the node on which the step is run. If there is any expectation that process output might include non-ASCII characters, it is best to specify the encoding explicitly. For example, if you have specific knowledge that a given process is going to be producing UTF-8 yet will be running on a node with a different system encoding (typically Windows, since every Linux distribution has defaulted to UTF-8 for a long time), you can ensure correct output by specifying: encoding: 'UTF-8'
Type:String
label (optional)
Label to be displayed in the pipeline step view and blue ocean details for the step instead of the step type. So the view is more meaningful and domain specific instead of technical.
Type:String
returnStatus (optional)
Normally, a script which exits with a nonzero status code will cause the step to fail with an exception. If this option is checked, the return value of the step will instead be the status code. You may then compare it to zero, for example.
Type:boolean
returnStdout (optional)
If checked, standard output from the task is returned as the step value as a String, rather than being printed to the build log. (Standard error, if any, will still be printed to the log.) You will often want to call .trim() on the result to strip off a trailing newline.
Type:boolean
build: Build a job

Trigger a new build for a given job.

Use the Pipeline Snippet Generator to generate a sample pipeline script for the build step.

job
Name of a downstream job to build. May be another Pipeline job, but more commonly a freestyle or other project. Use a simple name if the job is in the same folder as this upstream Pipeline job; otherwise can use relative paths like ../sister-folder/downstream or absolute paths like /top-level-folder/nested-folder/downstream.
Type:String
parameters (optional)
A list of parameters to pass to the downstream job. When passing secrets to downstream jobs, prefer credentials parameters over password parameters. See the documentation for details.
Array/List:
Nested choice of objects
booleanParam
name
Type:String
value
Type:boolean
credentials
name
Type:String
value
Type:String
description
Type:String
file
name
Type:String
file
Nested choice of objects
gitParameter
name
Type:String
value
Type:String
password
name
Type:String
value
org.kohsuke.stapler.NoStaplerConstructorException: There's no @DataBoundConstructor on any constructor of class hudson.util.Secret
description
Type:String
$class: 'PromotedBuildParameterValue'
name
Type:String
runId
Type:String
description
Type:String
run
name
Type:String
runId
Type:String
description
Type:String
string
name
Type:String
value
Type:String
text
name
Type:String
value
Type:String
propagate (optional)

If enabled (default state), then the result of this step is that of the downstream build (e.g., success, unstable, failure, not built, or aborted). If disabled, then this step succeeds even if the downstream build is unstable, failed, etc.; use the result property of the return value as needed.

Type:boolean
quietPeriod (optional)
Optional alternate quiet period (in seconds) before building. If unset, defaults to the quiet period defined by the downstream project (or finally to the system-wide default quiet period).
Type:int
wait (optional)
If true, the pipeline will wait for the result of the build step before jumping to the next step. Defaults to true.
Type:boolean
waitForStart (optional)
If true, the pipeline will wait for the downstream build to start before jumping to the next step. Defaults to false. Overrides the value of wait.
Type:boolean
catchError: Catch error and set build result to failure
If the body throws an exception, mark the build as a failure, but nonetheless continue to execute the Pipeline from the statement following the catchError step. The behavior of the step when an exception is thrown can be configured to print a message, set a build result other than failure, change the stage result, or ignore certain kinds of exceptions that are used to interrupt the build.

This step is most useful when used in Declarative Pipeline or with the options to set the stage result or ignore build interruptions. Otherwise, consider using plain try-catch(-finally) blocks. It is also useful when using certain post-build actions (notifiers) originally defined for freestyle projects which pay attention to the result of the ongoing build.

node {
    catchError {
        sh 'might fail'
    }
    step([$class: 'Mailer', recipients: 'admin@somewhere'])
}

If the shell step fails, the Pipeline build’s status will be set to failed, so that the subsequent mail step will see that this build is failed. In the case of the mail sender, this means that it will send mail. (It may also send mail if this build succeeded but previous ones failed, and so on.) Even in that case, this step can be replaced by the following idiom:

node {
    try {
        sh 'might fail'
    } catch (err) {
        echo "Caught: ${err}"
        currentBuild.result = 'FAILURE'
    }
    step([$class: 'Mailer', recipients: 'admin@somewhere'])
}

For other cases, plain try-catch(-finally) blocks may be used:

node {
    sh './set-up.sh'
    try {
        sh 'might fail'
        echo 'Succeeded!'
    } catch (err) {
        echo "Failed: ${err}"
    } finally {
        sh './tear-down.sh'
    }
    echo 'Printed whether above succeeded or failed.'
}
// …and the pipeline as a whole succeeds

See this document for background.

buildResult (optional)
If an error is caught, the overall build result will be set to this value. Note that the build result can only get worse, so you cannot change the result to SUCCESS if the current result is UNSTABLE or worse. Use SUCCESS or null to keep the build result from being set when an error is caught.
Type:String
catchInterruptions (optional)
If true, certain types of exceptions that are used to interrupt the flow of execution for Pipelines will be caught and handled by the step. If false, those types of exceptions will be caught and immediately rethrown. Examples of these types of exceptions include those thrown when a build is manually aborted through the UI and those thrown by the timeout step. Defaults to true.
Type:boolean
message (optional)
A message that will be logged to the console if an error is caught. If the stage result is specified, the message will also be associated with that result and may be shown in visualizations.
Type:String
stageResult (optional)
If an error is caught, the stage result will be set to this value. If a message was specified, the message will be associated with this result. Use SUCCESS or null to keep the stage result from being set when an error is caught.
Type:String
checkout: Check out from version control
scm
Nested choice of objects
scmGit

The git plugin provides fundamental git operations for Jenkins projects. It can poll, fetch, checkout, and merge contents of git repositories.

The git plugin provides an SCM implementation to be used with the Pipeline SCM checkout step. The Pipeline Syntax Snippet Generator guides the user to select git plugin checkout options and provides online help for each of the options.

Use the Pipeline Snippet Generator to generate a sample pipeline script for the checkout step. Examples of the checkout step include:

See the argument descriptions for more details.

The checkout step provides access to all the Pipeline capabilities provided by the git plugin:

checkout scmGit(userRemoteConfigs: [
                    [ url: 'https://github.com/jenkinsci/git-plugin' ]
                ])


NOTE: The checkout step is the preferred SCM checkout method. For simpler cases that do not require all the capabilities of the git plugin, the git step can also be used.

Use the Pipeline Snippet Generator to generate a sample pipeline script for the checkout step.

The checkout step can be used in many cases where the git step cannot be used. Refer to the git plugin documentation for detailed descriptions of options available to the checkout step. For example, the checkout step supports:

  • SHA-1 checkout
  • Tag checkout
  • Submodule checkout
  • Sparse checkout
  • Large file checkout (LFS)
  • Reference repositories
  • Branch merges
  • Repository tagging
  • Custom refspecs
  • Timeout configuration
  • Changelog calculation against a non-default reference
  • Stale branch pruning


Example: Checkout step with defaults

Checkout from the git plugin source repository using https protocol, no credentials, and the master branch.

The Pipeline Snippet Generator generates this example:

checkout scmGit(userRemoteConfigs: [
                    [ url: 'https://github.com/jenkinsci/git-plugin' ]
                ])

Example: Checkout step with https and a specific branch

Checkout from the Jenkins source repository using https protocol, no credentials, and a specific branch (stable-2.289).

The Pipeline Snippet Generator generates this example:

checkout scmGit(branches: [[name: 'stable-2.289']],
                userRemoteConfigs: [
                    [ url: 'https://github.com/jenkinsci/jenkins.git' ]
                ])

Example: Checkout step with ssh and a private key credential

Checkout from the git client plugin source repository using ssh protocol, private key credentials, and the master branch. The credential must be a private key credential if the remote git repository is accessed with the ssh protocol. The credential must be a username / password credential if the remote git repository is accessed with http or https protocol.

The Pipeline Snippet Generator generates this example:

checkout changelog: false,
         scm: scmGit(userRemoteConfigs: [
                         [ credentialsId: 'my-private-key-credential-id',
                           url: 'git@github.com:jenkinsci/git-client-plugin.git' ]
                         ])

Example: Checkout step with https and changelog disabled

Checkout from the Jenkins source repository using https protocol, no credentials, the master branch, and changelog calculation disabled. If changelog is false, then the changelog will not be computed for this job. If changelog is true or is not set, then the changelog will be computed. See the workflow scm step documentation for more changelog details.

The Pipeline Snippet Generator generates this example:

checkout changelog: false,
         scmGit(userRemoteConfigs: [
                    [ url: 'https://github.com/jenkinsci/credentials-plugin' ]
                ])

Example: Checkout step with git protocol and polling disabled

Checkout from the command line git repository using git protocol, no credentials, the master branch, and no polling for changes. If poll is false, then the remote repository will not be polled for changes. If poll is true or is not set, then the remote repository will be polled for changes. See the workflow scm step documentation for more polling details.

The Pipeline Snippet Generator generates this example:

checkout poll: false,
         scmGit(userRemoteConfigs: [
                    [ url: 'git://git.kernel.org/pub/scm/git/git.git ]
                ])


Argument Descriptions
userRemoteConfigs
Specify the repository to track. This can be a URL or a local file path. Note that for super-projects (repositories with submodules), only a local file path or a complete URL is valid. The following are examples of valid git URLs.
  • ssh://git@github.com/github/git.git
  • git@github.com:github/git.git (short notation for ssh protocol)
  • ssh://user@other.host.com/~/repos/R.git (to access the repos/R.git repository in the user's home directory)
  • https://github.com/github/git.git

If the repository is a super-project, the location from which to clone submodules is dependent on whether the repository is bare or non-bare (i.e. has a working directory).
  • If the super-project is bare, the location of the submodules will be taken from .gitmodules.
  • If the super-project is not bare, it is assumed that the repository has each of its submodules cloned and checked out appropriately. Thus, the submodules will be taken directly from a path like ${SUPER_PROJECT_URL}/${SUBMODULE}, rather than relying on information from .gitmodules.
For a local URL/path to a super-project, git rev-parse --is-bare-repository is used to detect whether the super-project is bare or not.
For a remote URL to a super-project, the ending of the URL determines whether a bare or non-bare repository is assumed:
  • If the remote URL ends with .git, a non-bare repository is assumed.
  • If the remote URL does NOT end with .git, a bare repository is assumed.
Array/List:
Nested object
url
Specify the URL or path of the git repository. This uses the same syntax as your git clone command.
Type:String
name
ID of the repository, such as origin, to uniquely identify this repository among other remote repositories. This is the same "name" that you use in your git remote command. If left empty, Jenkins will generate unique names for you.

You normally want to specify this when you have multiple remote repositories.

Type:String
refspec
A refspec controls the remote refs to be retrieved and how they map to local refs. If left blank, it will default to the normal behaviour of git fetch, which retrieves all the branch heads as remotes/REPOSITORYNAME/BRANCHNAME. This default behaviour is OK for most cases.

In other words, the default refspec is "+refs/heads/*:refs/remotes/REPOSITORYNAME/*" where REPOSITORYNAME is the value you specify in the above "name of repository" textbox.

When do you want to modify this value? A good example is when you want to just retrieve one branch. For example, +refs/heads/master:refs/remotes/origin/master would only retrieve the master branch and nothing else.

The plugin uses a default refspec for its initial fetch, unless the "Advanced Clone Option" is set to honor refspec. This keeps compatibility with previous behavior, and allows the job definition to decide if the refspec should be honored on initial clone.

Multiple refspecs can be entered by separating them with a space character. +refs/heads/master:refs/remotes/origin/master +refs/heads/develop:refs/remotes/origin/develop retrieves the master branch and the develop branch and nothing else.

See the refspec definition in Git user manual for more details.

Type:String
credentialsId
Credential used to check out sources.
Type:String
branches
List of branches to build. Jenkins jobs are most effective when each job builds only a single branch. When a single job builds multiple branches, the changelog comparisons between branches often show no changes or incorrect changes.
Array/List:
Nested object
name

Specify the branches if you'd like to track a specific branch in a repository. If left blank, all branches will be examined for changes and built.

The safest way is to use the refs/heads/<branchName> syntax. This way the expected branch is unambiguous.

If your branch name has a / in it make sure to use the full reference above. When not presented with a full path the plugin will only use the part of the string right of the last slash. Meaning foo/bar will actually match bar.

If you use a wildcard branch specifier, with a slash (e.g. release/), you'll need to specify the origin repository in the branch names to make sure changes are picked up. So e.g. origin/release/

Possible options:

  • <branchName>
    Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily the expected one. Better use refs/heads/<branchName>.
    E.g. master, feature1, ...
  • refs/heads/<branchName>
    Tracks/checks out the specified branch.
    E.g. refs/heads/master, refs/heads/feature1/master, ...
  • <remoteRepoName>/<branchName>
    Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily the expected one.
    Better use refs/heads/<branchName>.
    E.g. origin/master
  • remotes/<remoteRepoName>/<branchName>
    Tracks/checks out the specified branch.
    E.g. remotes/origin/master
  • refs/remotes/<remoteRepoName>/<branchName>
    Tracks/checks out the specified branch.
    E.g. refs/remotes/origin/master
  • <tagName>
    This does not work since the tag will not be recognized as tag.
    Use refs/tags/<tagName> instead.
    E.g. git-2.3.0
  • refs/tags/<tagName>
    Tracks/checks out the specified tag.
    E.g. refs/tags/git-2.3.0
  • <commitId>
    Checks out the specified commit.
    E.g. 5062ac843f2b947733e6a3b105977056821bd352, 5062ac84, ...
  • ${ENV_VARIABLE}
    It is also possible to use environment variables. In this case the variables are evaluated and the result is used as described above.
    E.g. ${TREEISH}, refs/tags/${TAGNAME}, ...
  • <Wildcards>
    The syntax is of the form: REPOSITORYNAME/BRANCH. In addition, BRANCH is recognized as a shorthand of */BRANCH, '*' is recognized as a wildcard, and '**' is recognized as wildcard that includes the separator '/'. Therefore, origin/branches* would match origin/branches-foo but not origin/branches/foo, while origin/branches** would match both origin/branches-foo and origin/branches/foo.
  • :<regular expression>
    The syntax is of the form: :regexp. Regular expression syntax in branches to build will only build those branches whose names match the regular expression.
    Examples:
    • :^(?!(origin/prefix)).*
      • matches: origin or origin/master or origin/feature
      • does not match: origin/prefix or origin/prefix_123 or origin/prefix-abc
    • :origin/release-\d{8}
      • matches: origin/release-20150101
      • does not match: origin/release-2015010 or origin/release-201501011 or origin/release-20150101-something
    • :^(?!origin/master$|origin/develop$).*
      • matches: origin/branch1 or origin/branch-2 or origin/master123 or origin/develop-123
      • does not match: origin/master or origin/develop

Type:String
browser
Defines the repository browser that displays changes detected by the git plugin.
Nested choice of objects
assembla
repoUrl
Specify the root URL serving this repository (such as https://www.assembla.com/code/PROJECT/git/).
Type:String
bitbucketServer
repoUrl
Specify the Bitbucket Server root URL for this repository (such as https://bitbucket:7990/OWNER/REPO/).
Type:String
bitbucket
repoUrl
Specify the root URL serving this repository (such as https://bitbucket.org/OWNER/REPO/).
Type:String
cgit
repoUrl
Specify the root URL serving this repository (such as https://cgit.example.com:port/group/REPO/).
Type:String
fisheye
repoUrl
Specify the URL of this repository in FishEye (such as https://fisheye.example.com/browse/project/).
Type:String
gitblit
repoUrl
Specify the root URL serving this repository.
Type:String
projectName
Specify the name of the project in GitBlit.
Type:String
gitLab
repoUrl
Specify the root URL serving this repository (such as https://gitlab.com/username/repository/).
Type:String
version (optional)
Specify the major and minor version of GitLab you use (such as 9.1). If you don't specify a version, a modern version of GitLab (>= 8.0) is assumed.
Type:String
gitLabBrowser
Specify the HTTP URL for this project's GitLab page so that links to changes can be automatically generated by Jenkins. The URL needs to include the owner and project. If the GitLab server is https://gitLab.example.com then the URL for bob's skunkworks project might be https://gitLab.example.com/bob/skunkworks.
projectUrl
Specify the HTTP URL for this project's GitLab page. The URL needs to include the owner and project so, for example, if the GitLab server is https://gitLab.example.com then the URL for bob's skunkworks project might be https://gitLab.example.com/bob/skunkworks
Type:String
gitList
repoUrl
Specify the root URL serving this repository (such as https://gitlist.example.com/repo/).
Type:String
gitWeb
repoUrl
Specify the root URL serving this repository (such as https://github.com/jenkinsci/jenkins.git).
Type:String
github
repoUrl
Specify the HTTP URL for this repository's GitHub page (such as https://github.com/jquery/jquery).
Type:String
gitiles
repoUrl
Specify the root URL serving this repository (such as https://gwt.googlesource.com/gwt/).
Type:String
$class: 'GitoriousWeb'
repoUrl
Specify the root URL serving this repository (such as https://gitorious.org/gitorious/mainline).
Type:String
gogs
repoUrl
Specify the root URL serving this repository (such as https://gogs.example.com/username/some-repo-url.git).
Type:String
kiln
repoUrl
Specify the root URL serving this repository (such as https://khanacademy.kilnhg.com/Code/Website/Group/webapp).
Type:String
phabricator
repoUrl
Specify the phabricator instance root URL (such as https://phabricator.example.com).
Type:String
repo
Specify the repository name in phabricator (such as the foo part of phabricator.example.com/diffusion/foo/browse).
Type:String
redmine
repoUrl
Specify the root URL serving this repository (such as https://redmine.example.com/PATH/projects/PROJECT/repository).
Type:String
rhodeCode
repoUrl
Specify the HTTP URL for this repository's RhodeCode page (such as https://rhodecode.example.com/projects/PROJECT/repos/REPO/).
Type:String
$class: 'Stash'
repoUrl
Specify the HTTP URL for this repository's Stash page (such as https://stash.example.com/projects/PROJECT/repos/REPO/).
Type:String
teamFoundation
repoUrl
Either the name of the remote whose URL should be used, or the URL of this module in TFS (such as https://tfs.example.com/tfs/PROJECT/_git/REPO/). If empty (default), the URL of the "origin" repository is used.

If TFS is also used as the repository server, this can usually be left blank.

Type:String
viewgit
repoUrl
Specify the root URL serving this repository (such as https://git.example.com/viewgit/).
Type:String
projectName
Specify the name of the project in ViewGit (e.g. scripts, scuttle etc. from https://code.fealdia.org/viewgit/).
Type:String
gitTool

Name of the git tool to be used for this job. Git tool names are defined in "Global Tool Configuration".

Type:String
extensions

Extensions add new behavior or modify existing plugin behavior for different uses. Extensions help users more precisely tune plugin behavior to meet their needs.

Extensions include:

  • Clone extensions modify the git operations that retrieve remote changes into the agent workspace. The extensions can adjust the amount of history retrieved, how long the retrieval is allowed to run, and other retrieval details.
  • Checkout extensions modify the git operations that place files in the workspace from the git repository on the agent. The extensions can adjust the maximum duration of the checkout operation, the use and behavior of git submodules, the location of the workspace on the disc, and more.
  • Changelog extensions adapt the source code difference calculations for different cases.
  • Tagging extensions allow the plugin to apply tags in the current workspace.
  • Build initiation extensions control the conditions that start a build. They can ignore notifications of a change or force a deeper evaluation of the commits when polling.
  • Merge extensions can optionally merge changes from other branches into the current branch of the agent workspace. They control the source branch for the merge and the options applied to the merge.

Array/List:
Nested choice of objects
authorInChangelog
The default behavior is to use the Git commit's "Committer" value in Jenkins' build changesets. If this option is selected, the Git commit's "Author" value would be used instead.
$class: 'BuildChooserSetting'
When you are interested in using a job to build multiple heads (most typically multiple branches), you can choose how Jenkins choose what branches to build in what order.

This extension point in Jenkins is used by many other plugins to control the job to build specific commits. When you activate those plugins, you may see them installing a custom strategy here.

buildChooser
Nested choice of objects
$class: 'AncestryBuildChooser'
maximumAgeInDays
Type:int
ancestorCommitSha1
Type:String
$class: 'DefaultBuildChooser'
$class: 'InverseBuildChooser'
buildSingleRevisionOnly
Disable scheduling for multiple candidate revisions.
If we have 3 branches:
----A--.---.--- B
         \-----C
jenkins would try to build (B) and (C).
This behaviour disables this and only builds one of them.
It is helpful to reduce the load of the Jenkins infrastructure when the SCM system like Bitbucket or GitHub should decide what commits to build.
changelogToBranch
This method calculates the changelog against the specified branch.
options
changelogBase
compareRemote
Name of the repository, such as origin, that contains the branch you specify below.
Type:String
compareTarget
The name of the branch within the named repository to compare against.
Type:String
checkoutOption
timeout
Specify a timeout (in minutes) for checkout.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
cleanBeforeCheckout
Clean up the workspace before every checkout by deleting all untracked files and directories, including those which are specified in .gitignore. It also resets all tracked files to their versioned state. This ensures that the workspace is in the same state as if you cloned and checked out in a brand-new empty directory, and ensures that your build is not affected by the files generated by the previous build.
deleteUntrackedNestedRepositories (optional)
Deletes untracked submodules and any other subdirectories which contain .git directories.
Type:boolean
cleanAfterCheckout
Clean up the workspace after every checkout by deleting all untracked files and directories, including those which are specified in .gitignore. It also resets all tracked files to their versioned state. This ensures that the workspace is in the same state as if you cloned and checked out in a brand-new empty directory, and ensures that your build is not affected by the files generated by the previous build.
deleteUntrackedNestedRepositories (optional)
Deletes untracked submodules and any other subdirectories which contain .git directories.
Type:boolean
cloneOption
shallow
Perform shallow clone, so that git will not download the history of the project, saving time and disk space when you just want to access the latest version of a repository.
Type:boolean
noTags
Deselect this to perform a clone without tags, saving time and disk space when you just want to access what is specified by the refspec.
Type:boolean
reference
Specify a folder containing a repository that will be used by Git as a reference during clone operations.
This option will be ignored if the folder is not available on the controller or agent where the clone is being executed.
Type:String
timeout
Specify a timeout (in minutes) for clone and fetch operations.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
depth (optional)
Set shallow clone depth, so that git will only download recent history of the project, saving time and disk space when you just want to access the latest commits of a repository.
Type:int
honorRefspec (optional)
Perform initial clone using the refspec defined for the repository. This can save time, data transfer and disk space when you only need to access the references specified by the refspec.
Type:boolean
$class: 'DisableRemotePoll'
Git plugin uses git ls-remote polling mechanism by default when configured with a single branch (no wildcards!). This compare the latest built commit SHA with the remote branch without cloning a local copy of the repo.

If you don't want to / can't use this.

If this option is selected, polling will require a workspace and might trigger unwanted builds (see JENKINS-10131).
lfs
Enable git large file support for the workspace by pulling large files after the checkout completes. Requires that the controller and each agent performing an LFS checkout have installed `git lfs`.
$class: 'IgnoreNotifyCommit'
If checked, this repository will be ignored when the notifyCommit-URL is accessed regardless of if the repository matches or not.
localBranch
If given, checkout the revision to build as HEAD on this branch.

If selected, and its value is an empty string or "**", then the branch name is computed from the remote branch without the origin. In that case, a remote branch origin/master will be checked out to a local branch named master, and a remote branch origin/develop/new-feature will be checked out to a local branch named develop/newfeature.

Please note that this has not been tested with submodules.

localBranch
Type:String
$class: 'MessageExclusion'
excludedMessage
If set, and Jenkins is set to poll for changes, Jenkins will ignore any revisions committed with message matched to Pattern when determining if a build needs to be triggered. This can be used to exclude commits done by the build itself from triggering another build, assuming the build server commits the change with a distinct message.

Exclusion uses Pattern matching

.*\[maven-release-plugin\].*
The example above illustrates that if only revisions with "[maven-release-plugin]" message in first comment line have been committed to the SCM a build will not occur.

You can create more complex patterns using embedded flag expressions.

(?s).*FOO.*
This example will search FOO message in all comment lines.
Type:String
$class: 'PathRestriction'
If set, and Jenkins is set to poll for changes, Jenkins will pay attention to included and/or excluded files and/or folders when determining if a build needs to be triggered.

Using this behaviour will preclude the faster git ls-remote polling mechanism, forcing polling to require a workspace thus sometimes triggering unwanted builds, as if you had selected the Force polling using workspace extension as well.

includedRegions
Each inclusion uses java regular expression pattern matching, and must be separated by a new line. An empty list implies that everything is included.

    myapp/src/main/web/.*\.html
    myapp/src/main/web/.*\.jpeg
    myapp/src/main/web/.*\.gif
  
The example above illustrates that a build will only occur, if html/jpeg/gif files have been committed to the SCM. Exclusions take precedence over inclusions, if there is an overlap between included and excluded regions.
Type:String
excludedRegions
Each exclusion uses java regular expression pattern matching, and must be separated by a new line.

    myapp/src/main/web/.*\.html
    myapp/src/main/web/.*\.jpeg
    myapp/src/main/web/.*\.gif
  
The example above illustrates that if only html/jpeg/gif files have been committed to the SCM a build will not occur.
Type:String
perBuildTag
Create a tag in the workspace for every build to unambiguously mark the commit that was built. You can combine this with Git publisher to push the tags to the remote repository.
$class: 'PreBuildMerge'
These options allow you to perform a merge to a particular branch before building. For example, you could specify an integration branch to be built, and to merge to master. In this scenario, on every change of integration, Jenkins will perform a merge with the master branch, and try to perform a build if the merge is successful. It then may push the merge back to the remote repository if the Git Push post-build action is selected.
options
Nested object
mergeTarget
The name of the branch within the named repository to merge to, such as master.
Type:String
fastForwardMode (optional)
Merge fast-forward mode selection.
The default, --ff, gracefully falls back to a merge commit when required.
For more information, see the Git Merge Documentation
Values:
FF
FF_ONLY
NO_FF
mergeRemote (optional)
Name of the repository, such as origin, that contains the branch you specify below. If left blank, it'll default to the name of the first repository configured above.
Type:String
mergeStrategy (optional)
Merge strategy selection. This feature is not fully implemented in JGIT.
Values:
DEFAULT
RESOLVE
RECURSIVE
OCTOPUS
OURS
SUBTREE
RECURSIVE_THEIRS
pruneStaleBranch
Run "git remote prune" for each remote, to prune obsolete local branches.
pruneTags
pruneTags
Type:boolean
$class: 'RelativeTargetDirectory'
relativeTargetDir
Specify a local directory (relative to the workspace root) where the Git repository will be checked out. If left empty, the workspace root itself will be used.

This extension should not be used in Jenkins Pipeline (either declarative or scripted). Jenkins Pipeline already provides standard techniques for checkout to a subdirectory. Use ws and dir in Jenkins Pipeline rather than this extension.

Type:String
$class: 'ScmName'

Unique name for this SCM. Needed when using Git within the Multi SCM plugin.

name
Type:String
$class: 'SparseCheckoutPaths'

Specify the paths that you'd like to sparse checkout. This may be used for saving space (Think about a reference repository). Be sure to use a recent version of Git, at least above 1.7.10

sparseCheckoutPaths
Array/List:
Nested object
path
Type:String
submodule
depth (optional)
Set shallow clone depth, so that git will only download recent history of the project, saving time and disk space when you just want to access the latest commits of a repository.
Type:int
disableSubmodules (optional)
By disabling support for submodules you can still keep using basic git plugin functionality and just have Jenkins to ignore submodules completely as if they didn't exist.
Type:boolean
parentCredentials (optional)
Use credentials from the default remote of the parent project.
Type:boolean
recursiveSubmodules (optional)
Retrieve all submodules recursively (uses '--recursive' option which requires git>=1.6.5)
Type:boolean
reference (optional)
Specify a folder containing a repository that will be used by Git as a reference during clone operations.
This option will be ignored if the folder is not available on the controller or agent where the clone is being executed.
To prepare a reference folder with multiple subprojects, create a bare git repository and add all the remote urls then perform a fetch:
  git init --bare
  git remote add SubProject1 https://gitrepo.com/subproject1
  git remote add SubProject2 https://gitrepo.com/subproject2
  git fetch --all
  
Type:String
shallow (optional)
Perform shallow clone, so that git will not download the history of the project, saving time and disk space when you just want to access the latest version of a repository.
Type:boolean
threads (optional)
Specify the number of threads that will be used to update submodules.
If unspecified, the command line git default thread count is used.
Type:int
timeout (optional)
Specify a timeout (in minutes) for submodules operations.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
trackingSubmodules (optional)
Retrieve the tip of the configured branch in .gitmodules (Uses '--remote' option which requires git>=1.8.2)
Type:boolean
$class: 'UserExclusion'
excludedUsers
If set, and Jenkins is set to poll for changes, Jenkins will ignore any revisions committed by users in this list when determining if a build needs to be triggered. This can be used to exclude commits done by the build itself from triggering another build, assuming the build server commits the change with a distinct SCM user.

Using this behaviour will preclude the faster git ls-remote polling mechanism, forcing polling to require a workspace thus sometimes triggering unwanted builds, as if you had selected the Force polling using workspace extension as well.

Each exclusion uses exact string comparison and must be separated by a new line. User names are only excluded if they exactly match one of the names in this list.

auto_build_user
The example above illustrates that if only revisions by "auto_build_user" have been committed to the SCM a build will not occur.
Type:String
$class: 'UserIdentity'
name

If given, "GIT_COMMITTER_NAME=[this]" and "GIT_AUTHOR_NAME=[this]" are set for builds. This overrides whatever is in the global settings.

Type:String
email

If given, "GIT_COMMITTER_EMAIL=[this]" and "GIT_AUTHOR_EMAIL=[this]" are set for builds. This overrides whatever is in the global settings.

Type:String
$class: 'WipeWorkspace'
Delete the contents of the workspace before building, ensuring a fully fresh workspace.
doGenerateSubmoduleConfigurations (optional)

Removed facility that was intended to test combinations of git submodule versions. Removed in git plugin 4.6.0. Ignores the user provided value and always uses false as its value.

Type:boolean
submoduleCfg (optional)

Removed facility that was intended to test combinations of git submodule versions. Removed in git plugin 4.6.0. Ignores the user provided value(s) and always uses empty values.

Array/List:
Nested object
submoduleName

Removed in git plugin 4.6.0.

Type:String
branches

Removed in git plugin 4.6.0.

Array/List:
Type:String
none
changelog (optional)
Enable or Disable 'Include in changelog':

If 'Include in changelog' is enabled for an SCM source, then when a build occurs, the changes from that SCM source will be included in the changelog.

If 'Include in changelog' is disabled, then when a build occurs, the changes from this SCM source will not be included in the changelog.

Type:boolean
poll (optional)
Enable or Disable 'Include in polling'

If 'Include in polling' is enabled or 'Include in changelog' is enabled, then when polling occurs, the job will be started if changes are detected from this SCM source.

If 'Include in polling' is disabled and 'Include in changelog' is disabled, then when polling occurs, changes that are detected from this repository will be ignored.

Type:boolean
cleanWs: Delete workspace when build is done
cleanWhenAborted (optional)
Type:boolean
cleanWhenFailure (optional)
Type:boolean
cleanWhenNotBuilt (optional)
Type:boolean
cleanWhenSuccess (optional)
Type:boolean
cleanWhenUnstable (optional)
Type:boolean
cleanupMatrixParent (optional)
Type:boolean
deleteDirs (optional)
Type:boolean
disableDeferredWipeout (optional)
Type:boolean
externalDelete (optional)
Type:String
notFailBuild (optional)
Type:boolean
patterns (optional)
Array/List:
Nested object
pattern
Type:String
type
Values:
INCLUDE
EXCLUDE
skipWhenFailed (optional)
Type:boolean
configFileProvider: Provide Configuration files
Make globally configured files available in your local workspace. All files configured via the config-file-provider plugin are available and can be referenced.
managedFiles
Array/List:
configFile
fileId

Name of the file.

Type:String
replaceTokens (optional)

Decides whether the token should be replaced using macro.

Type:boolean
targetLocation (optional)

Name of the file (with optional file relative to workspace directory) where the config file should be copied.

Type:String
variable (optional)

Name of the variable which can be used as the reference for further configuration.

Type:String
container: Run build steps in a container
Selects a container of the agent pod so that all shell steps are executed in that container.
name
Type:String
shell (optional)

Specifies a shell which will run inside the container and process requests from Jenkins to run executables, set environment variables, and similar infrastructure.

This does not affect the shell used to run user code, such as sh steps. To run your scripts with a specific shell on Linux, use an interpreter line:

sh '''#!/bin/bash
for x in {0..9}; do echo x; done
'''

or just use a subprocess and an externally versioned script:

sh 'bash ci.sh'

On Windows, choose between the bat or powershell steps.

For a pod running on Linux, defaults to sh, which should be in $PATH; for a pod running on Windows, defaults to cmd, which should be in %Path%. Should not generally be overridden.

Type:String
deleteDir: Recursively delete the current directory from the workspace
Recursively deletes the current directory and its contents. Symbolic links and junctions will not be followed but will be removed. To delete a specific directory of a workspace wrap the deleteDir step in a dir step.
dir: Change current directory
Change current directory. Any step inside the dir block will use this directory as current and any relative path will use it as base path.
path
The relative path of the directory in the workspace to use as a new working directory.
Type:String
discoverReferenceBuild: Discover reference build
referenceJob (optional)
The reference job is the baseline that is used to determine which of the issues in the current build are new, outstanding, or fixed. This baseline is also used to determine the number of new issues for the quality gate evaluation.
Type:String
echo: Print Message
message
The message to write to the console output.
Type:String
emailext: Extended Email
Step for sending email via the email-ext plugin.
subject
Type:String
body
Type:String
attachLog (optional)
Type:boolean
attachmentsPattern (optional)
Type:String
compressLog (optional)
Type:boolean
from (optional)
Type:String
mimeType (optional)
Type:String
postsendScript (optional)
Type:String
presendScript (optional)
Type:String
recipientProviders (optional)
Array/List:
Nested choice of objects
buildUser
contributor
culprits
Sends email to the list of users who committed a change since the last non-broken build till now. This list at least always include people who made changes in this build, but if the previous build was a failure it also includes the culprit list from there.
developers
Sends email to all the people who caused a change in the change set.
brokenTestsSuspects
Sends email to the list of users suspected of causing a unit test to begin failing. This list includes committers and requestors of the build where the test began to fail, and those for any consecutive failed builds prior to the build in which the test began to fail.
Build Number 1 2 3 4 5
Requestor Alice Alice
Committers Bob
Clay
Clay
Dan
Bob
Ed
Ed
foo Failed Failed Passed N/A Failed
bar Failed Failed Passed N/A Passed
baz Passed Failed Failed N/A Passed
qux Passed Passed Failed N/A Passed
new N/A Failed
Suspects Alice (foo, bar) Alice (foo, bar)
Bob (baz)
Clay (baz)
Bob (baz)
Clay (baz, qux)
Dan (qux)
N/A
(build failed)
Alice (foo, new)
Bob (foo, new)
Ed (foo, new)
brokenBuildSuspects
Sends email to the list of users suspected of causing the build to begin failing.
recipients
Sends email to the list of recipients defined in the "Project Recipient List."
previous
Sends an email to the the culprits, requestor and developers of the previous build(s).
requestor
Sends email to the user who initiated the build.
upstreamDevelopers
Sends email to the list of users who committed changes in upstream builds that triggered this build.
replyTo (optional)
Type:String
saveOutput (optional)
Type:boolean
to (optional)
Type:String
emailextrecipients: Extended Email Recipients
recipientProviders
Array/List:
Nested choice of objects
buildUser
contributor
culprits
Sends email to the list of users who committed a change since the last non-broken build till now. This list at least always include people who made changes in this build, but if the previous build was a failure it also includes the culprit list from there.
developers
Sends email to all the people who caused a change in the change set.
brokenTestsSuspects
Sends email to the list of users suspected of causing a unit test to begin failing. This list includes committers and requestors of the build where the test began to fail, and those for any consecutive failed builds prior to the build in which the test began to fail.
Build Number 1 2 3 4 5
Requestor Alice Alice
Committers Bob
Clay
Clay
Dan
Bob
Ed
Ed
foo Failed Failed Passed N/A Failed
bar Failed Failed Passed N/A Passed
baz Passed Failed Failed N/A Passed
qux Passed Passed Failed N/A Passed
new N/A Failed
Suspects Alice (foo, bar) Alice (foo, bar)
Bob (baz)
Clay (baz)
Bob (baz)
Clay (baz, qux)
Dan (qux)
N/A
(build failed)
Alice (foo, new)
Bob (foo, new)
Ed (foo, new)
brokenBuildSuspects
Sends email to the list of users suspected of causing the build to begin failing.
recipients
Sends email to the list of recipients defined in the "Project Recipient List."
previous
Sends an email to the the culprits, requestor and developers of the previous build(s).
requestor
Sends email to the user who initiated the build.
upstreamDevelopers
Sends email to the list of users who committed changes in upstream builds that triggered this build.
error: Error signal
Signals an error. Useful if you want to conditionally abort some part of your program. You can also just throw new Exception(), but this step will avoid printing a stack trace.
message
The message that will be logged to the console when an error is caught.
Type:String
fileExists: Verify if file exists in workspace
Checks if the given file exists on the current node. Returns true | false. This step must be run inside a node context:

# Declarative Syntax
stage ('Check for existence of index.html') {
    agent any # Could be a top-level directive or a stage level directive
    steps {
        script {
            if (fileExists('src/main/resources/index.html')) {
                echo "File src/main/resources/index.html found!"
            }
        }
    }
}

With the Declarative Syntax, it must be run in a stage with a defined agent (e.g. different than `agent none`):

# Scripted Syntax
node {
    if (fileExists('src/main/resources/index.html')) {
        echo "File src/main/resources/index.html found!"
    }
}

file
Path to a file or a directory to verify its existence.
  • Both absolute and relative paths are supported. When using relative path, it is relative to the current working directory (by default: the workspace).
  • Both Unix and Windows path are supported using a
    /
    separator:

    node('Linux') {
        if (fileExists('/usr/local/bin/jenkins.sh')) {
            sh '/usr/local/bin/jenkins.sh'
        }
    }
    node('Windows') {
        if (fileExists('C:/jenkins.exe')) {
            bat 'C:/jenkins.exe'
        }
    }
    

    When using a Windows path with the backslash (
    \
    ) separator, do not forget to escape it:

    node('Windows') { if (fileExists('src\\main\\resources')) { echo 'Found a directory resources.' } }

Type:String
fingerprint: Record fingerprints of files to track usage
Jenkins can record the 'fingerprint' of files (most often jar files) to keep track of where/when those files are produced and used. When you have inter-dependent projects on Jenkins, this allows you to quickly find out answers to questions like:
  • I have foo.jar on my HDD but which build number of FOO did it come from?
  • My BAR project depends on foo.jar from the FOO project.
    • Which build of foo.jar is used in BAR #51?
    • Which build of BAR contains my bug fix to foo.jar #32?

To use this feature, all of the involved projects (not just the project in which a file is produced, but also the projects in which the file is used) need to use this and record fingerprints.

See this document for more details.

targets
Can use wildcards like module/dist/**/*.zip (see the @includes of Ant fileset for the exact format). The base directory is the workspace .
Type:String
caseSensitive (optional)
Fingerprinter uses Ant org.apache.tools.ant.DirectoryScanner which by default is case sensitive. For instance, if the job produces *.hpi files, pattern "**/*.HPI" will fail to find them.

This option can be used to disable case sensitivity. When it's unchecked, pattern "**/*.HPI" will match any *.hpi files, or pattern "**/cAsEsEnSiTiVe.jar" will match a file called caseSensitive.jar.
Type:boolean
defaultExcludes (optional)
Type:boolean
excludes (optional)
Optionally specify the 'excludes' pattern, such as "foo/bar/**/*". Use "," to set a list of patterns. A file that matches this mask will not be fingerprinted even if it matches the mask specified in 'files to fingerprint' section.
Type:String
git: Git

Git step. It performs a clone from the specified repository.

Use the Pipeline Syntax Snippet Generator to generate a sample pipeline script for the git step. More advanced checkout operations require the checkout step rather than the git step. Examples of the git step include:

See the argument descriptions for more details.

The git step is a simplified shorthand for a subset of the more powerful checkout step:

checkout([$class: 'GitSCM', branches: [[name: '*/master']],
    userRemoteConfigs: [[url: 'https://git-server/user/repository.git']]])


NOTE: The checkout step is the preferred SCM checkout method. It provides significantly more functionality than the git step.

Use the Pipeline Syntax Snippet Generator to generate a sample pipeline script for the checkout step.

The checkout step can be used in many cases where the git step cannot be used. Refer to the git plugin documentation for detailed descriptions of options available to the checkout step. For example, the git step does not support:

  • SHA-1 checkout
  • Tag checkout
  • Submodule checkout
  • Sparse checkout
  • Large file checkout (LFS)
  • Reference repositories
  • Branch merges
  • Repository tagging
  • Custom refspecs
  • Timeout configuration
  • Changelog calculation against a non-default reference
  • Stale branch pruning


Example: Git step with defaults

Checkout from the git plugin source repository using https protocol, no credentials, and the master branch.

The Pipeline Syntax Snippet Generator generates this example:

git 'https://github.com/jenkinsci/git-plugin'

Example: Git step with https and a specific branch

Checkout from the Jenkins source repository using https protocol, no credentials, and a specific branch (stable-2.204). Note that this must be a local branch name like 'master' or 'develop'.

Branch names that are not supported by the git step

  • Remote branch names like 'origin/master' and 'origin/develop' are not supported as the branch argument
  • SHA-1 hashes are not supported as the branch argument
  • Tag names are not supported as the branch argument

Remote branch names, SHA-1 hashes, and tag names are supported by the general purpose checkout step.

The Pipeline Syntax Snippet Generator generates this example:

git branch: 'stable-2.204',
    url: 'https://github.com/jenkinsci/jenkins.git'

Example: Git step with ssh and a private key credential

Checkout from the git client plugin source repository using ssh protocol, private key credentials, and the master branch. The credential must be a private key credential if the remote git repository is accessed with the ssh protocol. The credential must be a username / password credential if the remote git repository is accessed with http or https protocol.

The Pipeline Syntax Snippet Generator generates this example:

git credentialsId: 'my-private-key-credential-id',
    url: 'git@github.com:jenkinsci/git-client-plugin.git'

Example: Git step with https and changelog disabled

Checkout from the Jenkins source repository using https protocol, no credentials, the master branch, and changelog calculation disabled. If changelog is false, then the changelog will not be computed for this job. If changelog is true or is not set, then the changelog will be computed. See the workflow scm step documentation for more changelog details.

The Pipeline Syntax Snippet Generator generates this example:

git changelog: false,
    url: 'https://github.com/jenkinsci/credentials-plugin.git'

Example: Git step with https protocol and polling disabled

Checkout from the Jenkins platform labeler repository using https protocol, no credentials, the master branch, and no polling for changes. If poll is false, then the remote repository will not be polled for changes. If poll is true or is not set, then the remote repository will be polled for changes. See the workflow scm step documentation for more polling details.

The Pipeline Syntax Snippet Generator generates this example:

git poll: false,
    url: 'https://github.com/jenkinsci/platformlabeler-plugin.git'


Argument Descriptions
url

URL of the repository to be checked out in the workspace. Required parameter.

Repository URL's should follow the git URL guidelines. Git steps to access a secured repository should provide a Jenkins credential with the credentialsId argument rather than embedding credentials in the URL. Credentials embedded in a repository URL may be visible in console logs or in other log files.

Type:String
branch (optional)

Branch to be checked out in the workspace. Default is 'master'.

Note that this must be a local branch name like 'master' or 'develop'. Remote branch names like 'origin/master' and 'origin/develop' are not supported as the branch argument. Tag names are not supported as the branch argument. SHA-1 hashes are not supported as the branch argument. Remote branch names, tag names, and SHA-1 hashes are supported by the general purpose checkout step.

Type:String
changelog (optional)

Compute changelog for this job. Default is 'true'.

If changelog is false, then the changelog will not be computed for this job. If changelog is true or is not set, then the changelog will be computed.

Type:boolean
credentialsId (optional)

Identifier of the credential used to access the remote git repository. Default is '<empty>'.

The credential must be a private key credential if the remote git repository is accessed with the ssh protocol. The credential must be a username / password credential if the remote git repository is accessed with http or https protocol.

Type:String
poll (optional)

Poll remote repository for changes. Default is 'true'.

If poll is false, then the remote repository will not be polled for changes. If poll is true or is not set, then the remote repository will be polled for changes.

Type:boolean
gitlabBuilds: Notify gitlab about pending builds
builds (optional)
Array/List:
Type:String
gitlabCommitStatus: Update the commit status in GitLab depending on the build status
name
Type:String
builds (optional)
Array/List:
Nested object
connection (optional)
gitLabConnection
gitLabConnection
Type:String
jobCredentialId (optional)
Type:String
useAlternativeCredential (optional)
Type:boolean
name (optional)
Type:String
projectId (optional)
Type:String
revisionHash (optional)
Type:String
connection (optional)
gitLabConnection
gitLabConnection
Type:String
jobCredentialId (optional)
Type:String
useAlternativeCredential (optional)
Type:boolean
input: Wait for interactive input

This step pauses Pipeline execution and allows the user to interact and control the flow of the build. Only a basic "proceed" or "abort" option is provided in the stage view.

You can optionally request information back, hence the name of the step. The parameter entry screen can be accessed via a link at the bottom of the build console log or via link in the sidebar for a build.

message

This parameter gives a prompt which will be shown to a human:

    Ready to go?
    Proceed or Abort
    

If you click "Proceed" the build will proceed to the next step, if you click "Abort" the build will be aborted.

Type:String
id (optional)

Every input step has an unique identifier. It is used in the generated URL to proceed or abort.

A specific identifier could be used, for example, to mechanically respond to the input from some external process/tool.

Type:String
ok (optional)
Type:String
parameters (optional)

Request that the submitter specify one or more parameter values when approving. If just one parameter is listed, its value will become the value of the input step. If multiple parameters are listed, the return value will be a map keyed by the parameter names. If parameters are not requested, the step returns nothing if approved.

On the parameter entry screen you are able to enter values for parameters that are defined in this field.

Array/List:
Nested choice of objects
booleanParam
name
Type:String
defaultValue (optional)
Type:boolean
description (optional)
Type:String
choice
name
Type:String
description (optional)
Type:String
choices (optional)
Nested choice of objects
(not enumerable)
credentials
Defines a credentials parameter, which you can use during a build.

For security reasons, the credential is NOT directly exposed, the ID of the credential is exposed.

However, the selected credential is available through variable substitution in some other parts of the configuration. The string value will be the ID of the credential. A supporting plugin can thus use the ID to retrieve the selected credential and expose it to the build in an appropriate way.
name
Type:String
defaultValue
The default credentials to use.
Type:String
credentialType
Type:String
required
When this option is selected, the credentials selection drop down will not provide the empty selection as one of the options. This will not prevent a build without a value if there are no credentials available, for example if the job does not have access to any credentials of the correct type or there is no default value and the user starting the build either does not have any credentials of the correct type in their personal credentials store or they do not have permissions on the job to use credentials from their personal store.
Type:boolean
description (optional)
Type:String
file
name
Type:String
description (optional)
Type:String
gitParameter

When used, this parameter will present at build-time a choice to select a Git tag (or revision number) which set a parameter for parametrized build.

Be aware that git does not allow us get additional information (like author/commmit date) from a remote URL this plugin will silently clone the project when your workspace is empty. This may take a long time when we have a slow connection and/or the checkout is big.

Often the parameter defined in the "Name" field is used to specify the branch of the git checkout.

name
The name of the parameter.
Type:String
type
The type of the list of parameters:
  • Tag - list of all commit tags in repository - returns Tag Name
  • Branch - list of all branch in repository - returns Branch Name
  • Revision - list of all revision sha1 in repository followed by its author and date - returns Tag SHA1
Type:String
defaultValue
This value is returned when the list is empty or if an error occurs while retrieving data.
Type:String
branch
Name of branch to look in. Used only if listing revisions.
Type:String
branchFilter
Regex used to filter displayed branches. If blank, the filter will default to ".*".
Remote branches will be listed with the remote name first. E.g., "origin/master"
Type:String
tagFilter
This parameter is used to get tag from git.
If is blank, parameter is set to "*".
Properly is executed command: git ls-remote -t <repository> "*" or git ls-remote -t <repository> "$tagFilter".
git-ls-remote documentation.
Type:String
sortMode
Select how to sort the downloaded parameters. Only applies to a branch or a tag.
  • none
  • ascending smart
  • descending smart
  • ascending
  • descending
When smart sorting is chosen, the compare treats a sequence of digits as a single character.
Values:
NONE
ASCENDING_SMART
DESCENDING_SMART
ASCENDING
DESCENDING
selectedValue
Which value is selected, after loaded parameters.
If you choose 'default', but default value is not present on the list, nothing is selected.
Values:
NONE
TOP
DEFAULT
useRepository
If in the task are defined multiple repositories, this option specifies which the repository is taken into account on getting data.
If the option is not defined, is taken a first defined repository.
This option is a regular expression, which is compared to the 'Repository URL'.
Type:String
quickFilterEnabled
When this option is enabled will show a text field.
Parameter is filtered on the fly.
Type:boolean
description (optional)
A description that will be shown to the user later.
Type:String
listSize (optional)
Specify the number of items the list will display. A value of 0 will display as a DropDown list.
Type:String
requiredParameter (optional)
When this option is selected the user must select an option or an error will be thrown(default values are ignored)
Type:boolean
password
Pass a password to your build. The password entered here is made available to the build in plain text as an environment variable like a string parameter would be. The value will be stored encrypted on the Jenkins controller, similar to passwords in Jenkins configuration.
name
Type:String
defaultValueAsSecret
org.kohsuke.stapler.NoStaplerConstructorException: There's no @DataBoundConstructor on any constructor of class hudson.util.Secret
description (optional)
Type:String
$class: 'PromotedBuildParameterDefinition'
name
Type:String
jobName
Type:String
process
Type:String
description (optional)
Type:String
run
name
Type:String
projectName
Type:String
filter
Values:
ALL
STABLE
SUCCESSFUL
COMPLETED
description (optional)
Type:String
string
name
Type:String
defaultValue (optional)
Type:String
description (optional)
Type:String
trim (optional)
Strip whitespace from the beginning and end of the string.
Type:boolean
text
name
Type:String
defaultValue (optional)
Type:String
description (optional)
Type:String
trim (optional)
Strip whitespace from the beginning and end of the string.
Type:boolean
submitter (optional)
User IDs and/or external group names of person or people permitted to respond to the input, separated by ','. Spaces will be trimmed. This means that "alice, bob, blah " is the same as "alice,bob,blah".
Note: Jenkins administrators are able to respond to the input regardless of the value of this parameter.
Type:String
submitterParameter (optional)
If specified, this is the name of the return value that will contain the ID of the user that approves this input. The return value will be handled in a fashion similar to the parameters value.
Type:String
isUnix: Checks if running on a Unix-like node
Returns true if enclosing node is running on a Unix-like system (such as Linux or Mac OS X), false if Windows.
javadoc: Publish Javadoc
javadocDir
Type:String
keepAll
If you check this option, Jenkins will retain Javadoc for each successful build. This allows you to browse Javadoc for older builds, at the expense of additional disk space requirement.

If you leave this option unchecked, Jenkins will only keep the latest Javadoc, so older Javadoc will be overwritten as new builds succeed.

Type:boolean
junit: Archive JUnit-formatted test results
Jenkins understands the JUnit test report XML format (which is also used by TestNG). When this option is configured, Jenkins can provide useful information about test results, such as historical test result trends, a web UI for viewing test reports, tracking failures, and so on.

To use this feature, first set up your build to run tests, then specify the path to JUnit XML files in the Ant glob syntax, such as **/build/test-reports/*.xml. Be sure not to include any non-report files into this pattern. You can specify multiple patterns of files separated by commas.

testResults
Type:String
allowEmptyResults (optional)
If checked, the default behavior of failing a build on missing test result files or empty test results is changed to not affect the status of the build. Please note that this setting make it harder to spot misconfigured jobs or build failures where the test tool does not exit with an error code when not producing test report files.
Type:boolean
checksName (optional)
If provided, and publishing checks enabled, the plugin will use this name when publishing results to corresponding SCM hosting platforms. If not, a default including the current stage / branch names will be used.
Type:String
healthScaleFactor (optional)
The amplification factor to apply to test failures when computing the test result contribution to the build health score.
The default factor is 1.0
  • A factor of 0.0 will disable the test result contribution to build health score.
  • A factor of 0.1 means that 10% of tests failing will score 99% health
  • A factor of 0.5 means that 10% of tests failing will score 95% health
  • A factor of 1.0 means that 10% of tests failing will score 90% health
  • A factor of 2.0 means that 10% of tests failing will score 80% health
  • A factor of 2.5 means that 10% of tests failing will score 75% health
  • A factor of 5.0 means that 10% of tests failing will score 50% health
  • A factor of 10.0 means that 10% of tests failing will score 0% health
The factor is persisted with the build results, so changes will only be reflected in new builds.
Type:double
keepLongStdio (optional)
If checked, any standard output or error from a test suite will be retained in the test results after the build completes. (This refers only to additional messages printed to console, not to a failure stack trace.) Such output is always kept if the test failed, but by default lengthy output from passing tests is truncated to save space. Check this option if you need to see every log message from even passing tests, but beware that Jenkins's memory consumption can substantially increase as a result, even if you never look at the test results!
Type:boolean
keepProperties (optional)
Type:boolean
skipMarkingBuildUnstable (optional)
If this option is unchecked, then the plugin will mark the build as unstable when it finds at least 1 test failure. If this option is checked, then the build will still be successful even if there are test failures reported. In any case, the corresponding pipeline node (and stage) will be marked as unstable in case of test failure.
Type:boolean
skipOldReports (optional)
Type:boolean
skipPublishingChecks (optional)
If this option is unchecked, then the plugin automatically publishes the test results to corresponding SCM hosting platforms. For example, if you are using this feature for a GitHub organization project, the warnings will be published to GitHub through the Checks API. If this operation slows down your build, or you don't want to publish the warnings to SCM platforms, you can use this option to deactivate this feature.
Type:boolean
testDataPublishers (optional)
Array/List:
Nested choice of objects
kubeconfig: Setup Kubernetes CLI (kubectl)
Configure Kubernetes client (kubectl) so it can be used in the build to run Kubernetes commands
serverUrl
URL of the Kubernetes API endpoint. If not set the connection options will be autoconfigured from service account or kube config file.
Type:String
credentialsId
Type:String
caCertificate
The base64 encoded certificate of the certificate authority (CA). It is used to verify the server certificate.

Leaving this field empty will skip the certificate verification.

Type:String
library: Load a library on the fly

Load a library dynamically rather than using @Library syntax. You may use global variables defined in the library thereafter:


library 'mylib@master'
usefulFunction()

You may also load classes defined in the library by selecting their fully-qualified names like properties on the return value of this step, then call static methods or call constructors as if they were a method named new:


def utils = library('mylib').com.mycorp.jenkins.Utils.new(this)
utils.handyStuff()
identifier
A library name to load. Should normally match that of a predefined library. You can append a version after @. You may instead define a library inline here.
Type:String
changelog (optional)
Whether to include any changes in the library in the recent changes of jobs using the library. Defaults to including the changes.
Type:boolean
retriever (optional)
Nested choice of objects
legacySCM
scm
Nested choice of objects
scmGit

The git plugin provides fundamental git operations for Jenkins projects. It can poll, fetch, checkout, and merge contents of git repositories.

The git plugin provides an SCM implementation to be used with the Pipeline SCM checkout step. The Pipeline Syntax Snippet Generator guides the user to select git plugin checkout options and provides online help for each of the options.

Use the Pipeline Snippet Generator to generate a sample pipeline script for the checkout step. Examples of the checkout step include:

See the argument descriptions for more details.

The checkout step provides access to all the Pipeline capabilities provided by the git plugin:

checkout scmGit(userRemoteConfigs: [
                    [ url: 'https://github.com/jenkinsci/git-plugin' ]
                ])


NOTE: The checkout step is the preferred SCM checkout method. For simpler cases that do not require all the capabilities of the git plugin, the git step can also be used.

Use the Pipeline Snippet Generator to generate a sample pipeline script for the checkout step.

The checkout step can be used in many cases where the git step cannot be used. Refer to the git plugin documentation for detailed descriptions of options available to the checkout step. For example, the checkout step supports:

  • SHA-1 checkout
  • Tag checkout
  • Submodule checkout
  • Sparse checkout
  • Large file checkout (LFS)
  • Reference repositories
  • Branch merges
  • Repository tagging
  • Custom refspecs
  • Timeout configuration
  • Changelog calculation against a non-default reference
  • Stale branch pruning


Example: Checkout step with defaults

Checkout from the git plugin source repository using https protocol, no credentials, and the master branch.

The Pipeline Snippet Generator generates this example:

checkout scmGit(userRemoteConfigs: [
                    [ url: 'https://github.com/jenkinsci/git-plugin' ]
                ])

Example: Checkout step with https and a specific branch

Checkout from the Jenkins source repository using https protocol, no credentials, and a specific branch (stable-2.289).

The Pipeline Snippet Generator generates this example:

checkout scmGit(branches: [[name: 'stable-2.289']],
                userRemoteConfigs: [
                    [ url: 'https://github.com/jenkinsci/jenkins.git' ]
                ])

Example: Checkout step with ssh and a private key credential

Checkout from the git client plugin source repository using ssh protocol, private key credentials, and the master branch. The credential must be a private key credential if the remote git repository is accessed with the ssh protocol. The credential must be a username / password credential if the remote git repository is accessed with http or https protocol.

The Pipeline Snippet Generator generates this example:

checkout changelog: false,
         scm: scmGit(userRemoteConfigs: [
                         [ credentialsId: 'my-private-key-credential-id',
                           url: 'git@github.com:jenkinsci/git-client-plugin.git' ]
                         ])

Example: Checkout step with https and changelog disabled

Checkout from the Jenkins source repository using https protocol, no credentials, the master branch, and changelog calculation disabled. If changelog is false, then the changelog will not be computed for this job. If changelog is true or is not set, then the changelog will be computed. See the workflow scm step documentation for more changelog details.

The Pipeline Snippet Generator generates this example:

checkout changelog: false,
         scmGit(userRemoteConfigs: [
                    [ url: 'https://github.com/jenkinsci/credentials-plugin' ]
                ])

Example: Checkout step with git protocol and polling disabled

Checkout from the command line git repository using git protocol, no credentials, the master branch, and no polling for changes. If poll is false, then the remote repository will not be polled for changes. If poll is true or is not set, then the remote repository will be polled for changes. See the workflow scm step documentation for more polling details.

The Pipeline Snippet Generator generates this example:

checkout poll: false,
         scmGit(userRemoteConfigs: [
                    [ url: 'git://git.kernel.org/pub/scm/git/git.git ]
                ])


Argument Descriptions
userRemoteConfigs
Specify the repository to track. This can be a URL or a local file path. Note that for super-projects (repositories with submodules), only a local file path or a complete URL is valid. The following are examples of valid git URLs.
  • ssh://git@github.com/github/git.git
  • git@github.com:github/git.git (short notation for ssh protocol)
  • ssh://user@other.host.com/~/repos/R.git (to access the repos/R.git repository in the user's home directory)
  • https://github.com/github/git.git

If the repository is a super-project, the location from which to clone submodules is dependent on whether the repository is bare or non-bare (i.e. has a working directory).
  • If the super-project is bare, the location of the submodules will be taken from .gitmodules.
  • If the super-project is not bare, it is assumed that the repository has each of its submodules cloned and checked out appropriately. Thus, the submodules will be taken directly from a path like ${SUPER_PROJECT_URL}/${SUBMODULE}, rather than relying on information from .gitmodules.
For a local URL/path to a super-project, git rev-parse --is-bare-repository is used to detect whether the super-project is bare or not.
For a remote URL to a super-project, the ending of the URL determines whether a bare or non-bare repository is assumed:
  • If the remote URL ends with .git, a non-bare repository is assumed.
  • If the remote URL does NOT end with .git, a bare repository is assumed.
Array/List:
Nested object
url
Specify the URL or path of the git repository. This uses the same syntax as your git clone command.
Type:String
name
ID of the repository, such as origin, to uniquely identify this repository among other remote repositories. This is the same "name" that you use in your git remote command. If left empty, Jenkins will generate unique names for you.

You normally want to specify this when you have multiple remote repositories.

Type:String
refspec
A refspec controls the remote refs to be retrieved and how they map to local refs. If left blank, it will default to the normal behaviour of git fetch, which retrieves all the branch heads as remotes/REPOSITORYNAME/BRANCHNAME. This default behaviour is OK for most cases.

In other words, the default refspec is "+refs/heads/*:refs/remotes/REPOSITORYNAME/*" where REPOSITORYNAME is the value you specify in the above "name of repository" textbox.

When do you want to modify this value? A good example is when you want to just retrieve one branch. For example, +refs/heads/master:refs/remotes/origin/master would only retrieve the master branch and nothing else.

The plugin uses a default refspec for its initial fetch, unless the "Advanced Clone Option" is set to honor refspec. This keeps compatibility with previous behavior, and allows the job definition to decide if the refspec should be honored on initial clone.

Multiple refspecs can be entered by separating them with a space character. +refs/heads/master:refs/remotes/origin/master +refs/heads/develop:refs/remotes/origin/develop retrieves the master branch and the develop branch and nothing else.

See the refspec definition in Git user manual for more details.

Type:String
credentialsId
Credential used to check out sources.
Type:String
branches
List of branches to build. Jenkins jobs are most effective when each job builds only a single branch. When a single job builds multiple branches, the changelog comparisons between branches often show no changes or incorrect changes.
Array/List:
Nested object
name

Specify the branches if you'd like to track a specific branch in a repository. If left blank, all branches will be examined for changes and built.

The safest way is to use the refs/heads/<branchName> syntax. This way the expected branch is unambiguous.

If your branch name has a / in it make sure to use the full reference above. When not presented with a full path the plugin will only use the part of the string right of the last slash. Meaning foo/bar will actually match bar.

If you use a wildcard branch specifier, with a slash (e.g. release/), you'll need to specify the origin repository in the branch names to make sure changes are picked up. So e.g. origin/release/

Possible options:

  • <branchName>
    Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily the expected one. Better use refs/heads/<branchName>.
    E.g. master, feature1, ...
  • refs/heads/<branchName>
    Tracks/checks out the specified branch.
    E.g. refs/heads/master, refs/heads/feature1/master, ...
  • <remoteRepoName>/<branchName>
    Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily the expected one.
    Better use refs/heads/<branchName>.
    E.g. origin/master
  • remotes/<remoteRepoName>/<branchName>
    Tracks/checks out the specified branch.
    E.g. remotes/origin/master
  • refs/remotes/<remoteRepoName>/<branchName>
    Tracks/checks out the specified branch.
    E.g. refs/remotes/origin/master
  • <tagName>
    This does not work since the tag will not be recognized as tag.
    Use refs/tags/<tagName> instead.
    E.g. git-2.3.0
  • refs/tags/<tagName>
    Tracks/checks out the specified tag.
    E.g. refs/tags/git-2.3.0
  • <commitId>
    Checks out the specified commit.
    E.g. 5062ac843f2b947733e6a3b105977056821bd352, 5062ac84, ...
  • ${ENV_VARIABLE}
    It is also possible to use environment variables. In this case the variables are evaluated and the result is used as described above.
    E.g. ${TREEISH}, refs/tags/${TAGNAME}, ...
  • <Wildcards>
    The syntax is of the form: REPOSITORYNAME/BRANCH. In addition, BRANCH is recognized as a shorthand of */BRANCH, '*' is recognized as a wildcard, and '**' is recognized as wildcard that includes the separator '/'. Therefore, origin/branches* would match origin/branches-foo but not origin/branches/foo, while origin/branches** would match both origin/branches-foo and origin/branches/foo.
  • :<regular expression>
    The syntax is of the form: :regexp. Regular expression syntax in branches to build will only build those branches whose names match the regular expression.
    Examples:
    • :^(?!(origin/prefix)).*
      • matches: origin or origin/master or origin/feature
      • does not match: origin/prefix or origin/prefix_123 or origin/prefix-abc
    • :origin/release-\d{8}
      • matches: origin/release-20150101
      • does not match: origin/release-2015010 or origin/release-201501011 or origin/release-20150101-something
    • :^(?!origin/master$|origin/develop$).*
      • matches: origin/branch1 or origin/branch-2 or origin/master123 or origin/develop-123
      • does not match: origin/master or origin/develop

Type:String
browser
Defines the repository browser that displays changes detected by the git plugin.
Nested choice of objects
assembla
repoUrl
Specify the root URL serving this repository (such as https://www.assembla.com/code/PROJECT/git/).
Type:String
bitbucketServer
repoUrl
Specify the Bitbucket Server root URL for this repository (such as https://bitbucket:7990/OWNER/REPO/).
Type:String
bitbucket
repoUrl
Specify the root URL serving this repository (such as https://bitbucket.org/OWNER/REPO/).
Type:String
cgit
repoUrl
Specify the root URL serving this repository (such as https://cgit.example.com:port/group/REPO/).
Type:String
fisheye
repoUrl
Specify the URL of this repository in FishEye (such as https://fisheye.example.com/browse/project/).
Type:String
gitblit
repoUrl
Specify the root URL serving this repository.
Type:String
projectName
Specify the name of the project in GitBlit.
Type:String
gitLab
repoUrl
Specify the root URL serving this repository (such as https://gitlab.com/username/repository/).
Type:String
version (optional)
Specify the major and minor version of GitLab you use (such as 9.1). If you don't specify a version, a modern version of GitLab (>= 8.0) is assumed.
Type:String
gitLabBrowser
Specify the HTTP URL for this project's GitLab page so that links to changes can be automatically generated by Jenkins. The URL needs to include the owner and project. If the GitLab server is https://gitLab.example.com then the URL for bob's skunkworks project might be https://gitLab.example.com/bob/skunkworks.
projectUrl
Specify the HTTP URL for this project's GitLab page. The URL needs to include the owner and project so, for example, if the GitLab server is https://gitLab.example.com then the URL for bob's skunkworks project might be https://gitLab.example.com/bob/skunkworks
Type:String
gitList
repoUrl
Specify the root URL serving this repository (such as https://gitlist.example.com/repo/).
Type:String
gitWeb
repoUrl
Specify the root URL serving this repository (such as https://github.com/jenkinsci/jenkins.git).
Type:String
github
repoUrl
Specify the HTTP URL for this repository's GitHub page (such as https://github.com/jquery/jquery).
Type:String
gitiles
repoUrl
Specify the root URL serving this repository (such as https://gwt.googlesource.com/gwt/).
Type:String
$class: 'GitoriousWeb'
repoUrl
Specify the root URL serving this repository (such as https://gitorious.org/gitorious/mainline).
Type:String
gogs
repoUrl
Specify the root URL serving this repository (such as https://gogs.example.com/username/some-repo-url.git).
Type:String
kiln
repoUrl
Specify the root URL serving this repository (such as https://khanacademy.kilnhg.com/Code/Website/Group/webapp).
Type:String
phabricator
repoUrl
Specify the phabricator instance root URL (such as https://phabricator.example.com).
Type:String
repo
Specify the repository name in phabricator (such as the foo part of phabricator.example.com/diffusion/foo/browse).
Type:String
redmine
repoUrl
Specify the root URL serving this repository (such as https://redmine.example.com/PATH/projects/PROJECT/repository).
Type:String
rhodeCode
repoUrl
Specify the HTTP URL for this repository's RhodeCode page (such as https://rhodecode.example.com/projects/PROJECT/repos/REPO/).
Type:String
$class: 'Stash'
repoUrl
Specify the HTTP URL for this repository's Stash page (such as https://stash.example.com/projects/PROJECT/repos/REPO/).
Type:String
teamFoundation
repoUrl
Either the name of the remote whose URL should be used, or the URL of this module in TFS (such as https://tfs.example.com/tfs/PROJECT/_git/REPO/). If empty (default), the URL of the "origin" repository is used.

If TFS is also used as the repository server, this can usually be left blank.

Type:String
viewgit
repoUrl
Specify the root URL serving this repository (such as https://git.example.com/viewgit/).
Type:String
projectName
Specify the name of the project in ViewGit (e.g. scripts, scuttle etc. from https://code.fealdia.org/viewgit/).
Type:String
gitTool

Name of the git tool to be used for this job. Git tool names are defined in "Global Tool Configuration".

Type:String
extensions

Extensions add new behavior or modify existing plugin behavior for different uses. Extensions help users more precisely tune plugin behavior to meet their needs.

Extensions include:

  • Clone extensions modify the git operations that retrieve remote changes into the agent workspace. The extensions can adjust the amount of history retrieved, how long the retrieval is allowed to run, and other retrieval details.
  • Checkout extensions modify the git operations that place files in the workspace from the git repository on the agent. The extensions can adjust the maximum duration of the checkout operation, the use and behavior of git submodules, the location of the workspace on the disc, and more.
  • Changelog extensions adapt the source code difference calculations for different cases.
  • Tagging extensions allow the plugin to apply tags in the current workspace.
  • Build initiation extensions control the conditions that start a build. They can ignore notifications of a change or force a deeper evaluation of the commits when polling.
  • Merge extensions can optionally merge changes from other branches into the current branch of the agent workspace. They control the source branch for the merge and the options applied to the merge.

Array/List:
Nested choice of objects
authorInChangelog
The default behavior is to use the Git commit's "Committer" value in Jenkins' build changesets. If this option is selected, the Git commit's "Author" value would be used instead.
$class: 'BuildChooserSetting'
When you are interested in using a job to build multiple heads (most typically multiple branches), you can choose how Jenkins choose what branches to build in what order.

This extension point in Jenkins is used by many other plugins to control the job to build specific commits. When you activate those plugins, you may see them installing a custom strategy here.

buildChooser
Nested choice of objects
$class: 'AncestryBuildChooser'
maximumAgeInDays
Type:int
ancestorCommitSha1
Type:String
$class: 'DefaultBuildChooser'
$class: 'InverseBuildChooser'
buildSingleRevisionOnly
Disable scheduling for multiple candidate revisions.
If we have 3 branches:
----A--.---.--- B
         \-----C
jenkins would try to build (B) and (C).
This behaviour disables this and only builds one of them.
It is helpful to reduce the load of the Jenkins infrastructure when the SCM system like Bitbucket or GitHub should decide what commits to build.
changelogToBranch
This method calculates the changelog against the specified branch.
options
changelogBase
compareRemote
Name of the repository, such as origin, that contains the branch you specify below.
Type:String
compareTarget
The name of the branch within the named repository to compare against.
Type:String
checkoutOption
timeout
Specify a timeout (in minutes) for checkout.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
cleanBeforeCheckout
Clean up the workspace before every checkout by deleting all untracked files and directories, including those which are specified in .gitignore. It also resets all tracked files to their versioned state. This ensures that the workspace is in the same state as if you cloned and checked out in a brand-new empty directory, and ensures that your build is not affected by the files generated by the previous build.
deleteUntrackedNestedRepositories (optional)
Deletes untracked submodules and any other subdirectories which contain .git directories.
Type:boolean
cleanAfterCheckout
Clean up the workspace after every checkout by deleting all untracked files and directories, including those which are specified in .gitignore. It also resets all tracked files to their versioned state. This ensures that the workspace is in the same state as if you cloned and checked out in a brand-new empty directory, and ensures that your build is not affected by the files generated by the previous build.
deleteUntrackedNestedRepositories (optional)
Deletes untracked submodules and any other subdirectories which contain .git directories.
Type:boolean
cloneOption
shallow
Perform shallow clone, so that git will not download the history of the project, saving time and disk space when you just want to access the latest version of a repository.
Type:boolean
noTags
Deselect this to perform a clone without tags, saving time and disk space when you just want to access what is specified by the refspec.
Type:boolean
reference
Specify a folder containing a repository that will be used by Git as a reference during clone operations.
This option will be ignored if the folder is not available on the controller or agent where the clone is being executed.
Type:String
timeout
Specify a timeout (in minutes) for clone and fetch operations.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
depth (optional)
Set shallow clone depth, so that git will only download recent history of the project, saving time and disk space when you just want to access the latest commits of a repository.
Type:int
honorRefspec (optional)
Perform initial clone using the refspec defined for the repository. This can save time, data transfer and disk space when you only need to access the references specified by the refspec.
Type:boolean
$class: 'DisableRemotePoll'
Git plugin uses git ls-remote polling mechanism by default when configured with a single branch (no wildcards!). This compare the latest built commit SHA with the remote branch without cloning a local copy of the repo.

If you don't want to / can't use this.

If this option is selected, polling will require a workspace and might trigger unwanted builds (see JENKINS-10131).
lfs
Enable git large file support for the workspace by pulling large files after the checkout completes. Requires that the controller and each agent performing an LFS checkout have installed `git lfs`.
$class: 'IgnoreNotifyCommit'
If checked, this repository will be ignored when the notifyCommit-URL is accessed regardless of if the repository matches or not.
localBranch
If given, checkout the revision to build as HEAD on this branch.

If selected, and its value is an empty string or "**", then the branch name is computed from the remote branch without the origin. In that case, a remote branch origin/master will be checked out to a local branch named master, and a remote branch origin/develop/new-feature will be checked out to a local branch named develop/newfeature.

Please note that this has not been tested with submodules.

localBranch
Type:String
$class: 'MessageExclusion'
excludedMessage
If set, and Jenkins is set to poll for changes, Jenkins will ignore any revisions committed with message matched to Pattern when determining if a build needs to be triggered. This can be used to exclude commits done by the build itself from triggering another build, assuming the build server commits the change with a distinct message.

Exclusion uses Pattern matching

.*\[maven-release-plugin\].*
The example above illustrates that if only revisions with "[maven-release-plugin]" message in first comment line have been committed to the SCM a build will not occur.

You can create more complex patterns using embedded flag expressions.

(?s).*FOO.*
This example will search FOO message in all comment lines.
Type:String
$class: 'PathRestriction'
If set, and Jenkins is set to poll for changes, Jenkins will pay attention to included and/or excluded files and/or folders when determining if a build needs to be triggered.

Using this behaviour will preclude the faster git ls-remote polling mechanism, forcing polling to require a workspace thus sometimes triggering unwanted builds, as if you had selected the Force polling using workspace extension as well.

includedRegions
Each inclusion uses java regular expression pattern matching, and must be separated by a new line. An empty list implies that everything is included.

    myapp/src/main/web/.*\.html
    myapp/src/main/web/.*\.jpeg
    myapp/src/main/web/.*\.gif
  
The example above illustrates that a build will only occur, if html/jpeg/gif files have been committed to the SCM. Exclusions take precedence over inclusions, if there is an overlap between included and excluded regions.
Type:String
excludedRegions
Each exclusion uses java regular expression pattern matching, and must be separated by a new line.

    myapp/src/main/web/.*\.html
    myapp/src/main/web/.*\.jpeg
    myapp/src/main/web/.*\.gif
  
The example above illustrates that if only html/jpeg/gif files have been committed to the SCM a build will not occur.
Type:String
perBuildTag
Create a tag in the workspace for every build to unambiguously mark the commit that was built. You can combine this with Git publisher to push the tags to the remote repository.
$class: 'PreBuildMerge'
These options allow you to perform a merge to a particular branch before building. For example, you could specify an integration branch to be built, and to merge to master. In this scenario, on every change of integration, Jenkins will perform a merge with the master branch, and try to perform a build if the merge is successful. It then may push the merge back to the remote repository if the Git Push post-build action is selected.
options
Nested object
mergeTarget
The name of the branch within the named repository to merge to, such as master.
Type:String
fastForwardMode (optional)
Merge fast-forward mode selection.
The default, --ff, gracefully falls back to a merge commit when required.
For more information, see the Git Merge Documentation
Values:
FF
FF_ONLY
NO_FF
mergeRemote (optional)
Name of the repository, such as origin, that contains the branch you specify below. If left blank, it'll default to the name of the first repository configured above.
Type:String
mergeStrategy (optional)
Merge strategy selection. This feature is not fully implemented in JGIT.
Values:
DEFAULT
RESOLVE
RECURSIVE
OCTOPUS
OURS
SUBTREE
RECURSIVE_THEIRS
pruneStaleBranch
Run "git remote prune" for each remote, to prune obsolete local branches.
pruneTags
pruneTags
Type:boolean
$class: 'RelativeTargetDirectory'
relativeTargetDir
Specify a local directory (relative to the workspace root) where the Git repository will be checked out. If left empty, the workspace root itself will be used.

This extension should not be used in Jenkins Pipeline (either declarative or scripted). Jenkins Pipeline already provides standard techniques for checkout to a subdirectory. Use ws and dir in Jenkins Pipeline rather than this extension.

Type:String
$class: 'ScmName'

Unique name for this SCM. Needed when using Git within the Multi SCM plugin.

name
Type:String
$class: 'SparseCheckoutPaths'

Specify the paths that you'd like to sparse checkout. This may be used for saving space (Think about a reference repository). Be sure to use a recent version of Git, at least above 1.7.10

sparseCheckoutPaths
Array/List:
Nested object
path
Type:String
submodule
depth (optional)
Set shallow clone depth, so that git will only download recent history of the project, saving time and disk space when you just want to access the latest commits of a repository.
Type:int
disableSubmodules (optional)
By disabling support for submodules you can still keep using basic git plugin functionality and just have Jenkins to ignore submodules completely as if they didn't exist.
Type:boolean
parentCredentials (optional)
Use credentials from the default remote of the parent project.
Type:boolean
recursiveSubmodules (optional)
Retrieve all submodules recursively (uses '--recursive' option which requires git>=1.6.5)
Type:boolean
reference (optional)
Specify a folder containing a repository that will be used by Git as a reference during clone operations.
This option will be ignored if the folder is not available on the controller or agent where the clone is being executed.
To prepare a reference folder with multiple subprojects, create a bare git repository and add all the remote urls then perform a fetch:
  git init --bare
  git remote add SubProject1 https://gitrepo.com/subproject1
  git remote add SubProject2 https://gitrepo.com/subproject2
  git fetch --all
  
Type:String
shallow (optional)
Perform shallow clone, so that git will not download the history of the project, saving time and disk space when you just want to access the latest version of a repository.
Type:boolean
threads (optional)
Specify the number of threads that will be used to update submodules.
If unspecified, the command line git default thread count is used.
Type:int
timeout (optional)
Specify a timeout (in minutes) for submodules operations.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
trackingSubmodules (optional)
Retrieve the tip of the configured branch in .gitmodules (Uses '--remote' option which requires git>=1.8.2)
Type:boolean
$class: 'UserExclusion'
excludedUsers
If set, and Jenkins is set to poll for changes, Jenkins will ignore any revisions committed by users in this list when determining if a build needs to be triggered. This can be used to exclude commits done by the build itself from triggering another build, assuming the build server commits the change with a distinct SCM user.

Using this behaviour will preclude the faster git ls-remote polling mechanism, forcing polling to require a workspace thus sometimes triggering unwanted builds, as if you had selected the Force polling using workspace extension as well.

Each exclusion uses exact string comparison and must be separated by a new line. User names are only excluded if they exactly match one of the names in this list.

auto_build_user
The example above illustrates that if only revisions by "auto_build_user" have been committed to the SCM a build will not occur.
Type:String
$class: 'UserIdentity'
name

If given, "GIT_COMMITTER_NAME=[this]" and "GIT_AUTHOR_NAME=[this]" are set for builds. This overrides whatever is in the global settings.

Type:String
email

If given, "GIT_COMMITTER_EMAIL=[this]" and "GIT_AUTHOR_EMAIL=[this]" are set for builds. This overrides whatever is in the global settings.

Type:String
$class: 'WipeWorkspace'
Delete the contents of the workspace before building, ensuring a fully fresh workspace.
doGenerateSubmoduleConfigurations (optional)

Removed facility that was intended to test combinations of git submodule versions. Removed in git plugin 4.6.0. Ignores the user provided value and always uses false as its value.

Type:boolean
submoduleCfg (optional)

Removed facility that was intended to test combinations of git submodule versions. Removed in git plugin 4.6.0. Ignores the user provided value(s) and always uses empty values.

Array/List:
Nested object
submoduleName

Removed in git plugin 4.6.0.

Type:String
branches

Removed in git plugin 4.6.0.

Array/List:
Type:String
none
clone (optional)
If checked, every build performs a fresh clone of the SCM rather than locking and updating a common copy. No changelog will be computed. For Git, you are advised to add Advanced clone behaviors and then check Shallow clone and Honor refspec on initial clone and uncheck Fetch tags to make the clone much faster. You may still enable Cache fetched versions on controller for quick retrieval if you prefer.
Type:boolean
libraryPath (optional)
A relative path from the root of the SCM to the root of the library. Leave this field blank if the root of the library is the root of the SCM. Note that ".." is not permitted as a path component to avoid security issues.
Type:String
modernSCM
scm
Nested choice of objects
github
repoOwner

Specify the name of the GitHub Organization or GitHub User Account.

Type:String
repository
The repository to scan.
Type:String
repositoryUrl

Specify the HTTPS URL of the GitHub Organization / User Account and repository.

GitHub examples:

  • https://github.com/jenkinsci/github-branch-source-plugin
  • https://github.com/jenkinsci/github-branch-source-plugin.git

GitHub Enterprise examples:

  • https://myccompany.github.com/jenkinsci/github-branch-source-plugin
  • https://myccompany.github.com/jenkinsci/github-branch-source-plugin.git

Type:String
configuredByUrl
Type:boolean
apiUri (optional)
The server to connect to. The list of servers is configured in the Manage Jenkins » Configure System » GitHub Enterprise Servers screen.
Type:String
buildForkPRHead (optional)
Type:boolean
buildForkPRMerge (optional)
Type:boolean
buildOriginBranch (optional)
Type:boolean
buildOriginBranchWithPR (optional)
Type:boolean
buildOriginPRHead (optional)
Type:boolean
buildOriginPRMerge (optional)
Type:boolean
credentialsId (optional)

Credentials used to scan branches and pull requests, check out sources and mark commit statuses.

Note that only "username with password" credentials are supported. Existing credentials of other kinds will be filtered out. This is because Jenkins uses the GitHub API, which does not support other ways of authentication.

If none is given, only the public repositories will be scanned, and commit status will not be set on GitHub.

If your organization contains private repositories, then you need to specify a credential from a user who has access to those repositories. This is done by creating a "username with password" credential where the password is GitHub personal access tokens. The necessary scope is "repo".

Type:String
excludes (optional)
Type:String
id (optional)
Type:String
includes (optional)
Type:String
traits (optional)
The behaviours control what is discovered from the GitHub repository. The behaviours are grouped into a number of categories:
Within repository
These behaviours determine what gets discovered. If you do not configure at least one discovery behaviour then nothing will be found!
General
These behaviours affect the configuration of each discovered branch / pull request.
Array/List:
Nested choice of objects
authorInChangelog
buildStatusNameCustomPart
Customize the pipeline status name used by Jenkins
buildStatusNameCustomPart (optional)
Enter a string to customize the status/context name for status updates published to GitLab. For a branch build the default name would be 'jenkinsci/branch'. With the buildStatusNameCustomPart 'custom' the name would be 'jenkinsci/custom/branch'. This allows to have multiple GitLab-Branch-Sources for the same GitLab-project configured.
Type:String
buildStatusNameOverwrite (optional)
Overwrites the build status name including the jenkinsci default part.
Instead of 'jenkinsci/custom/branch' just 'custom/branch'.
Type:boolean
ignoreTypeInStatusName (optional)
Type:boolean
checkoutOption
extension
checkoutOption
timeout
Specify a timeout (in minutes) for checkout.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
cleanAfterCheckout
extension
cleanAfterCheckout
Clean up the workspace after every checkout by deleting all untracked files and directories, including those which are specified in .gitignore. It also resets all tracked files to their versioned state. This ensures that the workspace is in the same state as if you cloned and checked out in a brand-new empty directory, and ensures that your build is not affected by the files generated by the previous build.
deleteUntrackedNestedRepositories (optional)
Deletes untracked submodules and any other subdirectories which contain .git directories.
Type:boolean
cleanBeforeCheckout
extension
cleanBeforeCheckout
Clean up the workspace before every checkout by deleting all untracked files and directories, including those which are specified in .gitignore. It also resets all tracked files to their versioned state. This ensures that the workspace is in the same state as if you cloned and checked out in a brand-new empty directory, and ensures that your build is not affected by the files generated by the previous build.
deleteUntrackedNestedRepositories (optional)
Deletes untracked submodules and any other subdirectories which contain .git directories.
Type:boolean
cloneOption
extension
cloneOption
shallow
Perform shallow clone, so that git will not download the history of the project, saving time and disk space when you just want to access the latest version of a repository.
Type:boolean
noTags
Deselect this to perform a clone without tags, saving time and disk space when you just want to access what is specified by the refspec.
Type:boolean
reference
Specify a folder containing a repository that will be used by Git as a reference during clone operations.
This option will be ignored if the folder is not available on the controller or agent where the clone is being executed.
Type:String
timeout
Specify a timeout (in minutes) for clone and fetch operations.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
depth (optional)
Set shallow clone depth, so that git will only download recent history of the project, saving time and disk space when you just want to access the latest commits of a repository.
Type:int
honorRefspec (optional)
Perform initial clone using the refspec defined for the repository. This can save time, data transfer and disk space when you only need to access the references specified by the refspec.
Type:boolean
discoverOtherRefs
Discovers other specified refs on the repository.
ref

The pattern under /refs on the remote repository to discover, can contain a wildcard.
Example: test/*/merged

Type:String
nameMapping (optional)

Mapping for how the ref can be named in for example the @Library.
Example: test-@{1}
Where @{1} replaces the first wildcard in the ref when discovered.

By default it will be "namespace_before_wildcard-@{1}". E.g. if ref is "test/*/merged" the default mapping would be "test-@{1}".

Type:String
gitLabForkDiscovery
Discovers merge requests where the origin project is a fork of the target project.
strategyId
Determines how merge requests are discovered:
Merging the merge request with the current target branch revision
Discover each merge request once with the discovered revision corresponding to the result of merging with the current revision of the target branch
The current merge request revision
Discover each merge request once with the discovered revision corresponding to the merge request head revision without merging
Both the current merge request revision and the merge request merged with the current target branch revision
Discover each merge request twice. The first discovered revision corresponds to the result of merging with the current revision of the target branch in each scan. The second parallel discovered revision corresponds to the merge request head revision without merging
Type:int
trust

One of the great powers of merge requests is that anyone with read access to a project can fork it, commit some changes to their fork and then create a merge request against the original project with their changes. There are some files stored in source control that are important. For example, a Jenkinsfile may contain configuration details to sandbox merge requests in order to mitigate against malicious merge requests. In order to protect against a malicious merge request itself modifying the Jenkinsfile to remove the protections, you can define the trust policy for merge requests from forks.

Other plugins can extend the available trust policies. The default policies are:

Nobody
Merge requests from forks will all be treated as untrusted. This means that where Jenkins requires a trusted file (e.g. Jenkinsfile) the contents of that file will be retrieved from the target branch on the origin project and not from the merge request branch on the fork project.
Members
Merge requests from collaborators to the origin project will be treated as trusted, all other merge requests from fork repositories will be treated as untrusted. Note that if credentials used by Jenkins for scanning the project does not have permission to query the list of contributors to the origin project then only the origin account will be treated as trusted - i.e. this will fall back to Nobody.
Trusted Members
Merge requests forks will be treated as trusted if and only if the fork owner has either Developer or Maintainer or Owner Access Level in the origin project. This is the recommended policy.
Everyone
All merge requests from forks will be treated as trusted. NOTE: this option can be dangerous if used on a public project hosted on a GitLab instance.
java.lang.UnsupportedOperationException: do not know how to categorize attributes of type jenkins.scm.api.trait.SCMHeadAuthority<? super io.jenkins.plugins.gitlabbranchsource.GitLabSCMSourceRequest, ? extends jenkins.scm.api.mixin.ChangeRequestSCMHead2, ? extends jenkins.scm.api.SCMRevision>
buildMRForksNotMirror (optional)
Add discovery of merge requests where the origin project is a fork of a certain project, but the target project is not the original forked project. To be used in case one has a GitLab project which is a fork of another project from another team, in order to isolate artefacts and allow an MR flow. This means using MRs inside that fork from branches in the fork back to the fork's default branch. (Implements https://github.com/jenkinsci/gitlab-branch-source-plugin/issues/167)
Type:boolean
gitHubForkDiscovery
Discovers pull requests where the origin repository is a fork of the target repository.
strategyId
Determines how pull requests are discovered:
Merging the pull request with the current target branch revision
Discover each pull request once with the discovered revision corresponding to the result of merging with the current revision of the target branch. Note that pushes to the target branch will result in new pull request builds.
The current pull request revision
Discover each pull request once with the discovered revision corresponding to the pull request head revision without merging.
Both the current pull request revision and the pull request merged with the current target branch revision
Discover each pull request twice. The first discovered revision corresponds to the result of merging with the current revision of the target branch in each scan. The second parallel discovered revision corresponds to the pull request head revision without merging.
Type:int
trust

One of the great powers of pull requests is that anyone with read access to a repository can fork it, commit some changes to their fork and then create a pull request against the original repository with their changes. There are some files stored in source control that are important. For example, a Jenkinsfile may contain configuration details to sandbox pull requests in order to mitigate against malicious pull requests. In order to protect against a malicious pull request itself modifying the Jenkinsfile to remove the protections, you can define the trust policy for pull requests from forks.

Other plugins can extend the available trust policies. The default policies are:

Nobody
Pull requests from forks will all be treated as untrusted. This means that where Jenkins requires a trusted file (e.g. Jenkinsfile) the contents of that file will be retrieved from the target branch on the origin repository and not from the pull request branch on the fork repository.
Collaborators
Pull requests from collaborators to the origin repository will be treated as trusted, all other pull requests from fork repositories will be treated as untrusted. Note that if credentials used by Jenkins for scanning the repository does not have permission to query the list of collaborators to the origin repository then only the origin account will be treated as trusted - i.e. this will fall back to Nobody. NOTE: all collaborators are trusted, even if they are only members of a team with read permission.
Everyone
All pull requests from forks will be treated as trusted. NOTE: this option can be dangerous if used on a public repository hosted on GitHub.
From users with Admin or Write permission
Pull requests forks will be treated as trusted if and only if the fork owner has either Admin or Write permissions on the origin repository. This is the recommended policy. Note that this strategy requires the Review a user's permission level API, as a result on GitHub Enterprise Server versions before 2.12 this is the same as trusting Nobody.
Nested choice of objects
gitHubTrustContributors
gitHubTrustEveryone
gitHubTrustNobody
gitHubTrustPermissions
browser
browser
Nested choice of objects
assembla
repoUrl
Specify the root URL serving this repository (such as https://www.assembla.com/code/PROJECT/git/).
Type:String
bitbucketServer
repoUrl
Specify the Bitbucket Server root URL for this repository (such as https://bitbucket:7990/OWNER/REPO/).
Type:String
bitbucket
repoUrl
Specify the root URL serving this repository (such as https://bitbucket.org/OWNER/REPO/).
Type:String
cgit
repoUrl
Specify the root URL serving this repository (such as https://cgit.example.com:port/group/REPO/).
Type:String
fisheye
repoUrl
Specify the URL of this repository in FishEye (such as https://fisheye.example.com/browse/project/).
Type:String
gitblit
repoUrl
Specify the root URL serving this repository.
Type:String
projectName
Specify the name of the project in GitBlit.
Type:String
gitLab
repoUrl
Specify the root URL serving this repository (such as https://gitlab.com/username/repository/).
Type:String
version (optional)
Specify the major and minor version of GitLab you use (such as 9.1). If you don't specify a version, a modern version of GitLab (>= 8.0) is assumed.
Type:String
gitLabBrowser
Specify the HTTP URL for this project's GitLab page so that links to changes can be automatically generated by Jenkins. The URL needs to include the owner and project. If the GitLab server is https://gitLab.example.com then the URL for bob's skunkworks project might be https://gitLab.example.com/bob/skunkworks.
projectUrl
Specify the HTTP URL for this project's GitLab page. The URL needs to include the owner and project so, for example, if the GitLab server is https://gitLab.example.com then the URL for bob's skunkworks project might be https://gitLab.example.com/bob/skunkworks
Type:String
gitList
repoUrl
Specify the root URL serving this repository (such as https://gitlist.example.com/repo/).
Type:String
gitWeb
repoUrl
Specify the root URL serving this repository (such as https://github.com/jenkinsci/jenkins.git).
Type:String
github
repoUrl
Specify the HTTP URL for this repository's GitHub page (such as https://github.com/jquery/jquery).
Type:String
gitiles
repoUrl
Specify the root URL serving this repository (such as https://gwt.googlesource.com/gwt/).
Type:String
$class: 'GitoriousWeb'
repoUrl
Specify the root URL serving this repository (such as https://gitorious.org/gitorious/mainline).
Type:String
gogs
repoUrl
Specify the root URL serving this repository (such as https://gogs.example.com/username/some-repo-url.git).
Type:String
kiln
repoUrl
Specify the root URL serving this repository (such as https://khanacademy.kilnhg.com/Code/Website/Group/webapp).
Type:String
phabricator
repoUrl
Specify the phabricator instance root URL (such as https://phabricator.example.com).
Type:String
repo
Specify the repository name in phabricator (such as the foo part of phabricator.example.com/diffusion/foo/browse).
Type:String
redmine
repoUrl
Specify the root URL serving this repository (such as https://redmine.example.com/PATH/projects/PROJECT/repository).
Type:String
rhodeCode
repoUrl
Specify the HTTP URL for this repository's RhodeCode page (such as https://rhodecode.example.com/projects/PROJECT/repos/REPO/).
Type:String
$class: 'Stash'
repoUrl
Specify the HTTP URL for this repository's Stash page (such as https://stash.example.com/projects/PROJECT/repos/REPO/).
Type:String
teamFoundation
repoUrl
Either the name of the remote whose URL should be used, or the URL of this module in TFS (such as https://tfs.example.com/tfs/PROJECT/_git/REPO/). If empty (default), the URL of the "origin" repository is used.

If TFS is also used as the repository server, this can usually be left blank.

Type:String
viewgit
repoUrl
Specify the root URL serving this repository (such as https://git.example.com/viewgit/).
Type:String
projectName
Specify the name of the project in ViewGit (e.g. scripts, scuttle etc. from https://code.fealdia.org/viewgit/).
Type:String
lfs
gitlabAvatar
disableProjectAvatar (optional)
Due to a GitLab bug, sometimes it is not possible to GitLab API to fetch GitLab Avatar for private projects or when the api doesn't have token access. You may choose to skip avatar for projects if you want to avoid broken or self generated avatars.
Type:boolean
gitlabMarkUnstableAsSuccess
markUnstableAsSuccess (optional)
Type:boolean
gitlabSkipNotifications
gitTool
gitTool
Type:String
gitLabHookRegistration
webHookMode
Type:String
systemHookMode
Type:String
gitHubIgnoreDraftPullRequestFilter
ignoreOnPush
localBranch
logComment
logSuccess (optional)
Sometimes the user doesn't want to log the builds that succeeded. The trait only enable logging of failed/aborted builds by default. Select this option to include logging of successful builds as well.
Type:boolean
sudoUser (optional)
Enter a sudo username of the user you want to comment as on GitLab Server. Remember the token specified should have api and sudo access both (which can only be created by your GitLab Server Admin). It is recommended to create a dummy user in your GitLab Server with an appropriate username like `jenkinsadmin` etc. Leave empty if you want use the owner of the project as the commenter.
Type:String
multiBranchProjectDisplayNaming
Some branch source plugins provide additional information about discovered branches like a title or subject of merge or change requests.
With this trait, that additional information can be used for the job display names.
Note: Job display name changes do not trigger builds.
displayNamingStrategy
The different strategies:
  • Job display name with fallback to name:
    Uses the branch source plugin's display name for the PR instead of the raw name
    Value for configuration-as-code: OBJECT_DISPLAY_NAME

  • Name and, if available, display name:
    Joins the raw name and the branch source plugin's display name
    Value for configuration-as-code: RAW_AND_OBJECT_DISPLAY_NAME

Values:
OBJECT_DISPLAY_NAME
RAW_AND_OBJECT_DISPLAY_NAME
gitLabOriginDiscovery
Discovers merge requests where the origin project is the same as the target project.
strategyId
Determines how merge requests are discovered:
Merging the merge request with the current target branch revision
Discover each merge request once with the discovered revision corresponding to the result of merging with the current revision of the target branch
The current merge request revision
Discover each merge request once with the discovered revision corresponding to the merge request head revision without merging
Both the current merge request revision and the merge request merged with the current target branch revision
Discover each merge request twice. The first discovered revision corresponds to the result of merging with the current revision of the target branch in each scan. The second parallel discovered revision corresponds to the merge request head revision without merging
Type:int
gitHubPullRequestDiscovery
Discovers pull requests where the origin repository is the same as the target repository.
strategyId
Determines how pull requests are discovered:
Merging the pull request with the current target branch revision
Discover each pull request once with the discovered revision corresponding to the result of merging with the current revision of the target branch. Note that pushes to the target branch will result in new pull request builds.
The current pull request revision
Discover each pull request once with the discovered revision corresponding to the pull request head revision without merging.
Both the current pull request revision and the pull request merged with the current target branch revision
Discover each pull request twice. The first discovered revision corresponds to the result of merging with the current revision of the target branch in each scan. The second parallel discovered revision corresponds to the pull request head revision without merging.
Type:int
pruneStaleBranch
pruneStaleTag
refSpecs
templates
Array/List:
Nested object
value
A ref spec to fetch. Any occurrences of @{remote} will be replaced by the remote name (which defaults to origin) before use.
Type:String
headRegexFilter
regex
A Java regular expression to restrict the names. Names that do not match the supplied regular expression will be ignored.
NOTE: this filter will be applied to all branch like things, including change requests
Type:String
remoteName
remoteName
Type:String
sparseCheckoutPaths
extension
Nested object

Specify the paths that you'd like to sparse checkout. This may be used for saving space (Think about a reference repository). Be sure to use a recent version of Git, at least above 1.7.10

sparseCheckoutPaths
Array/List:
Nested object
path
Type:String
submoduleOption
extension
submodule
depth (optional)
Set shallow clone depth, so that git will only download recent history of the project, saving time and disk space when you just want to access the latest commits of a repository.
Type:int
disableSubmodules (optional)
By disabling support for submodules you can still keep using basic git plugin functionality and just have Jenkins to ignore submodules completely as if they didn't exist.
Type:boolean
parentCredentials (optional)
Use credentials from the default remote of the parent project.
Type:boolean
recursiveSubmodules (optional)
Retrieve all submodules recursively (uses '--recursive' option which requires git>=1.6.5)
Type:boolean
reference (optional)
Specify a folder containing a repository that will be used by Git as a reference during clone operations.
This option will be ignored if the folder is not available on the controller or agent where the clone is being executed.
To prepare a reference folder with multiple subprojects, create a bare git repository and add all the remote urls then perform a fetch:
  git init --bare
  git remote add SubProject1 https://gitrepo.com/subproject1
  git remote add SubProject2 https://gitrepo.com/subproject2
  git fetch --all
  
Type:String
shallow (optional)
Perform shallow clone, so that git will not download the history of the project, saving time and disk space when you just want to access the latest version of a repository.
Type:boolean
threads (optional)
Specify the number of threads that will be used to update submodules.
If unspecified, the command line git default thread count is used.
Type:int
timeout (optional)
Specify a timeout (in minutes) for submodules operations.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
trackingSubmodules (optional)
Retrieve the tip of the configured branch in .gitmodules (Uses '--remote' option which requires git>=1.8.2)
Type:boolean
mrTriggerComment
commentBody
Add comment body you want to use to instruct Jenkins CI to rebuild the MR
Type:String
onlyTrustedMembersCanTrigger
Type:boolean
userIdentity
extension
Nested object
name

If given, "GIT_COMMITTER_NAME=[this]" and "GIT_AUTHOR_NAME=[this]" are set for builds. This overrides whatever is in the global settings.

Type:String
email

If given, "GIT_COMMITTER_EMAIL=[this]" and "GIT_AUTHOR_EMAIL=[this]" are set for builds. This overrides whatever is in the global settings.

Type:String
WebhookListenerBuildConditionsTrait
alwaysBuildMROpen (optional)
Type:boolean
alwaysBuildMRReOpen (optional)
Type:boolean
alwaysIgnoreMRApproval (optional)
Type:boolean
alwaysIgnoreMRApproved (optional)
Type:boolean
alwaysIgnoreMRUnApproval (optional)
Type:boolean
alwaysIgnoreMRUnApproved (optional)
Type:boolean
alwaysIgnoreMRWorkInProgress (optional)
Type:boolean
alwaysIgnoreNonCodeRelatedUpdates (optional)
GitLab will send a webhook to Jenkins when there are updates to the MR including title changes, labels removed/added, etc. Enabling this option will prevent a build running if the cause was one of these updates. Note: these settings do not have any impact on build from comment settings.
Type:boolean
headWildcardFilter
includes
Space-separated list of name patterns to consider. You may use * as a wildcard; for example: master release*
NOTE: this filter will be applied to all branch like things, including change requests
Type:String
excludes
Space-separated list of name patterns to ignore even if matched by the includes list. For example: release alpha-* beta-*
NOTE: this filter will be applied to all branch like things, including change requests
Type:String
$class: 'WipeWorkspaceTrait'
gitLabBranchDiscovery
Discovers branches on the repository.
strategyId
Determines which branches are discovered.
Only branches that are not also filed as MRs
If you are discovering origin merge requests, it may not make sense to discover the same changes both as a merge request and as a branch.
Only branches that are also filed as MRs
This option exists to preserve legacy behaviour when upgrading from older versions of the plugin. NOTE: If you have an actual use case for this option please file a merge request against this text.
All branches
Ignores whether the branch is also filed as a merge request and instead discovers all branches on the origin project.
Type:int
gitLabSshCheckout
By default the discovered branches / merge requests will all use the same username / password credentials that were used for discovery when checking out sources. This means that the checkout will be using the https:// protocol for the Git repository.

This behaviour allows you to select the SSH private key to be used for checking out sources, which will consequently force the checkout to use the ssh:// protocol.

credentialsId
Credentials used to check out sources. Must be a SSH key based credential.
Type:String
gitLabTagDiscovery
gitBranchDiscovery
Discovers branches on the repository.
gitTagDiscovery
Discovers tags on the repository.
gitHubBranchDiscovery
Discovers branches on the repository.
strategyId
Determines which branches are discovered.
Exclude branches that are also filed as PRs
If you are discovering origin pull requests, you may not want to also build the source branches for those pull requests.
Only branches that are also filed as PRs
Similar to discovering origin pull requests, but discovers the branch rather than the pull request. This means env.GIT_BRANCH will be set to the branch name rather than PR-#. Also, status notifications for these builds will only be applied to the commit and not to the pull request.
All branches
Ignores whether the branch is also filed as a pull request and instead discovers all branches on the origin repository.
Type:int
gitHubSshCheckout
By default the discovered branches / pull requests will all use the same username / password credentials that were used for discovery when checking out sources. This means that the checkout will be using the https:// protocol for the Git repository.

This behaviour allows you to select the SSH private key to be used for checking out sources, which will consequently force the checkout to use the ssh:// protocol.

credentialsId
Credentials used to check out sources. Must be a SSH key based credential.
Type:String
gitHubTagDiscovery
Discovers tags on the repository.
gitlab
serverName
Select the GitLab Server where you want the projects to be discovered from.
Type:String
projectOwner
Specify the namespace which owns your projects. It can be a user, a group or a subgroup with full path. E.g: If you want projects from subgroup `a` inside group `b`, then `Owner` should be b/a
Type:String
projectPath
Select the project on which you want to perform the Multibranch Pipeline Job.
Type:String
credentialsId (optional)
Checkout credentials is only needed for private projects. Add `SSHPrivateKey` or `Username/Password` to checkout over SSH remote or HTTPS remote respectively.
Type:String
id (optional)
Type:String
projectId (optional)
Type:long
traits (optional)
Array/List:
Nested choice of objects
authorInChangelog
buildStatusNameCustomPart
Customize the pipeline status name used by Jenkins
buildStatusNameCustomPart (optional)
Enter a string to customize the status/context name for status updates published to GitLab. For a branch build the default name would be 'jenkinsci/branch'. With the buildStatusNameCustomPart 'custom' the name would be 'jenkinsci/custom/branch'. This allows to have multiple GitLab-Branch-Sources for the same GitLab-project configured.
Type:String
buildStatusNameOverwrite (optional)
Overwrites the build status name including the jenkinsci default part.
Instead of 'jenkinsci/custom/branch' just 'custom/branch'.
Type:boolean
ignoreTypeInStatusName (optional)
Type:boolean
checkoutOption
extension
checkoutOption
timeout
Specify a timeout (in minutes) for checkout.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
cleanAfterCheckout
extension
cleanAfterCheckout
Clean up the workspace after every checkout by deleting all untracked files and directories, including those which are specified in .gitignore. It also resets all tracked files to their versioned state. This ensures that the workspace is in the same state as if you cloned and checked out in a brand-new empty directory, and ensures that your build is not affected by the files generated by the previous build.
deleteUntrackedNestedRepositories (optional)
Deletes untracked submodules and any other subdirectories which contain .git directories.
Type:boolean
cleanBeforeCheckout
extension
cleanBeforeCheckout
Clean up the workspace before every checkout by deleting all untracked files and directories, including those which are specified in .gitignore. It also resets all tracked files to their versioned state. This ensures that the workspace is in the same state as if you cloned and checked out in a brand-new empty directory, and ensures that your build is not affected by the files generated by the previous build.
deleteUntrackedNestedRepositories (optional)
Deletes untracked submodules and any other subdirectories which contain .git directories.
Type:boolean
cloneOption
extension
cloneOption
shallow
Perform shallow clone, so that git will not download the history of the project, saving time and disk space when you just want to access the latest version of a repository.
Type:boolean
noTags
Deselect this to perform a clone without tags, saving time and disk space when you just want to access what is specified by the refspec.
Type:boolean
reference
Specify a folder containing a repository that will be used by Git as a reference during clone operations.
This option will be ignored if the folder is not available on the controller or agent where the clone is being executed.
Type:String
timeout
Specify a timeout (in minutes) for clone and fetch operations.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
depth (optional)
Set shallow clone depth, so that git will only download recent history of the project, saving time and disk space when you just want to access the latest commits of a repository.
Type:int
honorRefspec (optional)
Perform initial clone using the refspec defined for the repository. This can save time, data transfer and disk space when you only need to access the references specified by the refspec.
Type:boolean
discoverOtherRefs
Discovers other specified refs on the repository.
ref

The pattern under /refs on the remote repository to discover, can contain a wildcard.
Example: test/*/merged

Type:String
nameMapping (optional)

Mapping for how the ref can be named in for example the @Library.
Example: test-@{1}
Where @{1} replaces the first wildcard in the ref when discovered.

By default it will be "namespace_before_wildcard-@{1}". E.g. if ref is "test/*/merged" the default mapping would be "test-@{1}".

Type:String
gitLabForkDiscovery
Discovers merge requests where the origin project is a fork of the target project.
strategyId
Determines how merge requests are discovered:
Merging the merge request with the current target branch revision
Discover each merge request once with the discovered revision corresponding to the result of merging with the current revision of the target branch
The current merge request revision
Discover each merge request once with the discovered revision corresponding to the merge request head revision without merging
Both the current merge request revision and the merge request merged with the current target branch revision
Discover each merge request twice. The first discovered revision corresponds to the result of merging with the current revision of the target branch in each scan. The second parallel discovered revision corresponds to the merge request head revision without merging
Type:int
trust

One of the great powers of merge requests is that anyone with read access to a project can fork it, commit some changes to their fork and then create a merge request against the original project with their changes. There are some files stored in source control that are important. For example, a Jenkinsfile may contain configuration details to sandbox merge requests in order to mitigate against malicious merge requests. In order to protect against a malicious merge request itself modifying the Jenkinsfile to remove the protections, you can define the trust policy for merge requests from forks.

Other plugins can extend the available trust policies. The default policies are:

Nobody
Merge requests from forks will all be treated as untrusted. This means that where Jenkins requires a trusted file (e.g. Jenkinsfile) the contents of that file will be retrieved from the target branch on the origin project and not from the merge request branch on the fork project.
Members
Merge requests from collaborators to the origin project will be treated as trusted, all other merge requests from fork repositories will be treated as untrusted. Note that if credentials used by Jenkins for scanning the project does not have permission to query the list of contributors to the origin project then only the origin account will be treated as trusted - i.e. this will fall back to Nobody.
Trusted Members
Merge requests forks will be treated as trusted if and only if the fork owner has either Developer or Maintainer or Owner Access Level in the origin project. This is the recommended policy.
Everyone
All merge requests from forks will be treated as trusted. NOTE: this option can be dangerous if used on a public project hosted on a GitLab instance.
java.lang.UnsupportedOperationException: do not know how to categorize attributes of type jenkins.scm.api.trait.SCMHeadAuthority<? super io.jenkins.plugins.gitlabbranchsource.GitLabSCMSourceRequest, ? extends jenkins.scm.api.mixin.ChangeRequestSCMHead2, ? extends jenkins.scm.api.SCMRevision>
buildMRForksNotMirror (optional)
Add discovery of merge requests where the origin project is a fork of a certain project, but the target project is not the original forked project. To be used in case one has a GitLab project which is a fork of another project from another team, in order to isolate artefacts and allow an MR flow. This means using MRs inside that fork from branches in the fork back to the fork's default branch. (Implements https://github.com/jenkinsci/gitlab-branch-source-plugin/issues/167)
Type:boolean
gitHubForkDiscovery
Discovers pull requests where the origin repository is a fork of the target repository.
strategyId
Determines how pull requests are discovered:
Merging the pull request with the current target branch revision
Discover each pull request once with the discovered revision corresponding to the result of merging with the current revision of the target branch. Note that pushes to the target branch will result in new pull request builds.
The current pull request revision
Discover each pull request once with the discovered revision corresponding to the pull request head revision without merging.
Both the current pull request revision and the pull request merged with the current target branch revision
Discover each pull request twice. The first discovered revision corresponds to the result of merging with the current revision of the target branch in each scan. The second parallel discovered revision corresponds to the pull request head revision without merging.
Type:int
trust

One of the great powers of pull requests is that anyone with read access to a repository can fork it, commit some changes to their fork and then create a pull request against the original repository with their changes. There are some files stored in source control that are important. For example, a Jenkinsfile may contain configuration details to sandbox pull requests in order to mitigate against malicious pull requests. In order to protect against a malicious pull request itself modifying the Jenkinsfile to remove the protections, you can define the trust policy for pull requests from forks.

Other plugins can extend the available trust policies. The default policies are:

Nobody
Pull requests from forks will all be treated as untrusted. This means that where Jenkins requires a trusted file (e.g. Jenkinsfile) the contents of that file will be retrieved from the target branch on the origin repository and not from the pull request branch on the fork repository.
Collaborators
Pull requests from collaborators to the origin repository will be treated as trusted, all other pull requests from fork repositories will be treated as untrusted. Note that if credentials used by Jenkins for scanning the repository does not have permission to query the list of collaborators to the origin repository then only the origin account will be treated as trusted - i.e. this will fall back to Nobody. NOTE: all collaborators are trusted, even if they are only members of a team with read permission.
Everyone
All pull requests from forks will be treated as trusted. NOTE: this option can be dangerous if used on a public repository hosted on GitHub.
From users with Admin or Write permission
Pull requests forks will be treated as trusted if and only if the fork owner has either Admin or Write permissions on the origin repository. This is the recommended policy. Note that this strategy requires the Review a user's permission level API, as a result on GitHub Enterprise Server versions before 2.12 this is the same as trusting Nobody.
Nested choice of objects
gitHubTrustContributors
gitHubTrustEveryone
gitHubTrustNobody
gitHubTrustPermissions
browser
browser
Nested choice of objects
assembla
repoUrl
Specify the root URL serving this repository (such as https://www.assembla.com/code/PROJECT/git/).
Type:String
bitbucketServer
repoUrl
Specify the Bitbucket Server root URL for this repository (such as https://bitbucket:7990/OWNER/REPO/).
Type:String
bitbucket
repoUrl
Specify the root URL serving this repository (such as https://bitbucket.org/OWNER/REPO/).
Type:String
cgit
repoUrl
Specify the root URL serving this repository (such as https://cgit.example.com:port/group/REPO/).
Type:String
fisheye
repoUrl
Specify the URL of this repository in FishEye (such as https://fisheye.example.com/browse/project/).
Type:String
gitblit
repoUrl
Specify the root URL serving this repository.
Type:String
projectName
Specify the name of the project in GitBlit.
Type:String
gitLab
repoUrl
Specify the root URL serving this repository (such as https://gitlab.com/username/repository/).
Type:String
version (optional)
Specify the major and minor version of GitLab you use (such as 9.1). If you don't specify a version, a modern version of GitLab (>= 8.0) is assumed.
Type:String
gitLabBrowser
Specify the HTTP URL for this project's GitLab page so that links to changes can be automatically generated by Jenkins. The URL needs to include the owner and project. If the GitLab server is https://gitLab.example.com then the URL for bob's skunkworks project might be https://gitLab.example.com/bob/skunkworks.
projectUrl
Specify the HTTP URL for this project's GitLab page. The URL needs to include the owner and project so, for example, if the GitLab server is https://gitLab.example.com then the URL for bob's skunkworks project might be https://gitLab.example.com/bob/skunkworks
Type:String
gitList
repoUrl
Specify the root URL serving this repository (such as https://gitlist.example.com/repo/).
Type:String
gitWeb
repoUrl
Specify the root URL serving this repository (such as https://github.com/jenkinsci/jenkins.git).
Type:String
github
repoUrl
Specify the HTTP URL for this repository's GitHub page (such as https://github.com/jquery/jquery).
Type:String
gitiles
repoUrl
Specify the root URL serving this repository (such as https://gwt.googlesource.com/gwt/).
Type:String
$class: 'GitoriousWeb'
repoUrl
Specify the root URL serving this repository (such as https://gitorious.org/gitorious/mainline).
Type:String
gogs
repoUrl
Specify the root URL serving this repository (such as https://gogs.example.com/username/some-repo-url.git).
Type:String
kiln
repoUrl
Specify the root URL serving this repository (such as https://khanacademy.kilnhg.com/Code/Website/Group/webapp).
Type:String
phabricator
repoUrl
Specify the phabricator instance root URL (such as https://phabricator.example.com).
Type:String
repo
Specify the repository name in phabricator (such as the foo part of phabricator.example.com/diffusion/foo/browse).
Type:String
redmine
repoUrl
Specify the root URL serving this repository (such as https://redmine.example.com/PATH/projects/PROJECT/repository).
Type:String
rhodeCode
repoUrl
Specify the HTTP URL for this repository's RhodeCode page (such as https://rhodecode.example.com/projects/PROJECT/repos/REPO/).
Type:String
$class: 'Stash'
repoUrl
Specify the HTTP URL for this repository's Stash page (such as https://stash.example.com/projects/PROJECT/repos/REPO/).
Type:String
teamFoundation
repoUrl
Either the name of the remote whose URL should be used, or the URL of this module in TFS (such as https://tfs.example.com/tfs/PROJECT/_git/REPO/). If empty (default), the URL of the "origin" repository is used.

If TFS is also used as the repository server, this can usually be left blank.

Type:String
viewgit
repoUrl
Specify the root URL serving this repository (such as https://git.example.com/viewgit/).
Type:String
projectName
Specify the name of the project in ViewGit (e.g. scripts, scuttle etc. from https://code.fealdia.org/viewgit/).
Type:String
lfs
gitlabAvatar
disableProjectAvatar (optional)
Due to a GitLab bug, sometimes it is not possible to GitLab API to fetch GitLab Avatar for private projects or when the api doesn't have token access. You may choose to skip avatar for projects if you want to avoid broken or self generated avatars.
Type:boolean
gitlabMarkUnstableAsSuccess
markUnstableAsSuccess (optional)
Type:boolean
gitlabSkipNotifications
gitTool
gitTool
Type:String
gitLabHookRegistration
webHookMode
Type:String
systemHookMode
Type:String
gitHubIgnoreDraftPullRequestFilter
ignoreOnPush
localBranch
logComment
logSuccess (optional)
Sometimes the user doesn't want to log the builds that succeeded. The trait only enable logging of failed/aborted builds by default. Select this option to include logging of successful builds as well.
Type:boolean
sudoUser (optional)
Enter a sudo username of the user you want to comment as on GitLab Server. Remember the token specified should have api and sudo access both (which can only be created by your GitLab Server Admin). It is recommended to create a dummy user in your GitLab Server with an appropriate username like `jenkinsadmin` etc. Leave empty if you want use the owner of the project as the commenter.
Type:String
multiBranchProjectDisplayNaming
Some branch source plugins provide additional information about discovered branches like a title or subject of merge or change requests.
With this trait, that additional information can be used for the job display names.
Note: Job display name changes do not trigger builds.
displayNamingStrategy
The different strategies:
  • Job display name with fallback to name:
    Uses the branch source plugin's display name for the PR instead of the raw name
    Value for configuration-as-code: OBJECT_DISPLAY_NAME

  • Name and, if available, display name:
    Joins the raw name and the branch source plugin's display name
    Value for configuration-as-code: RAW_AND_OBJECT_DISPLAY_NAME

Values:
OBJECT_DISPLAY_NAME
RAW_AND_OBJECT_DISPLAY_NAME
gitLabOriginDiscovery
Discovers merge requests where the origin project is the same as the target project.
strategyId
Determines how merge requests are discovered:
Merging the merge request with the current target branch revision
Discover each merge request once with the discovered revision corresponding to the result of merging with the current revision of the target branch
The current merge request revision
Discover each merge request once with the discovered revision corresponding to the merge request head revision without merging
Both the current merge request revision and the merge request merged with the current target branch revision
Discover each merge request twice. The first discovered revision corresponds to the result of merging with the current revision of the target branch in each scan. The second parallel discovered revision corresponds to the merge request head revision without merging
Type:int
gitHubPullRequestDiscovery
Discovers pull requests where the origin repository is the same as the target repository.
strategyId
Determines how pull requests are discovered:
Merging the pull request with the current target branch revision
Discover each pull request once with the discovered revision corresponding to the result of merging with the current revision of the target branch. Note that pushes to the target branch will result in new pull request builds.
The current pull request revision
Discover each pull request once with the discovered revision corresponding to the pull request head revision without merging.
Both the current pull request revision and the pull request merged with the current target branch revision
Discover each pull request twice. The first discovered revision corresponds to the result of merging with the current revision of the target branch in each scan. The second parallel discovered revision corresponds to the pull request head revision without merging.
Type:int
pruneStaleBranch
pruneStaleTag
refSpecs
templates
Array/List:
Nested object
value
A ref spec to fetch. Any occurrences of @{remote} will be replaced by the remote name (which defaults to origin) before use.
Type:String
headRegexFilter
regex
A Java regular expression to restrict the names. Names that do not match the supplied regular expression will be ignored.
NOTE: this filter will be applied to all branch like things, including change requests
Type:String
remoteName
remoteName
Type:String
sparseCheckoutPaths
extension
Nested object

Specify the paths that you'd like to sparse checkout. This may be used for saving space (Think about a reference repository). Be sure to use a recent version of Git, at least above 1.7.10

sparseCheckoutPaths
Array/List:
Nested object
path
Type:String
submoduleOption
extension
submodule
depth (optional)
Set shallow clone depth, so that git will only download recent history of the project, saving time and disk space when you just want to access the latest commits of a repository.
Type:int
disableSubmodules (optional)
By disabling support for submodules you can still keep using basic git plugin functionality and just have Jenkins to ignore submodules completely as if they didn't exist.
Type:boolean
parentCredentials (optional)
Use credentials from the default remote of the parent project.
Type:boolean
recursiveSubmodules (optional)
Retrieve all submodules recursively (uses '--recursive' option which requires git>=1.6.5)
Type:boolean
reference (optional)
Specify a folder containing a repository that will be used by Git as a reference during clone operations.
This option will be ignored if the folder is not available on the controller or agent where the clone is being executed.
To prepare a reference folder with multiple subprojects, create a bare git repository and add all the remote urls then perform a fetch:
  git init --bare
  git remote add SubProject1 https://gitrepo.com/subproject1
  git remote add SubProject2 https://gitrepo.com/subproject2
  git fetch --all
  
Type:String
shallow (optional)
Perform shallow clone, so that git will not download the history of the project, saving time and disk space when you just want to access the latest version of a repository.
Type:boolean
threads (optional)
Specify the number of threads that will be used to update submodules.
If unspecified, the command line git default thread count is used.
Type:int
timeout (optional)
Specify a timeout (in minutes) for submodules operations.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
trackingSubmodules (optional)
Retrieve the tip of the configured branch in .gitmodules (Uses '--remote' option which requires git>=1.8.2)
Type:boolean
mrTriggerComment
commentBody
Add comment body you want to use to instruct Jenkins CI to rebuild the MR
Type:String
onlyTrustedMembersCanTrigger
Type:boolean
userIdentity
extension
Nested object
name

If given, "GIT_COMMITTER_NAME=[this]" and "GIT_AUTHOR_NAME=[this]" are set for builds. This overrides whatever is in the global settings.

Type:String
email

If given, "GIT_COMMITTER_EMAIL=[this]" and "GIT_AUTHOR_EMAIL=[this]" are set for builds. This overrides whatever is in the global settings.

Type:String
WebhookListenerBuildConditionsTrait
alwaysBuildMROpen (optional)
Type:boolean
alwaysBuildMRReOpen (optional)
Type:boolean
alwaysIgnoreMRApproval (optional)
Type:boolean
alwaysIgnoreMRApproved (optional)
Type:boolean
alwaysIgnoreMRUnApproval (optional)
Type:boolean
alwaysIgnoreMRUnApproved (optional)
Type:boolean
alwaysIgnoreMRWorkInProgress (optional)
Type:boolean
alwaysIgnoreNonCodeRelatedUpdates (optional)
GitLab will send a webhook to Jenkins when there are updates to the MR including title changes, labels removed/added, etc. Enabling this option will prevent a build running if the cause was one of these updates. Note: these settings do not have any impact on build from comment settings.
Type:boolean
headWildcardFilter
includes
Space-separated list of name patterns to consider. You may use * as a wildcard; for example: master release*
NOTE: this filter will be applied to all branch like things, including change requests
Type:String
excludes
Space-separated list of name patterns to ignore even if matched by the includes list. For example: release alpha-* beta-*
NOTE: this filter will be applied to all branch like things, including change requests
Type:String
$class: 'WipeWorkspaceTrait'
gitLabBranchDiscovery
Discovers branches on the repository.
strategyId
Determines which branches are discovered.
Only branches that are not also filed as MRs
If you are discovering origin merge requests, it may not make sense to discover the same changes both as a merge request and as a branch.
Only branches that are also filed as MRs
This option exists to preserve legacy behaviour when upgrading from older versions of the plugin. NOTE: If you have an actual use case for this option please file a merge request against this text.
All branches
Ignores whether the branch is also filed as a merge request and instead discovers all branches on the origin project.
Type:int
gitLabSshCheckout
By default the discovered branches / merge requests will all use the same username / password credentials that were used for discovery when checking out sources. This means that the checkout will be using the https:// protocol for the Git repository.

This behaviour allows you to select the SSH private key to be used for checking out sources, which will consequently force the checkout to use the ssh:// protocol.

credentialsId
Credentials used to check out sources. Must be a SSH key based credential.
Type:String
gitLabTagDiscovery
gitBranchDiscovery
Discovers branches on the repository.
gitTagDiscovery
Discovers tags on the repository.
gitHubBranchDiscovery
Discovers branches on the repository.
strategyId
Determines which branches are discovered.
Exclude branches that are also filed as PRs
If you are discovering origin pull requests, you may not want to also build the source branches for those pull requests.
Only branches that are also filed as PRs
Similar to discovering origin pull requests, but discovers the branch rather than the pull request. This means env.GIT_BRANCH will be set to the branch name rather than PR-#. Also, status notifications for these builds will only be applied to the commit and not to the pull request.
All branches
Ignores whether the branch is also filed as a pull request and instead discovers all branches on the origin repository.
Type:int
gitHubSshCheckout
By default the discovered branches / pull requests will all use the same username / password credentials that were used for discovery when checking out sources. This means that the checkout will be using the https:// protocol for the Git repository.

This behaviour allows you to select the SSH private key to be used for checking out sources, which will consequently force the checkout to use the ssh:// protocol.

credentialsId
Credentials used to check out sources. Must be a SSH key based credential.
Type:String
gitHubTagDiscovery
Discovers tags on the repository.
git
remote
Specify the URL of this remote repository. This uses the same syntax as your git clone command.
Type:String
browser (optional)
Nested choice of objects
assembla
repoUrl
Specify the root URL serving this repository (such as https://www.assembla.com/code/PROJECT/git/).
Type:String
bitbucketServer
repoUrl
Specify the Bitbucket Server root URL for this repository (such as https://bitbucket:7990/OWNER/REPO/).
Type:String
bitbucket
repoUrl
Specify the root URL serving this repository (such as https://bitbucket.org/OWNER/REPO/).
Type:String
cgit
repoUrl
Specify the root URL serving this repository (such as https://cgit.example.com:port/group/REPO/).
Type:String
fisheye
repoUrl
Specify the URL of this repository in FishEye (such as https://fisheye.example.com/browse/project/).
Type:String
gitblit
repoUrl
Specify the root URL serving this repository.
Type:String
projectName
Specify the name of the project in GitBlit.
Type:String
gitLab
repoUrl
Specify the root URL serving this repository (such as https://gitlab.com/username/repository/).
Type:String
version (optional)
Specify the major and minor version of GitLab you use (such as 9.1). If you don't specify a version, a modern version of GitLab (>= 8.0) is assumed.
Type:String
gitLabBrowser
Specify the HTTP URL for this project's GitLab page so that links to changes can be automatically generated by Jenkins. The URL needs to include the owner and project. If the GitLab server is https://gitLab.example.com then the URL for bob's skunkworks project might be https://gitLab.example.com/bob/skunkworks.
projectUrl
Specify the HTTP URL for this project's GitLab page. The URL needs to include the owner and project so, for example, if the GitLab server is https://gitLab.example.com then the URL for bob's skunkworks project might be https://gitLab.example.com/bob/skunkworks
Type:String
gitList
repoUrl
Specify the root URL serving this repository (such as https://gitlist.example.com/repo/).
Type:String
gitWeb
repoUrl
Specify the root URL serving this repository (such as https://github.com/jenkinsci/jenkins.git).
Type:String
github
repoUrl
Specify the HTTP URL for this repository's GitHub page (such as https://github.com/jquery/jquery).
Type:String
gitiles
repoUrl
Specify the root URL serving this repository (such as https://gwt.googlesource.com/gwt/).
Type:String
$class: 'GitoriousWeb'
repoUrl
Specify the root URL serving this repository (such as https://gitorious.org/gitorious/mainline).
Type:String
gogs
repoUrl
Specify the root URL serving this repository (such as https://gogs.example.com/username/some-repo-url.git).
Type:String
kiln
repoUrl
Specify the root URL serving this repository (such as https://khanacademy.kilnhg.com/Code/Website/Group/webapp).
Type:String
phabricator
repoUrl
Specify the phabricator instance root URL (such as https://phabricator.example.com).
Type:String
repo
Specify the repository name in phabricator (such as the foo part of phabricator.example.com/diffusion/foo/browse).
Type:String
redmine
repoUrl
Specify the root URL serving this repository (such as https://redmine.example.com/PATH/projects/PROJECT/repository).
Type:String
rhodeCode
repoUrl
Specify the HTTP URL for this repository's RhodeCode page (such as https://rhodecode.example.com/projects/PROJECT/repos/REPO/).
Type:String
$class: 'Stash'
repoUrl
Specify the HTTP URL for this repository's Stash page (such as https://stash.example.com/projects/PROJECT/repos/REPO/).
Type:String
teamFoundation
repoUrl
Either the name of the remote whose URL should be used, or the URL of this module in TFS (such as https://tfs.example.com/tfs/PROJECT/_git/REPO/). If empty (default), the URL of the "origin" repository is used.

If TFS is also used as the repository server, this can usually be left blank.

Type:String
viewgit
repoUrl
Specify the root URL serving this repository (such as https://git.example.com/viewgit/).
Type:String
projectName
Specify the name of the project in ViewGit (e.g. scripts, scuttle etc. from https://code.fealdia.org/viewgit/).
Type:String
credentialsId (optional)
Credentials used to scan branches and check out sources.
Type:String
extensions (optional)
Array/List:
Nested choice of objects
authorInChangelog
The default behavior is to use the Git commit's "Committer" value in Jenkins' build changesets. If this option is selected, the Git commit's "Author" value would be used instead.
$class: 'BuildChooserSetting'
When you are interested in using a job to build multiple heads (most typically multiple branches), you can choose how Jenkins choose what branches to build in what order.

This extension point in Jenkins is used by many other plugins to control the job to build specific commits. When you activate those plugins, you may see them installing a custom strategy here.

buildChooser
Nested choice of objects
$class: 'AncestryBuildChooser'
maximumAgeInDays
Type:int
ancestorCommitSha1
Type:String
$class: 'DefaultBuildChooser'
$class: 'InverseBuildChooser'
buildSingleRevisionOnly
Disable scheduling for multiple candidate revisions.
If we have 3 branches:
----A--.---.--- B
         \-----C
jenkins would try to build (B) and (C).
This behaviour disables this and only builds one of them.
It is helpful to reduce the load of the Jenkins infrastructure when the SCM system like Bitbucket or GitHub should decide what commits to build.
changelogToBranch
This method calculates the changelog against the specified branch.
options
changelogBase
compareRemote
Name of the repository, such as origin, that contains the branch you specify below.
Type:String
compareTarget
The name of the branch within the named repository to compare against.
Type:String
checkoutOption
timeout
Specify a timeout (in minutes) for checkout.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
cleanBeforeCheckout
Clean up the workspace before every checkout by deleting all untracked files and directories, including those which are specified in .gitignore. It also resets all tracked files to their versioned state. This ensures that the workspace is in the same state as if you cloned and checked out in a brand-new empty directory, and ensures that your build is not affected by the files generated by the previous build.
deleteUntrackedNestedRepositories (optional)
Deletes untracked submodules and any other subdirectories which contain .git directories.
Type:boolean
cleanAfterCheckout
Clean up the workspace after every checkout by deleting all untracked files and directories, including those which are specified in .gitignore. It also resets all tracked files to their versioned state. This ensures that the workspace is in the same state as if you cloned and checked out in a brand-new empty directory, and ensures that your build is not affected by the files generated by the previous build.
deleteUntrackedNestedRepositories (optional)
Deletes untracked submodules and any other subdirectories which contain .git directories.
Type:boolean
cloneOption
shallow
Perform shallow clone, so that git will not download the history of the project, saving time and disk space when you just want to access the latest version of a repository.
Type:boolean
noTags
Deselect this to perform a clone without tags, saving time and disk space when you just want to access what is specified by the refspec.
Type:boolean
reference
Specify a folder containing a repository that will be used by Git as a reference during clone operations.
This option will be ignored if the folder is not available on the controller or agent where the clone is being executed.
Type:String
timeout
Specify a timeout (in minutes) for clone and fetch operations.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
depth (optional)
Set shallow clone depth, so that git will only download recent history of the project, saving time and disk space when you just want to access the latest commits of a repository.
Type:int
honorRefspec (optional)
Perform initial clone using the refspec defined for the repository. This can save time, data transfer and disk space when you only need to access the references specified by the refspec.
Type:boolean
$class: 'DisableRemotePoll'
Git plugin uses git ls-remote polling mechanism by default when configured with a single branch (no wildcards!). This compare the latest built commit SHA with the remote branch without cloning a local copy of the repo.

If you don't want to / can't use this.

If this option is selected, polling will require a workspace and might trigger unwanted builds (see JENKINS-10131).
lfs
Enable git large file support for the workspace by pulling large files after the checkout completes. Requires that the controller and each agent performing an LFS checkout have installed `git lfs`.
$class: 'IgnoreNotifyCommit'
If checked, this repository will be ignored when the notifyCommit-URL is accessed regardless of if the repository matches or not.
localBranch
If given, checkout the revision to build as HEAD on this branch.

If selected, and its value is an empty string or "**", then the branch name is computed from the remote branch without the origin. In that case, a remote branch origin/master will be checked out to a local branch named master, and a remote branch origin/develop/new-feature will be checked out to a local branch named develop/newfeature.

Please note that this has not been tested with submodules.

localBranch
Type:String
$class: 'MessageExclusion'
excludedMessage
If set, and Jenkins is set to poll for changes, Jenkins will ignore any revisions committed with message matched to Pattern when determining if a build needs to be triggered. This can be used to exclude commits done by the build itself from triggering another build, assuming the build server commits the change with a distinct message.

Exclusion uses Pattern matching

.*\[maven-release-plugin\].*
The example above illustrates that if only revisions with "[maven-release-plugin]" message in first comment line have been committed to the SCM a build will not occur.

You can create more complex patterns using embedded flag expressions.

(?s).*FOO.*
This example will search FOO message in all comment lines.
Type:String
$class: 'PathRestriction'
If set, and Jenkins is set to poll for changes, Jenkins will pay attention to included and/or excluded files and/or folders when determining if a build needs to be triggered.

Using this behaviour will preclude the faster git ls-remote polling mechanism, forcing polling to require a workspace thus sometimes triggering unwanted builds, as if you had selected the Force polling using workspace extension as well.

includedRegions
Each inclusion uses java regular expression pattern matching, and must be separated by a new line. An empty list implies that everything is included.

    myapp/src/main/web/.*\.html
    myapp/src/main/web/.*\.jpeg
    myapp/src/main/web/.*\.gif
  
The example above illustrates that a build will only occur, if html/jpeg/gif files have been committed to the SCM. Exclusions take precedence over inclusions, if there is an overlap between included and excluded regions.
Type:String
excludedRegions
Each exclusion uses java regular expression pattern matching, and must be separated by a new line.

    myapp/src/main/web/.*\.html
    myapp/src/main/web/.*\.jpeg
    myapp/src/main/web/.*\.gif
  
The example above illustrates that if only html/jpeg/gif files have been committed to the SCM a build will not occur.
Type:String
perBuildTag
Create a tag in the workspace for every build to unambiguously mark the commit that was built. You can combine this with Git publisher to push the tags to the remote repository.
$class: 'PreBuildMerge'
These options allow you to perform a merge to a particular branch before building. For example, you could specify an integration branch to be built, and to merge to master. In this scenario, on every change of integration, Jenkins will perform a merge with the master branch, and try to perform a build if the merge is successful. It then may push the merge back to the remote repository if the Git Push post-build action is selected.
options
Nested object
mergeTarget
The name of the branch within the named repository to merge to, such as master.
Type:String
fastForwardMode (optional)
Merge fast-forward mode selection.
The default, --ff, gracefully falls back to a merge commit when required.
For more information, see the Git Merge Documentation
Values:
FF
FF_ONLY
NO_FF
mergeRemote (optional)
Name of the repository, such as origin, that contains the branch you specify below. If left blank, it'll default to the name of the first repository configured above.
Type:String
mergeStrategy (optional)
Merge strategy selection. This feature is not fully implemented in JGIT.
Values:
DEFAULT
RESOLVE
RECURSIVE
OCTOPUS
OURS
SUBTREE
RECURSIVE_THEIRS
pruneStaleBranch
Run "git remote prune" for each remote, to prune obsolete local branches.
pruneTags
pruneTags
Type:boolean
$class: 'RelativeTargetDirectory'
relativeTargetDir
Specify a local directory (relative to the workspace root) where the Git repository will be checked out. If left empty, the workspace root itself will be used.

This extension should not be used in Jenkins Pipeline (either declarative or scripted). Jenkins Pipeline already provides standard techniques for checkout to a subdirectory. Use ws and dir in Jenkins Pipeline rather than this extension.

Type:String
$class: 'ScmName'

Unique name for this SCM. Needed when using Git within the Multi SCM plugin.

name
Type:String
$class: 'SparseCheckoutPaths'

Specify the paths that you'd like to sparse checkout. This may be used for saving space (Think about a reference repository). Be sure to use a recent version of Git, at least above 1.7.10

sparseCheckoutPaths
Array/List:
Nested object
path
Type:String
submodule
depth (optional)
Set shallow clone depth, so that git will only download recent history of the project, saving time and disk space when you just want to access the latest commits of a repository.
Type:int
disableSubmodules (optional)
By disabling support for submodules you can still keep using basic git plugin functionality and just have Jenkins to ignore submodules completely as if they didn't exist.
Type:boolean
parentCredentials (optional)
Use credentials from the default remote of the parent project.
Type:boolean
recursiveSubmodules (optional)
Retrieve all submodules recursively (uses '--recursive' option which requires git>=1.6.5)
Type:boolean
reference (optional)
Specify a folder containing a repository that will be used by Git as a reference during clone operations.
This option will be ignored if the folder is not available on the controller or agent where the clone is being executed.
To prepare a reference folder with multiple subprojects, create a bare git repository and add all the remote urls then perform a fetch:
  git init --bare
  git remote add SubProject1 https://gitrepo.com/subproject1
  git remote add SubProject2 https://gitrepo.com/subproject2
  git fetch --all
  
Type:String
shallow (optional)
Perform shallow clone, so that git will not download the history of the project, saving time and disk space when you just want to access the latest version of a repository.
Type:boolean
threads (optional)
Specify the number of threads that will be used to update submodules.
If unspecified, the command line git default thread count is used.
Type:int
timeout (optional)
Specify a timeout (in minutes) for submodules operations.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
trackingSubmodules (optional)
Retrieve the tip of the configured branch in .gitmodules (Uses '--remote' option which requires git>=1.8.2)
Type:boolean
$class: 'UserExclusion'
excludedUsers
If set, and Jenkins is set to poll for changes, Jenkins will ignore any revisions committed by users in this list when determining if a build needs to be triggered. This can be used to exclude commits done by the build itself from triggering another build, assuming the build server commits the change with a distinct SCM user.

Using this behaviour will preclude the faster git ls-remote polling mechanism, forcing polling to require a workspace thus sometimes triggering unwanted builds, as if you had selected the Force polling using workspace extension as well.

Each exclusion uses exact string comparison and must be separated by a new line. User names are only excluded if they exactly match one of the names in this list.

auto_build_user
The example above illustrates that if only revisions by "auto_build_user" have been committed to the SCM a build will not occur.
Type:String
$class: 'UserIdentity'
name

If given, "GIT_COMMITTER_NAME=[this]" and "GIT_AUTHOR_NAME=[this]" are set for builds. This overrides whatever is in the global settings.

Type:String
email

If given, "GIT_COMMITTER_EMAIL=[this]" and "GIT_AUTHOR_EMAIL=[this]" are set for builds. This overrides whatever is in the global settings.

Type:String
$class: 'WipeWorkspace'
Delete the contents of the workspace before building, ensuring a fully fresh workspace.
gitTool (optional)
Type:String
id (optional)
Type:String
traits (optional)
Array/List:
Nested choice of objects
authorInChangelog
buildStatusNameCustomPart
Customize the pipeline status name used by Jenkins
buildStatusNameCustomPart (optional)
Enter a string to customize the status/context name for status updates published to GitLab. For a branch build the default name would be 'jenkinsci/branch'. With the buildStatusNameCustomPart 'custom' the name would be 'jenkinsci/custom/branch'. This allows to have multiple GitLab-Branch-Sources for the same GitLab-project configured.
Type:String
buildStatusNameOverwrite (optional)
Overwrites the build status name including the jenkinsci default part.
Instead of 'jenkinsci/custom/branch' just 'custom/branch'.
Type:boolean
ignoreTypeInStatusName (optional)
Type:boolean
checkoutOption
extension
checkoutOption
timeout
Specify a timeout (in minutes) for checkout.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
cleanAfterCheckout
extension
cleanAfterCheckout
Clean up the workspace after every checkout by deleting all untracked files and directories, including those which are specified in .gitignore. It also resets all tracked files to their versioned state. This ensures that the workspace is in the same state as if you cloned and checked out in a brand-new empty directory, and ensures that your build is not affected by the files generated by the previous build.
deleteUntrackedNestedRepositories (optional)
Deletes untracked submodules and any other subdirectories which contain .git directories.
Type:boolean
cleanBeforeCheckout
extension
cleanBeforeCheckout
Clean up the workspace before every checkout by deleting all untracked files and directories, including those which are specified in .gitignore. It also resets all tracked files to their versioned state. This ensures that the workspace is in the same state as if you cloned and checked out in a brand-new empty directory, and ensures that your build is not affected by the files generated by the previous build.
deleteUntrackedNestedRepositories (optional)
Deletes untracked submodules and any other subdirectories which contain .git directories.
Type:boolean
cloneOption
extension
cloneOption
shallow
Perform shallow clone, so that git will not download the history of the project, saving time and disk space when you just want to access the latest version of a repository.
Type:boolean
noTags
Deselect this to perform a clone without tags, saving time and disk space when you just want to access what is specified by the refspec.
Type:boolean
reference
Specify a folder containing a repository that will be used by Git as a reference during clone operations.
This option will be ignored if the folder is not available on the controller or agent where the clone is being executed.
Type:String
timeout
Specify a timeout (in minutes) for clone and fetch operations.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
depth (optional)
Set shallow clone depth, so that git will only download recent history of the project, saving time and disk space when you just want to access the latest commits of a repository.
Type:int
honorRefspec (optional)
Perform initial clone using the refspec defined for the repository. This can save time, data transfer and disk space when you only need to access the references specified by the refspec.
Type:boolean
discoverOtherRefs
Discovers other specified refs on the repository.
ref

The pattern under /refs on the remote repository to discover, can contain a wildcard.
Example: test/*/merged

Type:String
nameMapping (optional)

Mapping for how the ref can be named in for example the @Library.
Example: test-@{1}
Where @{1} replaces the first wildcard in the ref when discovered.

By default it will be "namespace_before_wildcard-@{1}". E.g. if ref is "test/*/merged" the default mapping would be "test-@{1}".

Type:String
gitLabForkDiscovery
Discovers merge requests where the origin project is a fork of the target project.
strategyId
Determines how merge requests are discovered:
Merging the merge request with the current target branch revision
Discover each merge request once with the discovered revision corresponding to the result of merging with the current revision of the target branch
The current merge request revision
Discover each merge request once with the discovered revision corresponding to the merge request head revision without merging
Both the current merge request revision and the merge request merged with the current target branch revision
Discover each merge request twice. The first discovered revision corresponds to the result of merging with the current revision of the target branch in each scan. The second parallel discovered revision corresponds to the merge request head revision without merging
Type:int
trust

One of the great powers of merge requests is that anyone with read access to a project can fork it, commit some changes to their fork and then create a merge request against the original project with their changes. There are some files stored in source control that are important. For example, a Jenkinsfile may contain configuration details to sandbox merge requests in order to mitigate against malicious merge requests. In order to protect against a malicious merge request itself modifying the Jenkinsfile to remove the protections, you can define the trust policy for merge requests from forks.

Other plugins can extend the available trust policies. The default policies are:

Nobody
Merge requests from forks will all be treated as untrusted. This means that where Jenkins requires a trusted file (e.g. Jenkinsfile) the contents of that file will be retrieved from the target branch on the origin project and not from the merge request branch on the fork project.
Members
Merge requests from collaborators to the origin project will be treated as trusted, all other merge requests from fork repositories will be treated as untrusted. Note that if credentials used by Jenkins for scanning the project does not have permission to query the list of contributors to the origin project then only the origin account will be treated as trusted - i.e. this will fall back to Nobody.
Trusted Members
Merge requests forks will be treated as trusted if and only if the fork owner has either Developer or Maintainer or Owner Access Level in the origin project. This is the recommended policy.
Everyone
All merge requests from forks will be treated as trusted. NOTE: this option can be dangerous if used on a public project hosted on a GitLab instance.
java.lang.UnsupportedOperationException: do not know how to categorize attributes of type jenkins.scm.api.trait.SCMHeadAuthority<? super io.jenkins.plugins.gitlabbranchsource.GitLabSCMSourceRequest, ? extends jenkins.scm.api.mixin.ChangeRequestSCMHead2, ? extends jenkins.scm.api.SCMRevision>
buildMRForksNotMirror (optional)
Add discovery of merge requests where the origin project is a fork of a certain project, but the target project is not the original forked project. To be used in case one has a GitLab project which is a fork of another project from another team, in order to isolate artefacts and allow an MR flow. This means using MRs inside that fork from branches in the fork back to the fork's default branch. (Implements https://github.com/jenkinsci/gitlab-branch-source-plugin/issues/167)
Type:boolean
gitHubForkDiscovery
Discovers pull requests where the origin repository is a fork of the target repository.
strategyId
Determines how pull requests are discovered:
Merging the pull request with the current target branch revision
Discover each pull request once with the discovered revision corresponding to the result of merging with the current revision of the target branch. Note that pushes to the target branch will result in new pull request builds.
The current pull request revision
Discover each pull request once with the discovered revision corresponding to the pull request head revision without merging.
Both the current pull request revision and the pull request merged with the current target branch revision
Discover each pull request twice. The first discovered revision corresponds to the result of merging with the current revision of the target branch in each scan. The second parallel discovered revision corresponds to the pull request head revision without merging.
Type:int
trust

One of the great powers of pull requests is that anyone with read access to a repository can fork it, commit some changes to their fork and then create a pull request against the original repository with their changes. There are some files stored in source control that are important. For example, a Jenkinsfile may contain configuration details to sandbox pull requests in order to mitigate against malicious pull requests. In order to protect against a malicious pull request itself modifying the Jenkinsfile to remove the protections, you can define the trust policy for pull requests from forks.

Other plugins can extend the available trust policies. The default policies are:

Nobody
Pull requests from forks will all be treated as untrusted. This means that where Jenkins requires a trusted file (e.g. Jenkinsfile) the contents of that file will be retrieved from the target branch on the origin repository and not from the pull request branch on the fork repository.
Collaborators
Pull requests from collaborators to the origin repository will be treated as trusted, all other pull requests from fork repositories will be treated as untrusted. Note that if credentials used by Jenkins for scanning the repository does not have permission to query the list of collaborators to the origin repository then only the origin account will be treated as trusted - i.e. this will fall back to Nobody. NOTE: all collaborators are trusted, even if they are only members of a team with read permission.
Everyone
All pull requests from forks will be treated as trusted. NOTE: this option can be dangerous if used on a public repository hosted on GitHub.
From users with Admin or Write permission
Pull requests forks will be treated as trusted if and only if the fork owner has either Admin or Write permissions on the origin repository. This is the recommended policy. Note that this strategy requires the Review a user's permission level API, as a result on GitHub Enterprise Server versions before 2.12 this is the same as trusting Nobody.
Nested choice of objects
gitHubTrustContributors
gitHubTrustEveryone
gitHubTrustNobody
gitHubTrustPermissions
browser
browser
Nested choice of objects
assembla
repoUrl
Specify the root URL serving this repository (such as https://www.assembla.com/code/PROJECT/git/).
Type:String
bitbucketServer
repoUrl
Specify the Bitbucket Server root URL for this repository (such as https://bitbucket:7990/OWNER/REPO/).
Type:String
bitbucket
repoUrl
Specify the root URL serving this repository (such as https://bitbucket.org/OWNER/REPO/).
Type:String
cgit
repoUrl
Specify the root URL serving this repository (such as https://cgit.example.com:port/group/REPO/).
Type:String
fisheye
repoUrl
Specify the URL of this repository in FishEye (such as https://fisheye.example.com/browse/project/).
Type:String
gitblit
repoUrl
Specify the root URL serving this repository.
Type:String
projectName
Specify the name of the project in GitBlit.
Type:String
gitLab
repoUrl
Specify the root URL serving this repository (such as https://gitlab.com/username/repository/).
Type:String
version (optional)
Specify the major and minor version of GitLab you use (such as 9.1). If you don't specify a version, a modern version of GitLab (>= 8.0) is assumed.
Type:String
gitLabBrowser
Specify the HTTP URL for this project's GitLab page so that links to changes can be automatically generated by Jenkins. The URL needs to include the owner and project. If the GitLab server is https://gitLab.example.com then the URL for bob's skunkworks project might be https://gitLab.example.com/bob/skunkworks.
projectUrl
Specify the HTTP URL for this project's GitLab page. The URL needs to include the owner and project so, for example, if the GitLab server is https://gitLab.example.com then the URL for bob's skunkworks project might be https://gitLab.example.com/bob/skunkworks
Type:String
gitList
repoUrl
Specify the root URL serving this repository (such as https://gitlist.example.com/repo/).
Type:String
gitWeb
repoUrl
Specify the root URL serving this repository (such as https://github.com/jenkinsci/jenkins.git).
Type:String
github
repoUrl
Specify the HTTP URL for this repository's GitHub page (such as https://github.com/jquery/jquery).
Type:String
gitiles
repoUrl
Specify the root URL serving this repository (such as https://gwt.googlesource.com/gwt/).
Type:String
$class: 'GitoriousWeb'
repoUrl
Specify the root URL serving this repository (such as https://gitorious.org/gitorious/mainline).
Type:String
gogs
repoUrl
Specify the root URL serving this repository (such as https://gogs.example.com/username/some-repo-url.git).
Type:String
kiln
repoUrl
Specify the root URL serving this repository (such as https://khanacademy.kilnhg.com/Code/Website/Group/webapp).
Type:String
phabricator
repoUrl
Specify the phabricator instance root URL (such as https://phabricator.example.com).
Type:String
repo
Specify the repository name in phabricator (such as the foo part of phabricator.example.com/diffusion/foo/browse).
Type:String
redmine
repoUrl
Specify the root URL serving this repository (such as https://redmine.example.com/PATH/projects/PROJECT/repository).
Type:String
rhodeCode
repoUrl
Specify the HTTP URL for this repository's RhodeCode page (such as https://rhodecode.example.com/projects/PROJECT/repos/REPO/).
Type:String
$class: 'Stash'
repoUrl
Specify the HTTP URL for this repository's Stash page (such as https://stash.example.com/projects/PROJECT/repos/REPO/).
Type:String
teamFoundation
repoUrl
Either the name of the remote whose URL should be used, or the URL of this module in TFS (such as https://tfs.example.com/tfs/PROJECT/_git/REPO/). If empty (default), the URL of the "origin" repository is used.

If TFS is also used as the repository server, this can usually be left blank.

Type:String
viewgit
repoUrl
Specify the root URL serving this repository (such as https://git.example.com/viewgit/).
Type:String
projectName
Specify the name of the project in ViewGit (e.g. scripts, scuttle etc. from https://code.fealdia.org/viewgit/).
Type:String
lfs
gitlabAvatar
disableProjectAvatar (optional)
Due to a GitLab bug, sometimes it is not possible to GitLab API to fetch GitLab Avatar for private projects or when the api doesn't have token access. You may choose to skip avatar for projects if you want to avoid broken or self generated avatars.
Type:boolean
gitlabMarkUnstableAsSuccess
markUnstableAsSuccess (optional)
Type:boolean
gitlabSkipNotifications
gitTool
gitTool
Type:String
gitLabHookRegistration
webHookMode
Type:String
systemHookMode
Type:String
gitHubIgnoreDraftPullRequestFilter
ignoreOnPush
localBranch
logComment
logSuccess (optional)
Sometimes the user doesn't want to log the builds that succeeded. The trait only enable logging of failed/aborted builds by default. Select this option to include logging of successful builds as well.
Type:boolean
sudoUser (optional)
Enter a sudo username of the user you want to comment as on GitLab Server. Remember the token specified should have api and sudo access both (which can only be created by your GitLab Server Admin). It is recommended to create a dummy user in your GitLab Server with an appropriate username like `jenkinsadmin` etc. Leave empty if you want use the owner of the project as the commenter.
Type:String
multiBranchProjectDisplayNaming
Some branch source plugins provide additional information about discovered branches like a title or subject of merge or change requests.
With this trait, that additional information can be used for the job display names.
Note: Job display name changes do not trigger builds.
displayNamingStrategy
The different strategies:
  • Job display name with fallback to name:
    Uses the branch source plugin's display name for the PR instead of the raw name
    Value for configuration-as-code: OBJECT_DISPLAY_NAME

  • Name and, if available, display name:
    Joins the raw name and the branch source plugin's display name
    Value for configuration-as-code: RAW_AND_OBJECT_DISPLAY_NAME

Values:
OBJECT_DISPLAY_NAME
RAW_AND_OBJECT_DISPLAY_NAME
gitLabOriginDiscovery
Discovers merge requests where the origin project is the same as the target project.
strategyId
Determines how merge requests are discovered:
Merging the merge request with the current target branch revision
Discover each merge request once with the discovered revision corresponding to the result of merging with the current revision of the target branch
The current merge request revision
Discover each merge request once with the discovered revision corresponding to the merge request head revision without merging
Both the current merge request revision and the merge request merged with the current target branch revision
Discover each merge request twice. The first discovered revision corresponds to the result of merging with the current revision of the target branch in each scan. The second parallel discovered revision corresponds to the merge request head revision without merging
Type:int
gitHubPullRequestDiscovery
Discovers pull requests where the origin repository is the same as the target repository.
strategyId
Determines how pull requests are discovered:
Merging the pull request with the current target branch revision
Discover each pull request once with the discovered revision corresponding to the result of merging with the current revision of the target branch. Note that pushes to the target branch will result in new pull request builds.
The current pull request revision
Discover each pull request once with the discovered revision corresponding to the pull request head revision without merging.
Both the current pull request revision and the pull request merged with the current target branch revision
Discover each pull request twice. The first discovered revision corresponds to the result of merging with the current revision of the target branch in each scan. The second parallel discovered revision corresponds to the pull request head revision without merging.
Type:int
pruneStaleBranch
pruneStaleTag
refSpecs
templates
Array/List:
Nested object
value
A ref spec to fetch. Any occurrences of @{remote} will be replaced by the remote name (which defaults to origin) before use.
Type:String
headRegexFilter
regex
A Java regular expression to restrict the names. Names that do not match the supplied regular expression will be ignored.
NOTE: this filter will be applied to all branch like things, including change requests
Type:String
remoteName
remoteName
Type:String
sparseCheckoutPaths
extension
Nested object

Specify the paths that you'd like to sparse checkout. This may be used for saving space (Think about a reference repository). Be sure to use a recent version of Git, at least above 1.7.10

sparseCheckoutPaths
Array/List:
Nested object
path
Type:String
submoduleOption
extension
submodule
depth (optional)
Set shallow clone depth, so that git will only download recent history of the project, saving time and disk space when you just want to access the latest commits of a repository.
Type:int
disableSubmodules (optional)
By disabling support for submodules you can still keep using basic git plugin functionality and just have Jenkins to ignore submodules completely as if they didn't exist.
Type:boolean
parentCredentials (optional)
Use credentials from the default remote of the parent project.
Type:boolean
recursiveSubmodules (optional)
Retrieve all submodules recursively (uses '--recursive' option which requires git>=1.6.5)
Type:boolean
reference (optional)
Specify a folder containing a repository that will be used by Git as a reference during clone operations.
This option will be ignored if the folder is not available on the controller or agent where the clone is being executed.
To prepare a reference folder with multiple subprojects, create a bare git repository and add all the remote urls then perform a fetch:
  git init --bare
  git remote add SubProject1 https://gitrepo.com/subproject1
  git remote add SubProject2 https://gitrepo.com/subproject2
  git fetch --all
  
Type:String
shallow (optional)
Perform shallow clone, so that git will not download the history of the project, saving time and disk space when you just want to access the latest version of a repository.
Type:boolean
threads (optional)
Specify the number of threads that will be used to update submodules.
If unspecified, the command line git default thread count is used.
Type:int
timeout (optional)
Specify a timeout (in minutes) for submodules operations.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
trackingSubmodules (optional)
Retrieve the tip of the configured branch in .gitmodules (Uses '--remote' option which requires git>=1.8.2)
Type:boolean
mrTriggerComment
commentBody
Add comment body you want to use to instruct Jenkins CI to rebuild the MR
Type:String
onlyTrustedMembersCanTrigger
Type:boolean
userIdentity
extension
Nested object
name

If given, "GIT_COMMITTER_NAME=[this]" and "GIT_AUTHOR_NAME=[this]" are set for builds. This overrides whatever is in the global settings.

Type:String
email

If given, "GIT_COMMITTER_EMAIL=[this]" and "GIT_AUTHOR_EMAIL=[this]" are set for builds. This overrides whatever is in the global settings.

Type:String
WebhookListenerBuildConditionsTrait
alwaysBuildMROpen (optional)
Type:boolean
alwaysBuildMRReOpen (optional)
Type:boolean
alwaysIgnoreMRApproval (optional)
Type:boolean
alwaysIgnoreMRApproved (optional)
Type:boolean
alwaysIgnoreMRUnApproval (optional)
Type:boolean
alwaysIgnoreMRUnApproved (optional)
Type:boolean
alwaysIgnoreMRWorkInProgress (optional)
Type:boolean
alwaysIgnoreNonCodeRelatedUpdates (optional)
GitLab will send a webhook to Jenkins when there are updates to the MR including title changes, labels removed/added, etc. Enabling this option will prevent a build running if the cause was one of these updates. Note: these settings do not have any impact on build from comment settings.
Type:boolean
headWildcardFilter
includes
Space-separated list of name patterns to consider. You may use * as a wildcard; for example: master release*
NOTE: this filter will be applied to all branch like things, including change requests
Type:String
excludes
Space-separated list of name patterns to ignore even if matched by the includes list. For example: release alpha-* beta-*
NOTE: this filter will be applied to all branch like things, including change requests
Type:String
$class: 'WipeWorkspaceTrait'
gitLabBranchDiscovery
Discovers branches on the repository.
strategyId
Determines which branches are discovered.
Only branches that are not also filed as MRs
If you are discovering origin merge requests, it may not make sense to discover the same changes both as a merge request and as a branch.
Only branches that are also filed as MRs
This option exists to preserve legacy behaviour when upgrading from older versions of the plugin. NOTE: If you have an actual use case for this option please file a merge request against this text.
All branches
Ignores whether the branch is also filed as a merge request and instead discovers all branches on the origin project.
Type:int
gitLabSshCheckout
By default the discovered branches / merge requests will all use the same username / password credentials that were used for discovery when checking out sources. This means that the checkout will be using the https:// protocol for the Git repository.

This behaviour allows you to select the SSH private key to be used for checking out sources, which will consequently force the checkout to use the ssh:// protocol.

credentialsId
Credentials used to check out sources. Must be a SSH key based credential.
Type:String
gitLabTagDiscovery
gitBranchDiscovery
Discovers branches on the repository.
gitTagDiscovery
Discovers tags on the repository.
gitHubBranchDiscovery
Discovers branches on the repository.
strategyId
Determines which branches are discovered.
Exclude branches that are also filed as PRs
If you are discovering origin pull requests, you may not want to also build the source branches for those pull requests.
Only branches that are also filed as PRs
Similar to discovering origin pull requests, but discovers the branch rather than the pull request. This means env.GIT_BRANCH will be set to the branch name rather than PR-#. Also, status notifications for these builds will only be applied to the commit and not to the pull request.
All branches
Ignores whether the branch is also filed as a pull request and instead discovers all branches on the origin repository.
Type:int
gitHubSshCheckout
By default the discovered branches / pull requests will all use the same username / password credentials that were used for discovery when checking out sources. This means that the checkout will be using the https:// protocol for the Git repository.

This behaviour allows you to select the SSH private key to be used for checking out sources, which will consequently force the checkout to use the ssh:// protocol.

credentialsId
Credentials used to check out sources. Must be a SSH key based credential.
Type:String
gitHubTagDiscovery
Discovers tags on the repository.
fromScm
name
The name of the SCM head/trunk/branch/tag that this source provides.
Type:String
scm
Nested choice of objects
scmGit

The git plugin provides fundamental git operations for Jenkins projects. It can poll, fetch, checkout, and merge contents of git repositories.

The git plugin provides an SCM implementation to be used with the Pipeline SCM checkout step. The Pipeline Syntax Snippet Generator guides the user to select git plugin checkout options and provides online help for each of the options.

Use the Pipeline Snippet Generator to generate a sample pipeline script for the checkout step. Examples of the checkout step include:

See the argument descriptions for more details.

The checkout step provides access to all the Pipeline capabilities provided by the git plugin:

checkout scmGit(userRemoteConfigs: [
                    [ url: 'https://github.com/jenkinsci/git-plugin' ]
                ])


NOTE: The checkout step is the preferred SCM checkout method. For simpler cases that do not require all the capabilities of the git plugin, the git step can also be used.

Use the Pipeline Snippet Generator to generate a sample pipeline script for the checkout step.

The checkout step can be used in many cases where the git step cannot be used. Refer to the git plugin documentation for detailed descriptions of options available to the checkout step. For example, the checkout step supports:

  • SHA-1 checkout
  • Tag checkout
  • Submodule checkout
  • Sparse checkout
  • Large file checkout (LFS)
  • Reference repositories
  • Branch merges
  • Repository tagging
  • Custom refspecs
  • Timeout configuration
  • Changelog calculation against a non-default reference
  • Stale branch pruning


Example: Checkout step with defaults

Checkout from the git plugin source repository using https protocol, no credentials, and the master branch.

The Pipeline Snippet Generator generates this example:

checkout scmGit(userRemoteConfigs: [
                    [ url: 'https://github.com/jenkinsci/git-plugin' ]
                ])

Example: Checkout step with https and a specific branch

Checkout from the Jenkins source repository using https protocol, no credentials, and a specific branch (stable-2.289).

The Pipeline Snippet Generator generates this example:

checkout scmGit(branches: [[name: 'stable-2.289']],
                userRemoteConfigs: [
                    [ url: 'https://github.com/jenkinsci/jenkins.git' ]
                ])

Example: Checkout step with ssh and a private key credential

Checkout from the git client plugin source repository using ssh protocol, private key credentials, and the master branch. The credential must be a private key credential if the remote git repository is accessed with the ssh protocol. The credential must be a username / password credential if the remote git repository is accessed with http or https protocol.

The Pipeline Snippet Generator generates this example:

checkout changelog: false,
         scm: scmGit(userRemoteConfigs: [
                         [ credentialsId: 'my-private-key-credential-id',
                           url: 'git@github.com:jenkinsci/git-client-plugin.git' ]
                         ])

Example: Checkout step with https and changelog disabled

Checkout from the Jenkins source repository using https protocol, no credentials, the master branch, and changelog calculation disabled. If changelog is false, then the changelog will not be computed for this job. If changelog is true or is not set, then the changelog will be computed. See the workflow scm step documentation for more changelog details.

The Pipeline Snippet Generator generates this example:

checkout changelog: false,
         scmGit(userRemoteConfigs: [
                    [ url: 'https://github.com/jenkinsci/credentials-plugin' ]
                ])

Example: Checkout step with git protocol and polling disabled

Checkout from the command line git repository using git protocol, no credentials, the master branch, and no polling for changes. If poll is false, then the remote repository will not be polled for changes. If poll is true or is not set, then the remote repository will be polled for changes. See the workflow scm step documentation for more polling details.

The Pipeline Snippet Generator generates this example:

checkout poll: false,
         scmGit(userRemoteConfigs: [
                    [ url: 'git://git.kernel.org/pub/scm/git/git.git ]
                ])


Argument Descriptions
userRemoteConfigs
Specify the repository to track. This can be a URL or a local file path. Note that for super-projects (repositories with submodules), only a local file path or a complete URL is valid. The following are examples of valid git URLs.
  • ssh://git@github.com/github/git.git
  • git@github.com:github/git.git (short notation for ssh protocol)
  • ssh://user@other.host.com/~/repos/R.git (to access the repos/R.git repository in the user's home directory)
  • https://github.com/github/git.git

If the repository is a super-project, the location from which to clone submodules is dependent on whether the repository is bare or non-bare (i.e. has a working directory).
  • If the super-project is bare, the location of the submodules will be taken from .gitmodules.
  • If the super-project is not bare, it is assumed that the repository has each of its submodules cloned and checked out appropriately. Thus, the submodules will be taken directly from a path like ${SUPER_PROJECT_URL}/${SUBMODULE}, rather than relying on information from .gitmodules.
For a local URL/path to a super-project, git rev-parse --is-bare-repository is used to detect whether the super-project is bare or not.
For a remote URL to a super-project, the ending of the URL determines whether a bare or non-bare repository is assumed:
  • If the remote URL ends with .git, a non-bare repository is assumed.
  • If the remote URL does NOT end with .git, a bare repository is assumed.
Array/List:
Nested object
url
Specify the URL or path of the git repository. This uses the same syntax as your git clone command.
Type:String
name
ID of the repository, such as origin, to uniquely identify this repository among other remote repositories. This is the same "name" that you use in your git remote command. If left empty, Jenkins will generate unique names for you.

You normally want to specify this when you have multiple remote repositories.

Type:String
refspec
A refspec controls the remote refs to be retrieved and how they map to local refs. If left blank, it will default to the normal behaviour of git fetch, which retrieves all the branch heads as remotes/REPOSITORYNAME/BRANCHNAME. This default behaviour is OK for most cases.

In other words, the default refspec is "+refs/heads/*:refs/remotes/REPOSITORYNAME/*" where REPOSITORYNAME is the value you specify in the above "name of repository" textbox.

When do you want to modify this value? A good example is when you want to just retrieve one branch. For example, +refs/heads/master:refs/remotes/origin/master would only retrieve the master branch and nothing else.

The plugin uses a default refspec for its initial fetch, unless the "Advanced Clone Option" is set to honor refspec. This keeps compatibility with previous behavior, and allows the job definition to decide if the refspec should be honored on initial clone.

Multiple refspecs can be entered by separating them with a space character. +refs/heads/master:refs/remotes/origin/master +refs/heads/develop:refs/remotes/origin/develop retrieves the master branch and the develop branch and nothing else.

See the refspec definition in Git user manual for more details.

Type:String
credentialsId
Credential used to check out sources.
Type:String
branches
List of branches to build. Jenkins jobs are most effective when each job builds only a single branch. When a single job builds multiple branches, the changelog comparisons between branches often show no changes or incorrect changes.
Array/List:
Nested object
name

Specify the branches if you'd like to track a specific branch in a repository. If left blank, all branches will be examined for changes and built.

The safest way is to use the refs/heads/<branchName> syntax. This way the expected branch is unambiguous.

If your branch name has a / in it make sure to use the full reference above. When not presented with a full path the plugin will only use the part of the string right of the last slash. Meaning foo/bar will actually match bar.

If you use a wildcard branch specifier, with a slash (e.g. release/), you'll need to specify the origin repository in the branch names to make sure changes are picked up. So e.g. origin/release/

Possible options:

  • <branchName>
    Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily the expected one. Better use refs/heads/<branchName>.
    E.g. master, feature1, ...
  • refs/heads/<branchName>
    Tracks/checks out the specified branch.
    E.g. refs/heads/master, refs/heads/feature1/master, ...
  • <remoteRepoName>/<branchName>
    Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily the expected one.
    Better use refs/heads/<branchName>.
    E.g. origin/master
  • remotes/<remoteRepoName>/<branchName>
    Tracks/checks out the specified branch.
    E.g. remotes/origin/master
  • refs/remotes/<remoteRepoName>/<branchName>
    Tracks/checks out the specified branch.
    E.g. refs/remotes/origin/master
  • <tagName>
    This does not work since the tag will not be recognized as tag.
    Use refs/tags/<tagName> instead.
    E.g. git-2.3.0
  • refs/tags/<tagName>
    Tracks/checks out the specified tag.
    E.g. refs/tags/git-2.3.0
  • <commitId>
    Checks out the specified commit.
    E.g. 5062ac843f2b947733e6a3b105977056821bd352, 5062ac84, ...
  • ${ENV_VARIABLE}
    It is also possible to use environment variables. In this case the variables are evaluated and the result is used as described above.
    E.g. ${TREEISH}, refs/tags/${TAGNAME}, ...
  • <Wildcards>
    The syntax is of the form: REPOSITORYNAME/BRANCH. In addition, BRANCH is recognized as a shorthand of */BRANCH, '*' is recognized as a wildcard, and '**' is recognized as wildcard that includes the separator '/'. Therefore, origin/branches* would match origin/branches-foo but not origin/branches/foo, while origin/branches** would match both origin/branches-foo and origin/branches/foo.
  • :<regular expression>
    The syntax is of the form: :regexp. Regular expression syntax in branches to build will only build those branches whose names match the regular expression.
    Examples:
    • :^(?!(origin/prefix)).*
      • matches: origin or origin/master or origin/feature
      • does not match: origin/prefix or origin/prefix_123 or origin/prefix-abc
    • :origin/release-\d{8}
      • matches: origin/release-20150101
      • does not match: origin/release-2015010 or origin/release-201501011 or origin/release-20150101-something
    • :^(?!origin/master$|origin/develop$).*
      • matches: origin/branch1 or origin/branch-2 or origin/master123 or origin/develop-123
      • does not match: origin/master or origin/develop

Type:String
browser
Defines the repository browser that displays changes detected by the git plugin.
Nested choice of objects
assembla
repoUrl
Specify the root URL serving this repository (such as https://www.assembla.com/code/PROJECT/git/).
Type:String
bitbucketServer
repoUrl
Specify the Bitbucket Server root URL for this repository (such as https://bitbucket:7990/OWNER/REPO/).
Type:String
bitbucket
repoUrl
Specify the root URL serving this repository (such as https://bitbucket.org/OWNER/REPO/).
Type:String
cgit
repoUrl
Specify the root URL serving this repository (such as https://cgit.example.com:port/group/REPO/).
Type:String
fisheye
repoUrl
Specify the URL of this repository in FishEye (such as https://fisheye.example.com/browse/project/).
Type:String
gitblit
repoUrl
Specify the root URL serving this repository.
Type:String
projectName
Specify the name of the project in GitBlit.
Type:String
gitLab
repoUrl
Specify the root URL serving this repository (such as https://gitlab.com/username/repository/).
Type:String
version (optional)
Specify the major and minor version of GitLab you use (such as 9.1). If you don't specify a version, a modern version of GitLab (>= 8.0) is assumed.
Type:String
gitLabBrowser
Specify the HTTP URL for this project's GitLab page so that links to changes can be automatically generated by Jenkins. The URL needs to include the owner and project. If the GitLab server is https://gitLab.example.com then the URL for bob's skunkworks project might be https://gitLab.example.com/bob/skunkworks.
projectUrl
Specify the HTTP URL for this project's GitLab page. The URL needs to include the owner and project so, for example, if the GitLab server is https://gitLab.example.com then the URL for bob's skunkworks project might be https://gitLab.example.com/bob/skunkworks
Type:String
gitList
repoUrl
Specify the root URL serving this repository (such as https://gitlist.example.com/repo/).
Type:String
gitWeb
repoUrl
Specify the root URL serving this repository (such as https://github.com/jenkinsci/jenkins.git).
Type:String
github
repoUrl
Specify the HTTP URL for this repository's GitHub page (such as https://github.com/jquery/jquery).
Type:String
gitiles
repoUrl
Specify the root URL serving this repository (such as https://gwt.googlesource.com/gwt/).
Type:String
$class: 'GitoriousWeb'
repoUrl
Specify the root URL serving this repository (such as https://gitorious.org/gitorious/mainline).
Type:String
gogs
repoUrl
Specify the root URL serving this repository (such as https://gogs.example.com/username/some-repo-url.git).
Type:String
kiln
repoUrl
Specify the root URL serving this repository (such as https://khanacademy.kilnhg.com/Code/Website/Group/webapp).
Type:String
phabricator
repoUrl
Specify the phabricator instance root URL (such as https://phabricator.example.com).
Type:String
repo
Specify the repository name in phabricator (such as the foo part of phabricator.example.com/diffusion/foo/browse).
Type:String
redmine
repoUrl
Specify the root URL serving this repository (such as https://redmine.example.com/PATH/projects/PROJECT/repository).
Type:String
rhodeCode
repoUrl
Specify the HTTP URL for this repository's RhodeCode page (such as https://rhodecode.example.com/projects/PROJECT/repos/REPO/).
Type:String
$class: 'Stash'
repoUrl
Specify the HTTP URL for this repository's Stash page (such as https://stash.example.com/projects/PROJECT/repos/REPO/).
Type:String
teamFoundation
repoUrl
Either the name of the remote whose URL should be used, or the URL of this module in TFS (such as https://tfs.example.com/tfs/PROJECT/_git/REPO/). If empty (default), the URL of the "origin" repository is used.

If TFS is also used as the repository server, this can usually be left blank.

Type:String
viewgit
repoUrl
Specify the root URL serving this repository (such as https://git.example.com/viewgit/).
Type:String
projectName
Specify the name of the project in ViewGit (e.g. scripts, scuttle etc. from https://code.fealdia.org/viewgit/).
Type:String
gitTool

Name of the git tool to be used for this job. Git tool names are defined in "Global Tool Configuration".

Type:String
extensions

Extensions add new behavior or modify existing plugin behavior for different uses. Extensions help users more precisely tune plugin behavior to meet their needs.

Extensions include:

  • Clone extensions modify the git operations that retrieve remote changes into the agent workspace. The extensions can adjust the amount of history retrieved, how long the retrieval is allowed to run, and other retrieval details.
  • Checkout extensions modify the git operations that place files in the workspace from the git repository on the agent. The extensions can adjust the maximum duration of the checkout operation, the use and behavior of git submodules, the location of the workspace on the disc, and more.
  • Changelog extensions adapt the source code difference calculations for different cases.
  • Tagging extensions allow the plugin to apply tags in the current workspace.
  • Build initiation extensions control the conditions that start a build. They can ignore notifications of a change or force a deeper evaluation of the commits when polling.
  • Merge extensions can optionally merge changes from other branches into the current branch of the agent workspace. They control the source branch for the merge and the options applied to the merge.

Array/List:
Nested choice of objects
authorInChangelog
The default behavior is to use the Git commit's "Committer" value in Jenkins' build changesets. If this option is selected, the Git commit's "Author" value would be used instead.
$class: 'BuildChooserSetting'
When you are interested in using a job to build multiple heads (most typically multiple branches), you can choose how Jenkins choose what branches to build in what order.

This extension point in Jenkins is used by many other plugins to control the job to build specific commits. When you activate those plugins, you may see them installing a custom strategy here.

buildChooser
Nested choice of objects
$class: 'AncestryBuildChooser'
maximumAgeInDays
Type:int
ancestorCommitSha1
Type:String
$class: 'DefaultBuildChooser'
$class: 'InverseBuildChooser'
buildSingleRevisionOnly
Disable scheduling for multiple candidate revisions.
If we have 3 branches:
----A--.---.--- B
         \-----C
jenkins would try to build (B) and (C).
This behaviour disables this and only builds one of them.
It is helpful to reduce the load of the Jenkins infrastructure when the SCM system like Bitbucket or GitHub should decide what commits to build.
changelogToBranch
This method calculates the changelog against the specified branch.
options
changelogBase
compareRemote
Name of the repository, such as origin, that contains the branch you specify below.
Type:String
compareTarget
The name of the branch within the named repository to compare against.
Type:String
checkoutOption
timeout
Specify a timeout (in minutes) for checkout.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
cleanBeforeCheckout
Clean up the workspace before every checkout by deleting all untracked files and directories, including those which are specified in .gitignore. It also resets all tracked files to their versioned state. This ensures that the workspace is in the same state as if you cloned and checked out in a brand-new empty directory, and ensures that your build is not affected by the files generated by the previous build.
deleteUntrackedNestedRepositories (optional)
Deletes untracked submodules and any other subdirectories which contain .git directories.
Type:boolean
cleanAfterCheckout
Clean up the workspace after every checkout by deleting all untracked files and directories, including those which are specified in .gitignore. It also resets all tracked files to their versioned state. This ensures that the workspace is in the same state as if you cloned and checked out in a brand-new empty directory, and ensures that your build is not affected by the files generated by the previous build.
deleteUntrackedNestedRepositories (optional)
Deletes untracked submodules and any other subdirectories which contain .git directories.
Type:boolean
cloneOption
shallow
Perform shallow clone, so that git will not download the history of the project, saving time and disk space when you just want to access the latest version of a repository.
Type:boolean
noTags
Deselect this to perform a clone without tags, saving time and disk space when you just want to access what is specified by the refspec.
Type:boolean
reference
Specify a folder containing a repository that will be used by Git as a reference during clone operations.
This option will be ignored if the folder is not available on the controller or agent where the clone is being executed.
Type:String
timeout
Specify a timeout (in minutes) for clone and fetch operations.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
depth (optional)
Set shallow clone depth, so that git will only download recent history of the project, saving time and disk space when you just want to access the latest commits of a repository.
Type:int
honorRefspec (optional)
Perform initial clone using the refspec defined for the repository. This can save time, data transfer and disk space when you only need to access the references specified by the refspec.
Type:boolean
$class: 'DisableRemotePoll'
Git plugin uses git ls-remote polling mechanism by default when configured with a single branch (no wildcards!). This compare the latest built commit SHA with the remote branch without cloning a local copy of the repo.

If you don't want to / can't use this.

If this option is selected, polling will require a workspace and might trigger unwanted builds (see JENKINS-10131).
lfs
Enable git large file support for the workspace by pulling large files after the checkout completes. Requires that the controller and each agent performing an LFS checkout have installed `git lfs`.
$class: 'IgnoreNotifyCommit'
If checked, this repository will be ignored when the notifyCommit-URL is accessed regardless of if the repository matches or not.
localBranch
If given, checkout the revision to build as HEAD on this branch.

If selected, and its value is an empty string or "**", then the branch name is computed from the remote branch without the origin. In that case, a remote branch origin/master will be checked out to a local branch named master, and a remote branch origin/develop/new-feature will be checked out to a local branch named develop/newfeature.

Please note that this has not been tested with submodules.

localBranch
Type:String
$class: 'MessageExclusion'
excludedMessage
If set, and Jenkins is set to poll for changes, Jenkins will ignore any revisions committed with message matched to Pattern when determining if a build needs to be triggered. This can be used to exclude commits done by the build itself from triggering another build, assuming the build server commits the change with a distinct message.

Exclusion uses Pattern matching

.*\[maven-release-plugin\].*
The example above illustrates that if only revisions with "[maven-release-plugin]" message in first comment line have been committed to the SCM a build will not occur.

You can create more complex patterns using embedded flag expressions.

(?s).*FOO.*
This example will search FOO message in all comment lines.
Type:String
$class: 'PathRestriction'
If set, and Jenkins is set to poll for changes, Jenkins will pay attention to included and/or excluded files and/or folders when determining if a build needs to be triggered.

Using this behaviour will preclude the faster git ls-remote polling mechanism, forcing polling to require a workspace thus sometimes triggering unwanted builds, as if you had selected the Force polling using workspace extension as well.

includedRegions
Each inclusion uses java regular expression pattern matching, and must be separated by a new line. An empty list implies that everything is included.

    myapp/src/main/web/.*\.html
    myapp/src/main/web/.*\.jpeg
    myapp/src/main/web/.*\.gif
  
The example above illustrates that a build will only occur, if html/jpeg/gif files have been committed to the SCM. Exclusions take precedence over inclusions, if there is an overlap between included and excluded regions.
Type:String
excludedRegions
Each exclusion uses java regular expression pattern matching, and must be separated by a new line.

    myapp/src/main/web/.*\.html
    myapp/src/main/web/.*\.jpeg
    myapp/src/main/web/.*\.gif
  
The example above illustrates that if only html/jpeg/gif files have been committed to the SCM a build will not occur.
Type:String
perBuildTag
Create a tag in the workspace for every build to unambiguously mark the commit that was built. You can combine this with Git publisher to push the tags to the remote repository.
$class: 'PreBuildMerge'
These options allow you to perform a merge to a particular branch before building. For example, you could specify an integration branch to be built, and to merge to master. In this scenario, on every change of integration, Jenkins will perform a merge with the master branch, and try to perform a build if the merge is successful. It then may push the merge back to the remote repository if the Git Push post-build action is selected.
options
Nested object
mergeTarget
The name of the branch within the named repository to merge to, such as master.
Type:String
fastForwardMode (optional)
Merge fast-forward mode selection.
The default, --ff, gracefully falls back to a merge commit when required.
For more information, see the Git Merge Documentation
Values:
FF
FF_ONLY
NO_FF
mergeRemote (optional)
Name of the repository, such as origin, that contains the branch you specify below. If left blank, it'll default to the name of the first repository configured above.
Type:String
mergeStrategy (optional)
Merge strategy selection. This feature is not fully implemented in JGIT.
Values:
DEFAULT
RESOLVE
RECURSIVE
OCTOPUS
OURS
SUBTREE
RECURSIVE_THEIRS
pruneStaleBranch
Run "git remote prune" for each remote, to prune obsolete local branches.
pruneTags
pruneTags
Type:boolean
$class: 'RelativeTargetDirectory'
relativeTargetDir
Specify a local directory (relative to the workspace root) where the Git repository will be checked out. If left empty, the workspace root itself will be used.

This extension should not be used in Jenkins Pipeline (either declarative or scripted). Jenkins Pipeline already provides standard techniques for checkout to a subdirectory. Use ws and dir in Jenkins Pipeline rather than this extension.

Type:String
$class: 'ScmName'

Unique name for this SCM. Needed when using Git within the Multi SCM plugin.

name
Type:String
$class: 'SparseCheckoutPaths'

Specify the paths that you'd like to sparse checkout. This may be used for saving space (Think about a reference repository). Be sure to use a recent version of Git, at least above 1.7.10

sparseCheckoutPaths
Array/List:
Nested object
path
Type:String
submodule
depth (optional)
Set shallow clone depth, so that git will only download recent history of the project, saving time and disk space when you just want to access the latest commits of a repository.
Type:int
disableSubmodules (optional)
By disabling support for submodules you can still keep using basic git plugin functionality and just have Jenkins to ignore submodules completely as if they didn't exist.
Type:boolean
parentCredentials (optional)
Use credentials from the default remote of the parent project.
Type:boolean
recursiveSubmodules (optional)
Retrieve all submodules recursively (uses '--recursive' option which requires git>=1.6.5)
Type:boolean
reference (optional)
Specify a folder containing a repository that will be used by Git as a reference during clone operations.
This option will be ignored if the folder is not available on the controller or agent where the clone is being executed.
To prepare a reference folder with multiple subprojects, create a bare git repository and add all the remote urls then perform a fetch:
  git init --bare
  git remote add SubProject1 https://gitrepo.com/subproject1
  git remote add SubProject2 https://gitrepo.com/subproject2
  git fetch --all
  
Type:String
shallow (optional)
Perform shallow clone, so that git will not download the history of the project, saving time and disk space when you just want to access the latest version of a repository.
Type:boolean
threads (optional)
Specify the number of threads that will be used to update submodules.
If unspecified, the command line git default thread count is used.
Type:int
timeout (optional)
Specify a timeout (in minutes) for submodules operations.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
trackingSubmodules (optional)
Retrieve the tip of the configured branch in .gitmodules (Uses '--remote' option which requires git>=1.8.2)
Type:boolean
$class: 'UserExclusion'
excludedUsers
If set, and Jenkins is set to poll for changes, Jenkins will ignore any revisions committed by users in this list when determining if a build needs to be triggered. This can be used to exclude commits done by the build itself from triggering another build, assuming the build server commits the change with a distinct SCM user.

Using this behaviour will preclude the faster git ls-remote polling mechanism, forcing polling to require a workspace thus sometimes triggering unwanted builds, as if you had selected the Force polling using workspace extension as well.

Each exclusion uses exact string comparison and must be separated by a new line. User names are only excluded if they exactly match one of the names in this list.

auto_build_user
The example above illustrates that if only revisions by "auto_build_user" have been committed to the SCM a build will not occur.
Type:String
$class: 'UserIdentity'
name

If given, "GIT_COMMITTER_NAME=[this]" and "GIT_AUTHOR_NAME=[this]" are set for builds. This overrides whatever is in the global settings.

Type:String
email

If given, "GIT_COMMITTER_EMAIL=[this]" and "GIT_AUTHOR_EMAIL=[this]" are set for builds. This overrides whatever is in the global settings.

Type:String
$class: 'WipeWorkspace'
Delete the contents of the workspace before building, ensuring a fully fresh workspace.
doGenerateSubmoduleConfigurations (optional)

Removed facility that was intended to test combinations of git submodule versions. Removed in git plugin 4.6.0. Ignores the user provided value and always uses false as its value.

Type:boolean
submoduleCfg (optional)

Removed facility that was intended to test combinations of git submodule versions. Removed in git plugin 4.6.0. Ignores the user provided value(s) and always uses empty values.

Array/List:
Nested object
submoduleName

Removed in git plugin 4.6.0.

Type:String
branches

Removed in git plugin 4.6.0.

Array/List:
Type:String
none
id (optional)
Type:String
clone (optional)
If checked, every build performs a fresh clone of the SCM rather than locking and updating a common copy. No changelog will be computed. For Git, you are advised to add Advanced clone behaviors and then check Shallow clone and Honor refspec on initial clone and uncheck Fetch tags to make the clone much faster. You may still enable Cache fetched versions on controller for quick retrieval if you prefer.
Type:boolean
libraryPath (optional)
A relative path from the root of the SCM to the root of the library. Leave this field blank if the root of the library is the root of the SCM. Note that ".." is not permitted as a path component to avoid security issues.
Type:String
libraryResource: Load a resource file from a library
Reads a resource from a library and returns its content as a plain string.
resource
Relative (/-separated) path to a resource in a library's /resources folder.
Type:String
encoding (optional)
The encoding to use when reading the resource. If left blank, the platform default encoding will be used. Binary files can be read into a Base64-encoded string by specifying "Base64" as the encoding.
Type:String
load: Evaluate a Groovy source file into the Pipeline script
Takes a filename in the workspace and runs it as Groovy source text.

The loaded file can contain statements at top level or just load and run a closure. For example:

    def pipeline
    node('agent') {
        pipeline = load 'pipeline.groovy'
        pipeline.functionA()
    }
    pipeline.functionB()
    

Where pipeline.groovy defines functionA and functionB functions (among others) before ending with return this;

path

Current directory (pwd()) relative path to the Groovy file to load.

Type:String
mail: Mail
Simple step for sending email.
subject
Email subject line.
Type:String
body
Email body.
Type:String
bcc (optional)
BCC email address list. Comma separated list of email addresses.
Type:String
cc (optional)
CC email address list. Comma separated list of email addresses.
Type:String
charset (optional)
Email body character encoding. Defaults to UTF-8
Type:String
from (optional)
From email address. Defaults to the admin address globally configured for the Jenkins instance.
Type:String
mimeType (optional)
Email body MIME type. Defaults to text/plain.
Type:String
replyTo (optional)
Reply-To email address. Defaults to the admin address globally configured for the Jenkins instance.
Type:String
to (optional)
To email address list. Comma separated list of email addresses.
Type:String
milestone: The milestone step forces all builds to go through in order

By default, Pipeline builds can run concurrently.

The milestone step forces all builds to go through in order, so an older build will never be allowed pass a milestone (it is aborted) if a newer build already passed it.

In general this step grants:

  • Builds pass milestones in order (taking the build number as sorter field).
  • Older builds will not proceed (they are aborted) if a newer one already passed the milestone.
  • When a build passes a milestone, any older build that passed the previous milestone but not this one is aborted.
  • Once a build passes the milestone, it will never be aborted by a newer build that didn't pass the milestone yet.

ordinal

An optional ordinal for the milestone. It is autogenerated if not explicitly set.

Setting explicit milestone ordinals grants that each milestone can be univocally identified across builds even when script changes are made during a previous build. If you plan to add or remove milestone steps while there are running builds and trigger new builds before the previous ones finished, then you should set explicit milestone ordinals. Otherwise, let the step autogenerate them as it runs.

Type:int
label (optional)

A label for the milestone. It's shown in the build log metadata.

Type:String
unsafe (optional)

An optional flag to allow unsafe execution of the milestone step. Do not set unless you understand the risks.

Currently this will allow the execution of a milestone step within a parallel step. It is assumed only 1 branch can contain a milestone step.

Type:boolean
mineRepository: Mine SCM repository
scm (optional)
Type:String
node: Allocate node
Allocates an executor on a node (typically a build agent) and runs further code in the context of a workspace on that agent.
label
Computer name, label name, or any other label expression like linux && 64bit to restrict where this step builds. May be left blank, in which case any available executor is taken.

Supported operators

The following operators are supported, in descending order of precedence:
(expression)
parentheses — used to explicitly define the associativity of an expression
!expression
NOT — negation; the result of expression must not be true
a && b
AND — both of the expressions a and b must be true
a || b
OR — either of the expressions a or b may be true
a -> b
"implies" operator — equivalent to !a || b.
For example, windows -> x64 could be thought of as "if a Windows agent is used, then that agent must be 64-bit", while still allowing this block to be executed on any agents that do not have the windows label, regardless of whether they have also have an x64 label
a <-> b
"if and only if" operator — equivalent to a && b || !a && !b
For example, windows <-> dc2 could be thought of as "if a Windows agent is used, then that agent must be in datacenter 2, but if a non-Windows agent is used, then it must not be in datacenter 2"

Notes

  • All operators are left-associative, i.e. a -> b -> c is equivalent to (a -> b) -> c.
  • Labels or agent names can be surrounded with quotation marks if they contain characters that would conflict with the operator syntax.
    For example, "osx (10.11)" || "Windows Server".
  • Expressions can be written without whitespace, but including it is recommended for readability; Jenkins will ignore whitespace when evaluating expressions.
  • Matching labels or agent names with wildcards or regular expressions is not supported.
  • An empty expression will always evaluate to true, matching all agents.

Examples

master
This block may be executed only on the Jenkins built-in node
linux-machine-42
This block may be executed only on the agent with the name linux-machine-42 (or on any machine that happens to have a label called linux-machine-42)
windows && jdk9
This block may be executed only on any Windows agent that has version 9 of the Java Development Kit installed (assuming that agents with JDK 9 installed have been given a jdk9 label)
postgres && !vm && (linux || freebsd)
This block may be executed only any on Linux or FreeBSD agent, so long as they are not a virtual machine, and they have PostgreSQL installed (assuming that each agent has the appropriate labels — in particular, each agent running in a virtual machine must have the vm label in order for this example to work as expected)
Type:String
nodejs: Provide Node & npm bin/ folder to PATH
nodeJSInstallationName
Type:String
cacheLocationStrategy (optional)
Nested choice of objects
default
executor
workspace
configId (optional)
Type:String
parallel: Execute in parallel
org.kohsuke.stapler.NoStaplerConstructorException: There's no @DataBoundConstructor on any constructor of class org.jenkinsci.plugins.workflow.cps.steps.ParallelStep
podTemplate: Define a podTemplate to use in the kubernetes plugin

Defines a Kubernetes pod template that can be used to create nodes.

Example:

podTemplate(...) {
    node(POD_LABEL) {
        // some steps
    }
}
activeDeadlineSeconds (optional)
Type:int
annotations (optional)
Array/List:
podAnnotation
key
The annotation key.
Type:String
value
The annotation value.
Type:String
cloud (optional)
The Kubernetes cloud to use to schedule the pod.
If unset, the first available Kubernetes cloud will be used.
Type:String
containers (optional)
Array/List:
containerTemplate
name
The name for the container to be run. One container is automatically created with the name jnlp, and runs the Jenkins agent. In order to replace the default agent image, the container with the agent must be named jnlp.
Type:String
image
Container image (repository, name, and tag) for a Jenkins inbound agent. Connection details will be passed as environment variables as per documentation.
Type:String
alwaysPullImage (optional)
If ticked, the latest version of the image will be pulled every time it is used. See Images - Kubernetes for the default Kubernetes behaviour.
Type:boolean
args (optional)

Arguments to pass to the command.

${computer.jnlpmac} and ${computer.name} are replaced with the agent secret and name respectively.

For Windows containers the args Start-Sleep 999999 are reasonable choices to go with powershell.

Type:String
command (optional)

Override the image entrypoint with a different one.

For Windows containers powershell is a good default.

Type:String
envVars (optional)
The environment variables to pass to the container.
Array/List:
Nested choice of objects
containerEnvVar
key
The environment variable key.
Type:String
value
The environment variable value.
Type:String
envVar
key
The environment variable key.
Type:String
value
The environment variable value.
Type:String
podEnvVar
key
The environment variable key.
Type:String
value
The environment variable value.
Type:String
secretEnvVar
key
The environment variable key.
Type:String
secretName
Name of secret to lookup from Kubernetes.
Type:String
secretKey
Key of secret to lookup from Kubernetes.
Type:String
optional
Whether this secret is optional.
Type:boolean
livenessProbe (optional)
containerLivenessProbe
execArgs
Command executed by the liveness probe.
Type:String
timeoutSeconds
Number of seconds after which the probe times out. Defaults to 1 second. Minimum value is 1.
Type:int
initialDelaySeconds
Number of seconds after the container has started before liveness or readiness probes are initiated. Defaults to 0 seconds. Minimum value is 0.
Type:int
failureThreshold

When a Pod starts and the probe fails, Kubernetes will try failureThreshold times before giving up.
Giving up in case of liveness probe means restarting the container.
In case of readiness probe the Pod will be marked Unready. Defaults to 3. Minimum value is 1.

Type:int
periodSeconds

How often (in seconds) to perform the probe. Default to 10 seconds. Minimum value is 1.

Type:int
successThreshold
Minimum consecutive successes for the probe to be considered successful after having failed. Defaults to 1. Must be 1 for liveness. Minimum value is 1.
Type:int
ports (optional)
Array/List:
portMapping
name (optional)
The name of the port
Type:String
containerPort (optional)
Port to expose into the pod
Type:int
hostPort (optional)
Port to expose onto the host
Type:int
privileged (optional)
Flag to mark the container as privileged.
Type:boolean
resourceLimitCpu (optional)
Kubernetes Resources Limit of CPU This value can be set to control the CPU resource limit passed when creating the Jenkins agent Docker container in Kubernetes. Unlike a resource request, this is the upper limit of resources used by your Jenkins Agent container. When left blank, the defaults of your Kubernetes cluster will be used. For more info, see the Kubernetes docs. e.g. `500m`.
Type:String
resourceLimitEphemeralStorage (optional)
Type:String
resourceLimitMemory (optional)
Kubernetes Resources Limit of Memory This value can be set to control the memory resource limit passed when creating the Jenkins agent Docker container in Kubernetes. Unlike a resource request, this is the upper limit of resources used by your Jenkins Agent container. When left blank, the defaults of your Kubernetes cluster will be used. For more info, see the Kubernetes docs. e.g. `250Mi`.
Type:String
resourceRequestCpu (optional)
Kubernetes Resources Request of CPU This value can be set to control the CPU resources requested when creating the Jenkins agent Docker container in Kubernetes. When left blank, the defaults of your Kubernetes cluster will be used. For more info, see the Kubernetes docs. e.g. `500m`.
Type:String
resourceRequestEphemeralStorage (optional)
Type:String
resourceRequestMemory (optional)
Kubernetes Resources Request of Memory This value can be set to control the memory resources requested when creating the Jenkins agent Docker container in Kubernetes. When left blank, the defaults of your Kubernetes cluster will be used. For more info, see the Kubernetes docs. e.g. `250Mi`.
Type:String
runAsGroup (optional)
Specify the gid to run as.
Type:String
runAsUser (optional)
Specify the uid to run as.
Type:String
shell (optional)
Type:String
ttyEnabled (optional)
Whether this container should allocate a TTY for itself.
Type:boolean
workingDir (optional)
Path to the root of the workspace from the view point of this container, such as /home/jenkins/agent.
Type:String
envVars (optional)
Array/List:
Nested choice of objects
containerEnvVar
key
The environment variable key.
Type:String
value
The environment variable value.
Type:String
envVar
key
The environment variable key.
Type:String
value
The environment variable value.
Type:String
podEnvVar
key
The environment variable key.
Type:String
value
The environment variable value.
Type:String
secretEnvVar
key
The environment variable key.
Type:String
secretName
Name of secret to lookup from Kubernetes.
Type:String
secretKey
Key of secret to lookup from Kubernetes.
Type:String
optional
Whether this secret is optional.
Type:boolean
hostNetwork (optional)
Type:boolean
idleMinutes (optional)
Type:int
imagePullSecrets (optional)
Array/List:
Type:String
inheritFrom (optional)
Type:String
instanceCap (optional)
Type:int
label (optional)
Jenkins node label to bind. If left blank, one will be generated for you, and inside the step it will be bound to the variable POD_LABEL so you can use this as the argument to the node step.
Example:
        podTemplate(...) {
            node(POD_LABEL) {
                // some steps
            }
        }
    
Type:String
name (optional)
Type:String
namespace (optional)
Type:String
nodeSelector (optional)
Type:String
nodeUsageMode (optional)
Type:String
podRetention (optional)
Nested choice of objects
always
default
never
onFailure
runAsGroup (optional)
Type:String
runAsUser (optional)
Type:String
schedulerName (optional)
Type:String
serviceAccount (optional)
Type:String
showRawYaml (optional)
Type:boolean
slaveConnectTimeout (optional)
Type:int
supplementalGroups (optional)
Type:String
volumes (optional)
Array/List:
Nested choice of objects
configMapVolume
mountPath
Path to mount this volume inside the pod.
Type:String
configMapName
The name of the Kubernetes Config Map to mount into the pod.
Type:String
optional
Whether this configmap needs to exist.
Type:boolean
subPath (optional)
SubPath to mount this volume inside the pod.
Type:String
dynamicPVC
accessModes (optional)
A PersistentVolume can be mounted on a host in any way supported by the resource provider. Providers will have different capabilities and each PV’s access modes are set to the specific modes supported by that particular volume. For example, NFS can support multiple read/write clients, but a specific NFS PV might be exported on the server as read-only. Each PV gets its own set of access modes describing that specific PV’s capabilities. Defaults to ReadWriteOnce.
Type:String
mountPath (optional)
Path to mount this volume inside the pod.
Type:String
requestsSize (optional)
Claims, like pods, can request specific quantities of a resource. In this case, the request is for storage. The same resource model applies to both volumes and claims. Defaults to 10Gi.
Type:String
storageClassName (optional)
A StorageClass provides a way for administrators to describe the “classes” of storage they offer. Different classes might map to quality-of-service levels, or to backup policies, or to arbitrary policies determined by the cluster administrators. Kubernetes itself is unopinionated about what classes represent. This concept is sometimes called “profiles” in other storage systems.
Type:String
emptyDirVolume
mountPath
Path to mount this volume inside the pod.
Type:String
memory
Flag for in-memory volume.
Type:boolean
genericEphemeralVolume
accessModes (optional)
A PersistentVolume can be mounted on a host in any way supported by the resource provider. Providers will have different capabilities and each PV’s access modes are set to the specific modes supported by that particular volume. For example, NFS can support multiple read/write clients, but a specific NFS PV might be exported on the server as read-only. Each PV gets its own set of access modes describing that specific PV’s capabilities. Defaults to ReadWriteOnce.
Type:String
mountPath (optional)
Path to mount this volume inside the pod.
Type:String
requestsSize (optional)
Claims, like pods, can request specific quantities of a resource. In this case, the request is for storage. The same resource model applies to both volumes and claims. Defaults to 10Gi.
Type:String
storageClassName (optional)
A StorageClass provides a way for administrators to describe the “classes” of storage they offer. Different classes might map to quality-of-service levels, or to backup policies, or to arbitrary policies determined by the cluster administrators. Kubernetes itself is unopinionated about what classes represent. This concept is sometimes called “profiles” in other storage systems.
Type:String
hostPathVolume
hostPath
File or directory on the host node's filesystem to mount into the pod.
Type:String
mountPath
Path to mount this volume inside the pod.
Type:String
readOnly
Flag for read-only mount, set hostPath mount to readOnly is considered best-practice.
Type:boolean
nfsVolume
serverAddress
NFS Server Address.
Type:String
serverPath
NFS Server Path.
Type:String
readOnly
Type:boolean
mountPath
Path to mount this volume inside the pod.
Type:String
persistentVolumeClaim
mountPath
Path to mount this volume inside the pod.
Type:String
claimName
The claim name.
Type:String
readOnly
Flag for read-only volume.
Type:boolean
secretVolume
mountPath
Path to mount this volume inside the pod.
Type:String
secretName
The name of the Kubernetes Secret to mount into the pod.
Type:String
defaultMode
The file permissions for the secret volume. Does not support Octal notation.
Type:String
optional
Whether the secret needs to exist.
Type:boolean
workingDir (optional)
Type:String
workspaceVolume (optional)
Nested choice of objects
dynamicPVC
accessModes (optional)
A PersistentVolume can be mounted on a host in any way supported by the resource provider. Providers will have different capabilities and each PV’s access modes are set to the specific modes supported by that particular volume. For example, NFS can support multiple read/write clients, but a specific NFS PV might be exported on the server as read-only. Each PV gets its own set of access modes describing that specific PV’s capabilities. Defaults to ReadWriteOnce.
Type:String
requestsSize (optional)
Claims, like pods, can request specific quantities of a resource. In this case, the request is for storage. The same resource model applies to both volumes and claims. Defaults to 10Gi.
Type:String
storageClassName (optional)
A StorageClass provides a way for administrators to describe the “classes” of storage they offer. Different classes might map to quality-of-service levels, or to backup policies, or to arbitrary policies determined by the cluster administrators. Kubernetes itself is unopinionated about what classes represent. This concept is sometimes called “profiles” in other storage systems.
Type:String
emptyDirWorkspaceVolume
memory
Flag for in-memory volume.
Type:boolean
genericEphemeralVolume
accessModes (optional)
A PersistentVolume can be mounted on a host in any way supported by the resource provider. Providers will have different capabilities and each PV’s access modes are set to the specific modes supported by that particular volume. For example, NFS can support multiple read/write clients, but a specific NFS PV might be exported on the server as read-only. Each PV gets its own set of access modes describing that specific PV’s capabilities. Defaults to ReadWriteOnce.
Type:String
requestsSize (optional)
Claims, like pods, can request specific quantities of a resource. In this case, the request is for storage. The same resource model applies to both volumes and claims. Defaults to 10Gi.
Type:String
storageClassName (optional)
A StorageClass provides a way for administrators to describe the “classes” of storage they offer. Different classes might map to quality-of-service levels, or to backup policies, or to arbitrary policies determined by the cluster administrators. Kubernetes itself is unopinionated about what classes represent. This concept is sometimes called “profiles” in other storage systems.
Type:String
hostPathWorkspaceVolume
hostPath
File or directory on the host node's filesystem to mount into the pod.
Type:String
nfsWorkspaceVolume
serverAddress
NFS Server Address.
Type:String
serverPath
NFS Server Path.
Type:String
readOnly
Type:boolean
persistentVolumeClaimWorkspaceVolume
claimName
The claim name.
Type:String
readOnly
Flag for read-only volume.
Type:boolean
yaml (optional)
Type:String
yamlMergeStrategy (optional)
Nested choice of objects
merge
override
powershell: Windows PowerShell Script
script
Executes a Windows PowerShell script (version 3 or later). Multiple lines allowed.
Note: be aware of the differences between Windows PowerShell and PowerShell Core, check which one is available on your agents.
Type:String
encoding (optional)
Encoding of process output. In the case of returnStdout, applies to the return value of this step; otherwise, or always for standard error, controls how text is copied to the build log. If unspecified, uses the system default encoding of the node on which the step is run. If there is any expectation that process output might include non-ASCII characters, it is best to specify the encoding explicitly. For example, if you have specific knowledge that a given process is going to be producing UTF-8 yet will be running on a node with a different system encoding (typically Windows, since every Linux distribution has defaulted to UTF-8 for a long time), you can ensure correct output by specifying: encoding: 'UTF-8'
Type:String
label (optional)
Label to be displayed in the pipeline step view and blue ocean details for the step instead of the step type. So the view is more meaningful and domain specific instead of technical.
Type:String
returnStatus (optional)
Normally, a script which exits with a nonzero status code will cause the step to fail with an exception. If this option is checked, the return value of the step will instead be the status code. You may then compare it to zero, for example.
Type:boolean
returnStdout (optional)
If checked, standard output from the task is returned as the step value as a String, rather than being printed to the build log. (Standard error, if any, will still be printed to the log.) You will often want to call .trim() on the result to strip off a trailing newline.
Type:boolean
properties: Set job properties
Updates the properties of the job which runs this step. Mainly useful from multibranch Pipelines, so that Jenkinsfile itself can encode what would otherwise be static job configuration. Existing properties set through the Jenkins UI for non-multibranch Pipelines will be preserved.
properties
Array/List:
Nested choice of objects
authorizationMatrix
entries
Array/List:
Nested choice of objects
group
name
Type:String
permissions
Array/List:
Type:String
user
name
Type:String
permissions
Array/List:
Type:String
userOrGroup
name
Type:String
permissions
Array/List:
Type:String
inheritanceStrategy (optional)
Nested choice of objects
inheritingGlobal
inheriting
nonInheriting
$class: 'AuthorizeProjectProperty'
Run builds with specified authorization. Authorization of builds defaults to SYSTEM privilege. You can restrict builds to access other projects in Jenkins by specifying authorization when plugins perform access check properly.
strategy
Nested choice of objects
$class: 'AnonymousAuthorizationStrategy'
Run a build as an anonymous user.
$class: 'SpecificUsersAuthorizationStrategy'
Run a build as a specified user. You are required to one of following condition to successfully save the configuration.
  • You are an administrator.
  • You yourself are the specified user.
  • The specified user is not changed from the last configuration, and "No need for re-authentication" was checked in the last configuration.
  • You enter the password for the specified user.
userid
ID of the user to run builds as.
Type:String
useApitoken
Type:boolean
apitoken
Type:String
password
Password of the user specified in User ID. This field is shown only when authentication is required for this user.

You can use API token for authentication instead by checking "Use API Token for authentication". You can get your API token from your user configuration page.

Type:String
dontRestrictJobConfiguration (optional)

"Run as Specific User" restricts the job configuration only to the specified user. Other users cannot configure the job even if the Jenkins access control configuration allows it.

This option disabled that feature, and the job configuration is controlled by the Jenkins access control.

Use this feature carefully, for a malicious user can run unintended commands without authentication by changing configuration of the job. Check the access control configuration, and ensure that the CONFIGURE permission for this job is granted only to proper users.

Type:boolean
$class: 'SystemAuthorizationStrategy'
Run a build as the SYSTEM user.
$class: 'TriggeringUsersAuthorizationStrategy'
Run a build as a user who triggered it. If the build was triggered as a downstream build, the build runs as a user who triggered the upstream build. This does not work when the build is triggered by SCM polling or scheduled triggering. The build runs as SYSTEM authorization in those cases.
buildDiscarder
This determines when, if ever, build records for this project should be discarded. Build records include the console output, archived artifacts, and any other metadata related to a particular build.

Keeping fewer builds means less disk space will be used in the Build Record Root Directory , which is specified on the Configure System screen.

Jenkins offers two options for determining when builds should be discarded:

  1. Build age: discard builds when they reach a certain age; for example, seven days old.
  2. Build count: discard the oldest build when a certain number of builds already exist.
These two options can be active at the same time, so you can keep builds for 14 days, but only up to a limit of 50 builds, for example. If either limit is exceeded, then any builds beyond that limit will be discarded.

You can also ensure that important builds are kept forever, regardless of the setting here — click the Keep this build forever button on the build page.
The last stable and last successful build are also excluded from these rules.


In the Advanced section, the same options can be specified, but specifically for build artifacts . If enabled, build artifacts will be discarded for any builds which exceed the defined limits. The builds themselves will still be kept; only the associated artifacts, if any, will be deleted.

For example, if a project builds some software and produces a large installer, which is archived, you may wish to always keep the console log and information about which source control commit was built, while for disk space reasons, you may want to keep only the last three installers that were built.
This can make sense for projects where you can easily recreate the same artifacts later by building the same source control commit again.


Note that Jenkins does not discard items immediately when this configuration is updated, or as soon as any of the configured values are exceeded; these rules are evaluated each time a build of this project completes.
strategy
Nested choice of objects
logRotator
daysToKeepStr
Type:String
numToKeepStr
Type:String
artifactDaysToKeepStr
Type:String
artifactNumToKeepStr
Type:String
$class: 'ConfigurationPermissionEnforcer'
disableConcurrentBuilds
abortPrevious (optional)
By default, disabling concurrent builds means that new builds will queue up and wait for a running build to complete. With this option, scheduling a new build immediately aborts any running build. This is handy for example if you have an expensive pull request testing procedure and do not wish to waste any time completing tests on an outdated commit.
Type:boolean
disableResume
durabilityHint

This setting allows users to change the default durability mode for running Pipelines. In most cases this is a trade-off between performance and the ability for running pipelines to resume after unplanned Jenkins outages.

What does this do?

  • Previously, running pipelines wrote data constantly, so that they could resume even if Jenkins fails. This setting gives the user the ability to adjust this write behavior.
  • Higher-performance/lower-durability modes write data to disk much less often for running pipelines.
  • Writing data less often can massively reduce build times for Pipelines with many steps or complex logic. For pipelines which spend most of their time waiting for a shell/batch script to run, the difference will be less visible.
  • Running pipelines with lower durability settings may lose data if they do not finish and Jenkins is not shut down gracefully:
    • A "graceful" shutdown where Jenkins goes through a full shutdown process, such as visiting http://[jenkins-server]/exit
    • A "dirty" shutdown, such as using kill -9 to terminate the Jenkins process, may prevent incomplete pipelines from persisting data
  • Pipelines that cannot persist data may not be able to resume or displayed in Blue Ocean/Stage View/etc.
  • Pipelines will generally write log data regardless of durability settings.
  • Some modes use an "atomic write" option - this helps ensure that pipeline build files aren't overwritten or left partially written if something fails.
  • Atomic writes may place more stress on filesystems, so especially with networked storage it may be faster not to use them.

Note: defaults also be set globally under Manage Jenkins > Configure System.

hint
Values:
PERFORMANCE_OPTIMIZED
SURVIVABLE_NONATOMIC
MAX_SURVIVABILITY
gitLabConnection
gitLabConnection
Type:String
jobCredentialId (optional)
Type:String
useAlternativeCredential (optional)
Type:boolean
githubProjectProperty
projectUrlStr

Enter the URL for the GitHub hosted project (without the tree/master or tree/branch part).

For example: https://github.com/rails/rails for the Rails project.

Type:String
displayName (optional)

This value will be used as context name for commit status if status builder or status publisher is defined for this project. It should be small and clear.

If you leave it empty, job name will be used for builder and publisher.

Type:String
$class: 'JobLocalConfiguration'
changeReasonComment
The change reason provided at the diff view.
Type:String
overrideIndexTriggers

Allows overriding default treatment of branch indexing triggers.

If branch indexing triggers are disabled at the multibranch or organization label, selecting this will enable them for this job only.

Otherwise, leaving the checkbox unselected will disable branch indexing triggers for this job only.

enableTriggers
Type:boolean
parameters
Parameters allow you to prompt users for one or more inputs that will be passed into a build. For example, you might have a project that runs tests on demand by allowing users to upload a zip file with binaries to be tested. This could be done by adding a File Parameter here.
Or you might have a project that releases some software, and you want users to enter release notes that will be uploaded along with the software. This could be done by adding a Multi-line String Parameter here.

Each parameter has a Name and some sort of Value , depending on the parameter type. These name-value pairs will be exported as environment variables when the build starts, allowing subsequent parts of the build configuration (such as build steps) to access those values, e.g. by using the ${PARAMETER_NAME} syntax (or %PARAMETER_NAME% on Windows).
This also implies that each parameter defined here should have a unique Name .

When a project is parameterized, the usual Build Now link will be replaced with a Build with Parameters link, where users will be prompted to specify values for each of the defined parameters. If they choose not to enter anything, the build will start with the default value for each parameter.

If a build is started automatically, for example if started by an SCM trigger, the default values for each parameter will be used.

When a parameterized build is in the queue, attempting to start another build of the same project will only succeed if the parameter values are different, or if the Execute concurrent builds if necessary option is enabled.

See the Parameterized Builds documentation for more information about this feature.

parameterDefinitions
Array/List:
Nested choice of objects
booleanParam
name
Type:String
defaultValue (optional)
Type:boolean
description (optional)
Type:String
choice
name
Type:String
description (optional)
Type:String
choices (optional)
Nested choice of objects
(not enumerable)
credentials
Defines a credentials parameter, which you can use during a build.

For security reasons, the credential is NOT directly exposed, the ID of the credential is exposed.

However, the selected credential is available through variable substitution in some other parts of the configuration. The string value will be the ID of the credential. A supporting plugin can thus use the ID to retrieve the selected credential and expose it to the build in an appropriate way.
name
Type:String
defaultValue
The default credentials to use.
Type:String
credentialType
Type:String
required
When this option is selected, the credentials selection drop down will not provide the empty selection as one of the options. This will not prevent a build without a value if there are no credentials available, for example if the job does not have access to any credentials of the correct type or there is no default value and the user starting the build either does not have any credentials of the correct type in their personal credentials store or they do not have permissions on the job to use credentials from their personal store.
Type:boolean
description (optional)
Type:String
file
name
Type:String
description (optional)
Type:String
gitParameter

When used, this parameter will present at build-time a choice to select a Git tag (or revision number) which set a parameter for parametrized build.

Be aware that git does not allow us get additional information (like author/commmit date) from a remote URL this plugin will silently clone the project when your workspace is empty. This may take a long time when we have a slow connection and/or the checkout is big.

Often the parameter defined in the "Name" field is used to specify the branch of the git checkout.

name
The name of the parameter.
Type:String
type
The type of the list of parameters:
  • Tag - list of all commit tags in repository - returns Tag Name
  • Branch - list of all branch in repository - returns Branch Name
  • Revision - list of all revision sha1 in repository followed by its author and date - returns Tag SHA1
Type:String
defaultValue
This value is returned when the list is empty or if an error occurs while retrieving data.
Type:String
branch
Name of branch to look in. Used only if listing revisions.
Type:String
branchFilter
Regex used to filter displayed branches. If blank, the filter will default to ".*".
Remote branches will be listed with the remote name first. E.g., "origin/master"
Type:String
tagFilter
This parameter is used to get tag from git.
If is blank, parameter is set to "*".
Properly is executed command: git ls-remote -t <repository> "*" or git ls-remote -t <repository> "$tagFilter".
git-ls-remote documentation.
Type:String
sortMode
Select how to sort the downloaded parameters. Only applies to a branch or a tag.
  • none
  • ascending smart
  • descending smart
  • ascending
  • descending
When smart sorting is chosen, the compare treats a sequence of digits as a single character.
Values:
NONE
ASCENDING_SMART
DESCENDING_SMART
ASCENDING
DESCENDING
selectedValue
Which value is selected, after loaded parameters.
If you choose 'default', but default value is not present on the list, nothing is selected.
Values:
NONE
TOP
DEFAULT
useRepository
If in the task are defined multiple repositories, this option specifies which the repository is taken into account on getting data.
If the option is not defined, is taken a first defined repository.
This option is a regular expression, which is compared to the 'Repository URL'.
Type:String
quickFilterEnabled
When this option is enabled will show a text field.
Parameter is filtered on the fly.
Type:boolean
description (optional)
A description that will be shown to the user later.
Type:String
listSize (optional)
Specify the number of items the list will display. A value of 0 will display as a DropDown list.
Type:String
requiredParameter (optional)
When this option is selected the user must select an option or an error will be thrown(default values are ignored)
Type:boolean
password
Pass a password to your build. The password entered here is made available to the build in plain text as an environment variable like a string parameter would be. The value will be stored encrypted on the Jenkins controller, similar to passwords in Jenkins configuration.
name
Type:String
defaultValueAsSecret
org.kohsuke.stapler.NoStaplerConstructorException: There's no @DataBoundConstructor on any constructor of class hudson.util.Secret
description (optional)
Type:String
$class: 'PromotedBuildParameterDefinition'
name
Type:String
jobName
Type:String
process
Type:String
description (optional)
Type:String
run
name
Type:String
projectName
Type:String
filter
Values:
ALL
STABLE
SUCCESSFUL
COMPLETED
description (optional)
Type:String
string
name
Type:String
defaultValue (optional)
Type:String
description (optional)
Type:String
trim (optional)
Strip whitespace from the beginning and end of the string.
Type:boolean
text
name
Type:String
defaultValue (optional)
Type:String
description (optional)
Type:String
trim (optional)
Strip whitespace from the beginning and end of the string.
Type:boolean
pipelineTriggers
triggers
Array/List:
Nested choice of objects
$class: 'GhprbTrigger'
adminlist
Type:String
whitelist
Type:String
orgslist
Type:String
cron
Type:String
triggerPhrase
When filled, commenting this phrase in the pull request will trigger a build. Matches case insensitively and supports regular expressions (e.g. .*(re)?run tests.*).
Type:String
onlyTriggerPhrase
When checked, only commenting the trigger phrase in the pull request will trigger a build. All other methods of triggering a pull request build are disabled.
Type:boolean
useGitHubHooks
Checking this option will disable regular polling (cron) for changes in GitHub and will try to create a GitHub hook. Creating a GitHub hook requires that the user which is specified in the GitHub Pull Request Builder configuration has admin rights to the specified repository.
By default, GitHub hooks created this way will have SSL certificate verification enabled. To disable SSL certificate verification in these GitHub hooks, start Jenkins with system property org.jenkinsci.plugins.ghprb.GhprbRepository.webhook.insecure set to true.
If you want to create a hook manually set it for event types: issue_comment, pull_request and url < your jenkins server url >/ghprbhook/. The url should be composed of your full jenkins server url plus the ending /ghprbhook/ path. If your jenkins server is just a domain like https://jenkins.yourcompany.com then the url would look like https://jenkins.yourcompany.com/ghprbhook/. If your jenkins server is accessed at a path off of a domain like https://yourcompany.com/jenkins then the url would look like https://yourcompany.com/jenkins/ghprbhook/
. Your Jenkins server must be accessible from internet.
Type:boolean
permitAll
This is dangerous!!! With this option enabled everyone can run his own code on your machine!
Type:boolean
autoCloseFailedPullRequests
Type:boolean
displayBuildErrorsOnDownstreamBuilds
Type:boolean
commentFilePath
Type:String
skipBuildPhrase
When filled, adding this phrase to the pull request title or body will not trigger a build.
Type:String
blackListCommitAuthor
When filled, pull request commits from this user(s) will not trigger a build. (Note: this can be overridden by job-specific configuration.)
Type:String
whiteListTargetBranches
Adding branches to this whitelist allows you to selectively test pull requests destined for these branches only.
Supports regular expressions (e.g. 'master', 'feature-.*').
Array/List:
Nested object
branch
Type:String
blackListTargetBranches
Adding branches to this blacklist allows you to prevent pull requests for specific branches.
Supports regular expressions (e.g. 'master', 'feature-.*').
Array/List:
Nested object
branch
Type:String
allowMembersOfWhitelistedOrgsAsAdmin
Use this option to allow members of whitelisted organisations to behave like admins, i.e. whitelist users and trigger pull request testing.
Type:boolean
msgSuccess
Type:String
msgFailure
Type:String
commitStatusContext
Type:String
gitHubAuthId
Type:String
buildDescTemplate
Set the build description. The default is: <a title=\"$title\" href=\"$url\">PR #$pullId</a>: $abbrTitle
Type:String
blackListLabels
Type:String
whiteListLabels
Type:String
extensions
Array/List:
Nested choice of objects
$class: 'GhprbBuildLog'
logExcerptLines
Type:int
$class: 'GhprbBuildStatus'
messages
Global: Sets a default for each job, if the job setup has no entries then this is used.

Add a text message to the comment posted to the pull request on build completion.
Array/List:
Nested object
result
Choose either SUCCESS, ERROR, or FAILURE for when the message is appended to the comment that is added to the pull request.
Values:
PENDING
SUCCESS
ERROR
FAILURE
message
The message that is appended to a comment when a build finishes with the desired build status. If no status updates should be made when a build finishes with the indicated build status, use "--none--" to alert the trigger.
Type:String
$class: 'GhprbCancelBuildsOnUpdate'
overrideGlobal
Type:boolean
$class: 'GhprbCommentFile'
commentFilePath
Extends the standard build comment message on github with a custom message file.
Type:String
$class: 'GhprbNoCommitStatus'
$class: 'GhprbPublishJenkinsUrl'
publishedURL
Sometimes Jenkins is set up behind a firewall and normal access is restricted. This URL will be added to a comment appended to the Pull Request.
Type:String
$class: 'GhprbSimpleStatus'
showMatrixStatus
Type:boolean
commitStatusContext
Context: A string label to differentiate this status from the status of other systems. Default: "default"
Type:String
statusUrl
Use a custom url instead of the Jenkins job url. If the desired url should be blank, use "--none--" to alert the trigger to use a blank url.
Type:String
triggeredStatus
Use a custom status for when a build is triggered. If the field is left blank then the default value is used instead. If no status updates should be made when a build is triggered, use "--none--" to alert the trigger.
Type:String
startedStatus
Use a custom status for when a build is started. If the field is left blank then the default value is used instead. If no status updates should be made when a build is started, use "--none--" to alert the trigger.
Type:String
addTestResults
Type:boolean
completedStatus
Use a custom status on the commit for when a build is completed. If the field is left blank then the default value is used instead.
Array/List:
Nested object
result
Choose either SUCCESS, ERROR, or FAILURE for when the message is appended to the comment that is added to the pull request.
Values:
PENDING
SUCCESS
ERROR
FAILURE
message
The message that is appended to a comment when a build finishes with the desired build status. If no status updates should be made when a build finishes with the indicated build status, use "--none--" to alert the trigger.
Type:String
includedRegions
Each inclusion uses regular expression pattern matching, and must be separated by a new line. An empty list implies that everything is included.
        myapp/src/main/web/.*\.html
        myapp/src/main/web/.*\.jpeg
        myapp/src/main/web/.*\.gif
    

The example above illustrates that a build will only occur, if html/jpeg/gif files have been committed to the GitHub repository. Exclusions take precedence over inclusions, if there is an overlap between included and excluded regions.
More information on regular expressions can be found here.
Type:String
excludedRegions
Each exclusion uses regular expression pattern matching, and must be separated by a new line.
        myapp/src/main/web/.*\.html
        myapp/src/main/web/.*\.jpeg
        myapp/src/main/web/.*\.gif
    

The example above illustrates that if only html/jpeg/gif files have been committed to the GitHub repository a build will not occur.
More information on regular expressions can be found here.
Type:String
githubPush
When Jenkins receives a GitHub push hook, GitHub Plugin checks to see whether the hook came from a GitHub repository which matches the Git repository defined in SCM/Git section of this job. If they match and this option is enabled, GitHub Plugin triggers a one-time polling on GITScm. When GITScm polls GitHub, it finds that there is a change and initiates a build. The last sentence describes the behavior of Git plugin, thus the polling and initiating the build is not a part of GitHub plugin.
gitlab
Options for triggering Jenkins jobs based on GitLab events.
acceptMergeRequestOnSuccess (optional)
Type:boolean
addCiMessage (optional)
Type:boolean
addNoteOnMergeRequest (optional)
Type:boolean
addVoteOnMergeRequest (optional)
Type:boolean
branchFilterName (optional)
Type:String
branchFilterType (optional)
Values:
All
NameBasedFilter
RegexBasedFilter
cancelPendingBuildsOnUpdate (optional)
If enabled, then pending builds will be canceled when a merge request is updated in the GitLab repository.
Type:boolean
ciSkip (optional)
If enabled, then the build will be skipped when a GitLab comment includes the text ci-skip.
Type:boolean
excludeBranchesSpec (optional)
Type:String
includeBranchesSpec (optional)
Type:String
labelsThatForcesBuildIfAdded (optional)
Type:String
mergeRequestLabelFilterConfig (optional)
Nested object
exclude (optional)
Type:String
include (optional)
Type:String
noteRegex (optional)
Type:String
pendingBuildName (optional)
Type:String
secretToken (optional)
Type:String
setBuildDescription (optional)
If enabled, then the build Jenkins description will be updated with the build cause.
Type:boolean
skipWorkInProgressMergeRequest (optional)
If enabled, then the build will be skipped when a GitLab merge request is a work in progress.
Type:boolean
sourceBranchRegex (optional)
Type:String
targetBranchRegex (optional)
Type:String
triggerOnAcceptedMergeRequest (optional)
If enabled, then the build will be triggered when a merge request is accepted in the GitLab repository.
Type:boolean
triggerOnApprovedMergeRequest (optional)
If enabled, then the build will be triggered when a merge request is approved on the GitLab Enterprise Edition repository.
Type:boolean
triggerOnClosedMergeRequest (optional)
If enabled, then the build will be triggered when merge requests are closed in the GitLab repository.
Type:boolean
triggerOnMergeRequest (optional)
If enabled, then the build will be triggered when a merge request is created in the GitLab repository.
Type:boolean
triggerOnNoteRequest (optional)
If enabled, then the build will be triggered when a comment is added to the GitLab repository.
Type:boolean
triggerOnPipelineEvent (optional)
Type:boolean
triggerOnPush (optional)
If enabled, then the build will be triggered when new commits are pushed to the GitLab repository.
Type:boolean
triggerOnlyIfNewCommitsPushed (optional)
If enabled, then the build will be triggered when new commits are pushed to the GitLab repository.
Type:boolean
triggerOpenMergeRequestOnPush (optional)
If enabled, then the build will be triggered when changes are made to open merge requests in the GitLab repository.
Values:
never
source
both
triggerToBranchDeleteRequest (optional)
If enabled, then the build will be triggered when a branch is deleted from the GitLab repository.
Type:boolean
issueCommentTrigger
commentPattern
Type:String
labelAddedTrigger
labelTriggerPattern
Type:String
$class: 'PeriodicFolderTrigger'

Some kinds of folders are reindexed automatically and immediately upon receipt of an external event. For example, a multi-branch project will recheck its SCM repository for new or removed or modified branches when it receives an SCM change notification. (Push notification may be configured as per the SCM plugin used for each respective branch source.) Such notifications can occasionally be unreliable, however, or Jenkins might not even be running to receive them. In some cases no immediate notification is even possible, for example because Jenkins is behind a firewall and can only poll an external system.

This trigger allows for a periodic fallback, but when necessary. If no indexing has been performed in the specified interval, then an indexing will be scheduled. For example, in the case of a multi-branch project, if the source control system is not configured for push notification, set a short interval (most people will pick between 15 minutes and 1 hour). If the source control system is configured for push notification, set an interval that corresponds to the maximum acceptable delay in the event of a lost push notification as the last commit of the day. (Subsequent commits should trigger indexing anyway and result in the commit being picked up, so most people will pick between 4 hours and 1 day.)

interval

The maximum amount of time since the last indexing that is allowed to elapse before an indexing is triggered. For example: interval('5m') // or '2h', '7d', '5000ms', '60s'

Type:String
$class: 'PromotionTrigger'
jobName
Type:String
process
Type:String
pullRequestReview
reviewStates (optional)
Array/List:
Type:String
upstream

Set up a trigger so that when some other projects finish building, a new build is scheduled for this project. This is convenient for running an extensive test after a build is complete, for example.

This configuration complements the "Build other projects" section in the "Post-build Actions" of an upstream project, but is preferable when you want to configure the downstream project.

upstreamProjects
Type:String
threshold (optional)
Type:String
pollSCM
Configure Jenkins to poll changes in SCM.

Note that this is going to be an expensive operation for CVS, as every polling requires Jenkins to scan the entire workspace and verify it with the server. Consider setting up a "push" trigger to avoid this overhead, as described in this document

scmpoll_spec
Type:String
ignorePostCommitHooks (optional)
Ignore changes notified by SCM post-commit hooks.

This can be useful if you want to prevent some long-running jobs (e.g. reports) starting because of every commit, but still want to run them periodic if SCM changes have occurred.

Note that this option needs to be supported by the SCM plugin, too! The subversion-plugin supports this since version 1.44.

Type:boolean
cron
Provides a cron -like feature to periodically execute this project.

This feature is primarily for using Jenkins as a cron replacement, and it is not ideal for continuously building software projects . When people first start continuous integration, they are often so used to the idea of regularly scheduled builds like nightly/weekly that they use this feature. However, the point of continuous integration is to start a build as soon as a change is made, to provide a quick feedback to the change. To do that you need to hook up SCM change notification to Jenkins .

So, before using this feature, stop and ask yourself if this is really what you want.

spec
Type:String
snapshotDependencies
Trigger the build of this pipeline when a Maven SNAPSHOT dependency is built by this Jenkins instance. Jenkins discovers all the dependencies of the Maven builds of this pipeline invoked in a withMaven(){...} wrapping step and will trigger the build if one of these dependencies has been built (typically a SNAPSHOT version). This is convenient for automatically performing continuous integration. Jenkins will check the snapshot dependencies from the <dependency> element in the POM.
preserveStashes
Preserve the stashes from the most recent completed builds of this project. This allows a restarted Declarative Pipeline to reuse a stash from the build it was restarted from.
buildCount (optional)
Type:int
$class: 'RebuildSettings'
autoRebuild
Option enables rebuild without confirmation of parameters.
It also allows to rebuild the job without manual upload of file parameters.
Type:boolean
rebuildDisabled
Type:boolean
throttleJobProperty

Note that the Throttle Concurrent Builds configuration here does not work for Pipeline jobs.

For that, use the throttle step.

maxConcurrentPerNode

The maximum number of concurrent builds of this project (or category) to be allowed to run per node.

Type:int
maxConcurrentTotal

The maximum number of concurrent builds of this project (or category) to be allowed to run at any one time, across all nodes.

Type:int
categories

Categories can be used to throttle multiple projects.

Categories can be optionally configured with pairs of throttled Jenkins node labels.
Pairs can make each maximum applicable to nodes with matching labels only.
That is achieved by adding such Maximum Per Labeled Node pair(s) to any category.
Category's Maximum Concurrent Builds Per Node is superseded by matching-pair's maximum.

Array/List:
Type:String
throttleEnabled
Type:boolean
throttleOption
Type:String
limitOneJobWithMatchingParams

If this box is checked, only one instance of the job with matching parameter values will be allowed to run at a given time. Other instances of this job with different parameter values will be allowed to run concurrently.

Optionally, provide a comma- or whitespace-separated list of parameters to use when comparing jobs. If blank, all parameters must match for a job to be limited to one running instance.

Type:boolean
paramsToUseForLimit
Type:String
matrixOptions
Nested object
throttleMatrixBuilds
Type:boolean
throttleMatrixConfigurations
Type:boolean
rateLimitBuilds
throttle
Enforces a minimum time between builds based on the desired maximum rate.
Note: this does not enforce an "average" rate, it only looks at the time since last build.
Nested object
count
Type:int
durationName
Type:String
userBoost
Type:boolean
publishChecks: Publish customized checks to SCM platforms
actions (optional)
Array/List:
Nested object
label
The label to be displayed on the checks report for this action.
Type:String
identifier
The unique identifier for the action. Since for SCM platforms like GitHub, this is the only field that would be sent back to your Jenkins instance when an action is requested, so you may need to use this field to have more information besides the basic type of the action.
Type:String
description (optional)
Detailed description of the action's purpose, functionality, and so on.
Type:String
annotations (optional)
Array/List:
Nested object
path
Path to the file to be annotated, started from the project root directory.
Type:String
startLine
Start line of code to be annotated.
Type:int
endLine
End line of code to be annotated.
Type:int
message
A digest message of the annotation.
Type:String
annotationLevel (optional)
Severity level of the annotation, can be one of can be "NOTICE", "WARNING", or "FAILURE"; by default, "WARNING" will be used.
Values:
NONE
NOTICE
WARNING
FAILURE
endColumn (optional)
End column of code to be annotated.
Type:int
rawDetails (optional)
Raw details of the annotation.
Type:String
startColumn (optional)
Start column of code to be annotated.
Type:int
title (optional)
Title of the annotation.
Type:String
conclusion (optional)
The conclusion of the check, can be "ACTION_REQUIRED", "SKIPPED", "CANCELED", "TIME_OUT", "FAILURE", "NEUTRAL", "SUCCESS" or "NONE". By default, "SUCCESS" will be used. When providing the conclusion other than "NONE", please make sure the status is "COMPLETED".
Values:
NONE
ACTION_REQUIRED
SKIPPED
CANCELED
TIME_OUT
FAILURE
NEUTRAL
SUCCESS
detailsURL (optional)
The URL of the site where full details can be found. When providing this parameter, make sure it is http or https scheme.
Type:String
name (optional)
Name or identifier of the check.
Type:String
status (optional)
The status of the check, can be "QUEUED", "IN_PROGRESS", or "COMPLETED". By default, "COMPLETED" will be used.
Values:
NONE
QUEUED
IN_PROGRESS
COMPLETED
summary (optional)
The summary of the check run. This field supports Markdown.
Type:String
text (optional)
The details of the check. This parameter supports Markdown.
Type:String
title (optional)
The title of the check run.
Type:String
publishIssues: Publish issues created by a static analysis scan
issues
Array/List:
org.kohsuke.stapler.NoStaplerConstructorException: There's no @DataBoundConstructor on any constructor of class io.jenkins.plugins.analysis.core.steps.AnnotatedReport
failOnError (optional)
If there are errors while scanning the console log or files for issues (e.g., file pattern matches no files, source files could not be copied, etc.) then the warning plugin will show these errors in a separate view but does not alter the build state. If you would rather like to fail the step on such errors, please tick this checkbox.
Type:boolean
failedNewAll (optional)
Type:int
failedNewHigh (optional)
Type:int
failedNewLow (optional)
Type:int
failedNewNormal (optional)
Type:int
failedTotalAll (optional)
Type:int
failedTotalHigh (optional)
Type:int
failedTotalLow (optional)
Type:int
failedTotalNormal (optional)
Type:int
healthy (optional)
The healthy threshold defines the limit of warnings for a healthy result: A build is considered as 100% healthy when the number of issues is less than the specified threshold. Values less or equal zero are ignored. So if you want to have a healthy build (i.e. 100%) only for zero warnings, then set this field to 1.
Type:int
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression \p{Alnum}[\p{Alnum}-_]*). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
ignoreFailedBuilds (optional)
This option determines if failed builds should be selected as baseline or not. It is enabled by default, since analysis results might be inaccurate if the build failed. If unchecked, every build that contains a static analysis result is considered, even if the build failed.
Type:boolean
ignoreQualityGate (optional)

If this option is set, only those issues are marked as new, that have been introduced in the current build. Previously new issues in older builds will be converted to outstanding issues. I.e. if someone starts a new build manually (without source code changes), then no new issues will be in the job anymore.

By default, this option is disabled: then a build is selected as reference that passed all quality gates. As soon as a build fails a quality gate, the reference will be frozen until all new issues will be resolved again. That means, that new issues will be aggregated from build to build until the original reason for the failure and all those additional new issues have been resolved. This helps much more to keep your project clean: as soon as there are issues, Jenkins will mark all builds as unstable until the issues have been resolved.

Type:boolean
minimumSeverity (optional)
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
publishAllIssues (optional)
Type:boolean
qualityGates (optional)
Array/List:
Nested object
threshold
The threshold defines the minimum number of warnings that will fail a build. Values less or equal zero are ignored. So if you want to fail a build that has one warning, set this field to 1.
Type:int
type
In order to simplify the user interface you can select the property that will be compared with the specified threshold. Basically, three different properties are available:
Total
Selects the total number of issues in the current build.
New
Selects the total number of new issues in the current build with respect to the reference build. New issues will be calculated by a sophisticated algorithm, that tries to track issues from build to build, even if the source code has been modified. Note that this algorithm sometimes detects outstanding warnings as new, e.g., if a source file has been refactored heavily.
Delta
Selects the difference of the total number of issues of the current build subtracted by the total number of issues in the reference build. This is a simple subtraction, so if you have a build that adds a new warning and removes a completely different warning, then the result will be zero.
Additionally, you can select to choose all issues, or issues of a given severity only (error, high, normal or low).
Values:
TOTAL
TOTAL_ERROR
TOTAL_HIGH
TOTAL_NORMAL
TOTAL_LOW
NEW
NEW_ERROR
NEW_HIGH
NEW_NORMAL
NEW_LOW
DELTA
DELTA_ERROR
DELTA_HIGH
DELTA_NORMAL
DELTA_LOW
unstable
Type:boolean
quiet (optional)
Type:boolean
referenceBuildId (optional)
Type:String
referenceJobName (optional)
Type:String
skipPublishingChecks (optional)
If this option is unchecked, then the plugin automatically publishes the issues to corresponding SCM hosting platforms. For example, if you are using this feature for a GitHub organization project, the warnings will be published to GitHub through the Checks API. If this operation slows down your build or you don't want to publish the warnings to SCM platforms, you can use this option to deactivate this feature.
Type:boolean
sourceCodeEncoding (optional)
In order to correctly show all your affected source code files in the detail views, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
trendChartType (optional)
If there is more than one static analysis result available then an aggregation trend chart will be shown on the project page that shows the analysis results in a single trend chart. You can choose the position of this aggregation trend:
AGGREGATION_TOOLS
The aggregation trend is shown before all other analysis tool trend charts.
TOOLS_AGGREGATION
The aggregation trend is shown after all other analysis tool trend charts.
TOOLS_ONLY
The aggregation trend is not shown, only the analysis tool trend charts are shown.
AGGREGATION_ONLY
The aggregation trend is only shown, no other analysis tool trend charts are shown.
NONE
Neither the aggregation trend nor analysis tool trend charts are shown.
Values:
AGGREGATION_TOOLS
TOOLS_AGGREGATION
TOOLS_ONLY
AGGREGATION_ONLY
NONE
unhealthy (optional)
The unhealthy threshold defines the limit of warnings for an unhealthy result: A build is considered as unhealthy (i.e. 0% health) when the number of issues is greater than the specified threshold. Values less or equal zero are ignored. So if you want to have a build health of 0% starting with 10 issues, then set this field to 9.
Type:int
unstableNewAll (optional)
Type:int
unstableNewHigh (optional)
Type:int
unstableNewLow (optional)
Type:int
unstableNewNormal (optional)
Type:int
unstableTotalAll (optional)
Type:int
unstableTotalHigh (optional)
Type:int
unstableTotalLow (optional)
Type:int
unstableTotalNormal (optional)
Type:int
pwd: Determine current directory
Returns the current directory path as a string.
tmp (optional)
If selected, return a temporary directory associated with the current directory path rather than the directory path itself. The return value is different for each current directory. No two directories share the same temporary directory. This is an appropriate place to put temporary files which should not clutter a source checkout; local repositories or caches; etc. Defaults to false.
Type:boolean
pwsh: PowerShell Core Script
script
Executes a PowerShell script. Multiple lines allowed. This plugin supports PowerShell Core 6+.
Note: be aware of the differences between Windows PowerShell and PowerShell Core, check which one is available on your agents.
Type:String
encoding (optional)
Encoding of process output. In the case of returnStdout, applies to the return value of this step; otherwise, or always for standard error, controls how text is copied to the build log. If unspecified, uses the system default encoding of the node on which the step is run. If there is any expectation that process output might include non-ASCII characters, it is best to specify the encoding explicitly. For example, if you have specific knowledge that a given process is going to be producing UTF-8 yet will be running on a node with a different system encoding (typically Windows, since every Linux distribution has defaulted to UTF-8 for a long time), you can ensure correct output by specifying: encoding: 'UTF-8'
Type:String
label (optional)
Label to be displayed in the pipeline step view and blue ocean details for the step instead of the step type. So the view is more meaningful and domain specific instead of technical.
Type:String
returnStatus (optional)
Normally, a script which exits with a nonzero status code will cause the step to fail with an exception. If this option is checked, the return value of the step will instead be the status code. You may then compare it to zero, for example.
Type:boolean
returnStdout (optional)
If checked, standard output from the task is returned as the step value as a String, rather than being printed to the build log. (Standard error, if any, will still be printed to the log.) You will often want to call .trim() on the result to strip off a trailing newline.
Type:boolean
readFile: Read file from workspace
Reads a file from a relative path (with root in current directory, usually workspace) and returns its content as a plain string.
file
Relative (/-separated) path to file within a workspace to read.
Type:String
encoding (optional)
The encoding to use when reading the file. If left blank, the platform default encoding will be used. Binary files can be read into a Base64-encoded string by specifying "Base64" as the encoding.
Type:String
readTrusted: Read trusted file from SCM
From a multibranch Pipeline project, reads a file from the associated SCM and returns its contents. Unlike the readFile step, no workspace is required. If the associated branch is not trusted, yet the file has been modified from its trusted version, an error is thrown. Thus this step is useful for loading scripts or other files which might otherwise be used to run malicious commands. Like checkout scm, as a convenience it may also be used from a standalone project configured with Pipeline from SCM, in which case there is no security aspect.
path
Relative (slash-separated) path to the file from the SCM root. Thus readTrusted 'subdir/file' is similar to node {checkout scm; readFile 'subdir/file'}.
Type:String
recordIssues: Record compiler warnings and static analysis results
aggregatingResults (optional)
By default, each static analysis result will be recorded as a separate result that is presented as an individual Jenkins Action with separate UI and dashboard. If you rather prefer aggregation of the results into a single result (i.e., single Jenkins Action), then activate this check box. You still can see the distribution of issues grouped by static analysis tool in the UI.
Type:boolean
blameDisabled (optional)
If this option is unchecked, then the plugin automatically shows what revision and author (name and email) last modified the lines of the affected files that contain issues. If this operation slows down your build or you don't want to publish sensitive user data, you can use this option to deactivate this feature.
Type:boolean
enabledForFailure (optional)
By default, static analysis results are only recorded for stable or unstable builds, but not for failed builds: analysis results might be inaccurate if the build failed. If recording should be enabled for failed builds as well then activate this check box.
Type:boolean
failOnError (optional)
If there are errors while scanning the console log or files for issues (e.g., file pattern matches no files, source files could not be copied, etc.) then the warning plugin will show these errors in a separate view but does not alter the build state. If you would rather like to fail the step on such errors, please tick this checkbox.
Type:boolean
failedNewAll (optional)
Type:int
failedNewHigh (optional)
Type:int
failedNewLow (optional)
Type:int
failedNewNormal (optional)
Type:int
failedTotalAll (optional)
Type:int
failedTotalHigh (optional)
Type:int
failedTotalLow (optional)
Type:int
failedTotalNormal (optional)
Type:int
filters (optional)
The created report of issues can be filtered afterwards. You can specify an arbitrary number of include or exclude filters. Currently, there is support for filtering issues by module name, package or namespace name, file name, category or type. Include filters will be combined with or, exclude filters with and. If no filter is defined, then all issues will be published. Filters with empty regular expression will be ignored.
Array/List:
Nested choice of objects
excludeCategory
pattern
Type:String
excludeFile
pattern
Type:String
excludeMessage
pattern
Type:String
excludeModule
pattern
Type:String
excludePackage
pattern
Type:String
excludeType
pattern
Type:String
includeCategory
pattern
Type:String
includeFile
pattern
Type:String
includeMessage
pattern
Type:String
includeModule
pattern
Type:String
includePackage
pattern
Type:String
includeType
pattern
Type:String
forensicsDisabled (optional)
Type:boolean
healthy (optional)
The healthy threshold defines the limit of warnings for a healthy result: A build is considered as 100% healthy when the number of issues is less than the specified threshold. Values less or equal zero are ignored. So if you want to have a healthy build (i.e. 100%) only for zero warnings, then set this field to 1.
Type:int
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression \p{Alnum}[\p{Alnum}-_]*). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
ignoreFailedBuilds (optional)
This option determines if failed builds should be selected as baseline or not. It is enabled by default, since analysis results might be inaccurate if the build failed. If unchecked, every build that contains a static analysis result is considered, even if the build failed.
Type:boolean
ignoreQualityGate (optional)

If this option is set, only those issues are marked as new, that have been introduced in the current build. Previously new issues in older builds will be converted to outstanding issues. I.e. if someone starts a new build manually (without source code changes), then no new issues will be in the job anymore.

By default, this option is disabled: then a build is selected as reference that passed all quality gates. As soon as a build fails a quality gate, the reference will be frozen until all new issues will be resolved again. That means, that new issues will be aggregated from build to build until the original reason for the failure and all those additional new issues have been resolved. This helps much more to keep your project clean: as soon as there are issues, Jenkins will mark all builds as unstable until the issues have been resolved.

Type:boolean
minimumSeverity (optional)
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
publishAllIssues (optional)
Type:boolean
qualityGates (optional)
Array/List:
Nested object
threshold
The threshold defines the minimum number of warnings that will fail a build. Values less or equal zero are ignored. So if you want to fail a build that has one warning, set this field to 1.
Type:int
type
In order to simplify the user interface you can select the property that will be compared with the specified threshold. Basically, three different properties are available:
Total
Selects the total number of issues in the current build.
New
Selects the total number of new issues in the current build with respect to the reference build. New issues will be calculated by a sophisticated algorithm, that tries to track issues from build to build, even if the source code has been modified. Note that this algorithm sometimes detects outstanding warnings as new, e.g., if a source file has been refactored heavily.
Delta
Selects the difference of the total number of issues of the current build subtracted by the total number of issues in the reference build. This is a simple subtraction, so if you have a build that adds a new warning and removes a completely different warning, then the result will be zero.
Additionally, you can select to choose all issues, or issues of a given severity only (error, high, normal or low).
Values:
TOTAL
TOTAL_ERROR
TOTAL_HIGH
TOTAL_NORMAL
TOTAL_LOW
NEW
NEW_ERROR
NEW_HIGH
NEW_NORMAL
NEW_LOW
DELTA
DELTA_ERROR
DELTA_HIGH
DELTA_NORMAL
DELTA_LOW
unstable
Type:boolean
quiet (optional)
Type:boolean
referenceBuildId (optional)
Type:String
referenceJobName (optional)
Type:String
scm (optional)
Type:String
skipBlames (optional)
Type:boolean
skipPostProcessing (optional)
If this option is unchecked, then the plugin automatically resolves absolute paths, fingerprints, package and module names from the source files in the workspace. If this operation slows down your build, you can use this option to deactivate this feature.
Type:boolean
skipPublishingChecks (optional)
If this option is unchecked, then the plugin automatically publishes the issues to corresponding SCM hosting platforms. For example, if you are using this feature for a GitHub organization project, the warnings will be published to GitHub through the Checks API. If this operation slows down your build or you don't want to publish the warnings to SCM platforms, you can use this option to deactivate this feature.
Type:boolean
sourceCodeEncoding (optional)
In order to correctly show all your affected source code files in the detail views, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
sourceDirectories (optional)
Some plugins copy source code files to Jenkins' build folder so that these files can be rendered in the user interface together with build results (coverage, warnings, etc.). If these files are not part of the workspace of a build then Jenkins will not show them by default: otherwise sensitive files could be shown by accident. You can provide a list of additional source code directories that are allowed to be shown in Jenkins user interface here. Note, that such a directory must be an absolute path on the agent that executes the build.
Array/List:
Nested object
path
Select the path to your source code files. This plugin copies source code files to Jenkins' build folder so that these files can be rendered in the user interface together with the plugin results. If these files are referenced with relative paths then they cannot be found by the plugin. In these cases you need to specify one or more relative paths within the workspace where the plugin can locate them. Alternatively, you can also specify absolute paths if the source code files are stored outside the workspace (in a directory on the agent). All absolute paths must be additionally approved by an administrator in Jenkins' global configuration page.
Type:String
sourceDirectory (optional)
Type:String
tool (optional)
For each static analysis tool a dedicated parser or scanner will be used to read report files or produce issues in any other way. If your tool is not yet supported you can define a new Groovy based parser in Jenkins system configuration. You can reference this new parser afterwards when you select the tool 'Groovy Parser'. Additionally, you provide a new parser within a new small plug-in. If the parser is useful for other teams as well please share it and provide pull requests for the Warnings Next Generation Plug-in and the Analysis Parsers Library.
Nested choice of objects
acuCobol
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ajc
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
androidLintParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ansibleLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
aquaScanner
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
armCc
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
axivionSuite
basedir (optional)
Type:String
credentialsId (optional)
Type:String
id (optional)
Type:String
ignoreSuppressedOrJustified (optional)
Type:boolean
name (optional)
Type:String
namedFilter (optional)
Type:String
projectUrl (optional)
Type:String
bluepearl
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
brakeman
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
buckminster
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
cadence
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
cargo
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ccm
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
checkStyle
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
clair
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
clang
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
clangAnalyzer
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
clangTidy
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
cmake
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
codeAnalysis
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
codeChecker
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
codeGeneratorParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
codeNarc
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
coolflux
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
cpd
highThreshold (optional)
Type:int
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
normalThreshold (optional)
Type:int
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
cppCheck
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
cppLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
CrossCoreEmbeddedStudioParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
cssLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
dscanner
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
dart
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
detekt
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
diabC
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
docFx
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
dockerLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
doxygen
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
drMemory
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
dupFinder
highThreshold (optional)
Type:int
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
normalThreshold (optional)
Type:int
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
eclipse
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
embeddedEngineerParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
erlc
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
errorProne
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
esLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
findBugs
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
useRankAsPriority (optional)
Type:boolean
flake8
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
flawfinder
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
flexSdk
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
fxcop
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
gcc3
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
gcc
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
gendarme
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ghsMulti
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
gnat
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
gnuFortran
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
goLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
goVet
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
groovyScript
parserId
Type:String
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
grype
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
hadoLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
iar
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
iarCstat
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ibLinter
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ideaInspection
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
infer
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
intel
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
invalids
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
junitParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
java
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
javaDoc
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
jcReport
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
jsHint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
jsLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
klocWork
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
kotlin
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ktLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
mavenConsole
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
modelsim
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
metrowerksCodeWarrior
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
msBuild
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
myPy
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
nagFortran
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
oelintAdv
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
otDockerLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
taskScanner
excludePattern (optional)
Type:String
highTags (optional)
Type:String
id (optional)
Type:String
ignoreCase (optional)
Type:boolean
includePattern (optional)
You can define multiple filesets using comma as a separator, e.g. '**/*.c, **/*.h'. Basedir of the fileset is the workspace root.
Type:String
isRegularExpression (optional)
Note that the regular expression must contain two capturing groups: the first one is interpreted as tag name, the second one as message. An example of such a regular expression would be ^.*(TODO(?:[0-9]*))(.*)$.
Type:boolean
lowTags (optional)
Type:String
name (optional)
Type:String
normalTags (optional)
Type:String
owaspDependencyCheck
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
PVSStudio
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
pcLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
pep8
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
perforce
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
perlCritic
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
php
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
phpCodeSniffer
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
phpStan
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
pit
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
pmdParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
polyspaceParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
prefast
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
protoLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
puppetLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
pyDocStyle
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
pyLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
qacSourceCodeAnalyser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
qtTranslation
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
analysisParser
analysisModelId
Type:String
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
resharperInspectCode
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
revApi
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
rfLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
robocopy
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ruboCop
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
sarif
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
scala
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
simian
highThreshold (optional)
Type:int
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
normalThreshold (optional)
Type:int
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
simulinkCheckParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
sonarQube
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
sphinxBuild
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
spotBugs
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
useRankAsPriority (optional)
Type:boolean
styleCop
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
styleLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
sunC
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
swiftLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
tagList
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
taskingVx
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
tiCss
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
tnsdl
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
trivy
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
tsLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
veracodePipelineScanner
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
issues
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
xlc
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
xmlLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
yamlLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
yuiCompressor
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
zptLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
toolProxies (optional)
For each static analysis tool a dedicated parser or scanner will be used to read report files or produce issues in any other way. If your tool is not yet supported you can define a new Groovy based parser in Jenkins system configuration. You can reference this new parser afterwards when you select the tool 'Groovy Parser'. Additionally, you provide a new parser within a new small plug-in. If the parser is useful for other teams as well please share it and provide pull requests for the Warnings Next Generation Plug-in and the Analysis Parsers Library.
Array/List:
Nested object
tool

For each static analysis tool a dedicated parser or scanner will be used to read report files or produce issues in any other way. If your tool is not yet supported you can define a new Groovy based parser in Jenkins system configuration. You can reference this new parser afterwards when you select the tool 'Groovy Parser'. Additionally, you provide a new parser within a new small plug-in. If the parser is useful for other teams as well please share it and provide pull requests for the Warnings Next Generation Plug-in and the Analysis Parsers Library.

Nested choice of objects
acuCobol
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ajc
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
androidLintParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ansibleLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
aquaScanner
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
armCc
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
axivionSuite
basedir (optional)
Type:String
credentialsId (optional)
Type:String
id (optional)
Type:String
ignoreSuppressedOrJustified (optional)
Type:boolean
name (optional)
Type:String
namedFilter (optional)
Type:String
projectUrl (optional)
Type:String
bluepearl
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
brakeman
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
buckminster
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
cadence
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
cargo
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ccm
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
checkStyle
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
clair
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
clang
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
clangAnalyzer
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
clangTidy
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
cmake
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
codeAnalysis
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
codeChecker
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
codeGeneratorParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
codeNarc
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
coolflux
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
cpd
highThreshold (optional)
Type:int
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
normalThreshold (optional)
Type:int
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
cppCheck
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
cppLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
CrossCoreEmbeddedStudioParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
cssLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
dscanner
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
dart
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
detekt
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
diabC
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
docFx
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
dockerLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
doxygen
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
drMemory
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
dupFinder
highThreshold (optional)
Type:int
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
normalThreshold (optional)
Type:int
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
eclipse
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
embeddedEngineerParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
erlc
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
errorProne
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
esLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
findBugs
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
useRankAsPriority (optional)
Type:boolean
flake8
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
flawfinder
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
flexSdk
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
fxcop
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
gcc3
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
gcc
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
gendarme
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ghsMulti
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
gnat
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
gnuFortran
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
goLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
goVet
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
groovyScript
parserId
Type:String
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
grype
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
hadoLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
iar
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
iarCstat
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ibLinter
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ideaInspection
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
infer
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
intel
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
invalids
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
junitParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
java
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
javaDoc
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
jcReport
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
jsHint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
jsLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
klocWork
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
kotlin
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ktLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
mavenConsole
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
modelsim
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
metrowerksCodeWarrior
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
msBuild
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
myPy
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
nagFortran
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
oelintAdv
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
otDockerLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
taskScanner
excludePattern (optional)
Type:String
highTags (optional)
Type:String
id (optional)
Type:String
ignoreCase (optional)
Type:boolean
includePattern (optional)
You can define multiple filesets using comma as a separator, e.g. '**/*.c, **/*.h'. Basedir of the fileset is the workspace root.
Type:String
isRegularExpression (optional)
Note that the regular expression must contain two capturing groups: the first one is interpreted as tag name, the second one as message. An example of such a regular expression would be ^.*(TODO(?:[0-9]*))(.*)$.
Type:boolean
lowTags (optional)
Type:String
name (optional)
Type:String
normalTags (optional)
Type:String
owaspDependencyCheck
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
PVSStudio
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
pcLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
pep8
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
perforce
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
perlCritic
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
php
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
phpCodeSniffer
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
phpStan
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
pit
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
pmdParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
polyspaceParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
prefast
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
protoLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
puppetLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
pyDocStyle
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
pyLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
qacSourceCodeAnalyser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
qtTranslation
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
analysisParser
analysisModelId
Type:String
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
resharperInspectCode
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
revApi
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
rfLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
robocopy
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ruboCop
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
sarif
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
scala
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
simian
highThreshold (optional)
Type:int
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
normalThreshold (optional)
Type:int
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
simulinkCheckParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
sonarQube
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
sphinxBuild
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
spotBugs
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
useRankAsPriority (optional)
Type:boolean
styleCop
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
styleLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
sunC
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
swiftLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
tagList
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
taskingVx
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
tiCss
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
tnsdl
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
trivy
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
tsLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
veracodePipelineScanner
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
issues
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
xlc
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
xmlLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
yamlLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
yuiCompressor
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
zptLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
tools (optional)
Array/List:
Nested choice of objects
acuCobol
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ajc
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
androidLintParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ansibleLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
aquaScanner
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
armCc
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
axivionSuite
basedir (optional)
Type:String
credentialsId (optional)
Type:String
id (optional)
Type:String
ignoreSuppressedOrJustified (optional)
Type:boolean
name (optional)
Type:String
namedFilter (optional)
Type:String
projectUrl (optional)
Type:String
bluepearl
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
brakeman
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
buckminster
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
cadence
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
cargo
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ccm
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
checkStyle
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
clair
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
clang
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
clangAnalyzer
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
clangTidy
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
cmake
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
codeAnalysis
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
codeChecker
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
codeGeneratorParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
codeNarc
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
coolflux
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
cpd
highThreshold (optional)
Type:int
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
normalThreshold (optional)
Type:int
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
cppCheck
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
cppLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
CrossCoreEmbeddedStudioParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
cssLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
dscanner
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
dart
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
detekt
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
diabC
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
docFx
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
dockerLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
doxygen
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
drMemory
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
dupFinder
highThreshold (optional)
Type:int
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
normalThreshold (optional)
Type:int
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
eclipse
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
embeddedEngineerParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
erlc
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
errorProne
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
esLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
findBugs
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
useRankAsPriority (optional)
Type:boolean
flake8
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
flawfinder
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
flexSdk
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
fxcop
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
gcc3
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
gcc
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
gendarme
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ghsMulti
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
gnat
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
gnuFortran
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
goLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
goVet
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
groovyScript
parserId
Type:String
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
grype
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
hadoLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
iar
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
iarCstat
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ibLinter
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ideaInspection
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
infer
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
intel
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
invalids
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
junitParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
java
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
javaDoc
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
jcReport
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
jsHint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
jsLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
klocWork
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
kotlin
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ktLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
mavenConsole
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
modelsim
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
metrowerksCodeWarrior
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
msBuild
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
myPy
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
nagFortran
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
oelintAdv
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
otDockerLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
taskScanner
excludePattern (optional)
Type:String
highTags (optional)
Type:String
id (optional)
Type:String
ignoreCase (optional)
Type:boolean
includePattern (optional)
You can define multiple filesets using comma as a separator, e.g. '**/*.c, **/*.h'. Basedir of the fileset is the workspace root.
Type:String
isRegularExpression (optional)
Note that the regular expression must contain two capturing groups: the first one is interpreted as tag name, the second one as message. An example of such a regular expression would be ^.*(TODO(?:[0-9]*))(.*)$.
Type:boolean
lowTags (optional)
Type:String
name (optional)
Type:String
normalTags (optional)
Type:String
owaspDependencyCheck
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
PVSStudio
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
pcLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
pep8
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
perforce
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
perlCritic
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
php
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
phpCodeSniffer
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
phpStan
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
pit
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
pmdParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
polyspaceParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
prefast
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
protoLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
puppetLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
pyDocStyle
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
pyLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
qacSourceCodeAnalyser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
qtTranslation
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
analysisParser
analysisModelId
Type:String
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
resharperInspectCode
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
revApi
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
rfLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
robocopy
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ruboCop
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
sarif
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
scala
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
simian
highThreshold (optional)
Type:int
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
normalThreshold (optional)
Type:int
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
simulinkCheckParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
sonarQube
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
sphinxBuild
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
spotBugs
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
useRankAsPriority (optional)
Type:boolean
styleCop
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
styleLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
sunC
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
swiftLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
tagList
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
taskingVx
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
tiCss
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
tnsdl
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
trivy
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
tsLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
veracodePipelineScanner
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
issues
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
xlc
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
xmlLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
yamlLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
yuiCompressor
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
zptLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
trendChartType (optional)
If there is more than one static analysis result available then an aggregation trend chart will be shown on the project page that shows the analysis results in a single trend chart. You can choose the position of this aggregation trend:
AGGREGATION_TOOLS
The aggregation trend is shown before all other analysis tool trend charts.
TOOLS_AGGREGATION
The aggregation trend is shown after all other analysis tool trend charts.
TOOLS_ONLY
The aggregation trend is not shown, only the analysis tool trend charts are shown.
AGGREGATION_ONLY
The aggregation trend is only shown, no other analysis tool trend charts are shown.
NONE
Neither the aggregation trend nor analysis tool trend charts are shown.
Values:
AGGREGATION_TOOLS
TOOLS_AGGREGATION
TOOLS_ONLY
AGGREGATION_ONLY
NONE
unhealthy (optional)
The unhealthy threshold defines the limit of warnings for an unhealthy result: A build is considered as unhealthy (i.e. 0% health) when the number of issues is greater than the specified threshold. Values less or equal zero are ignored. So if you want to have a build health of 0% starting with 10 issues, then set this field to 9.
Type:int
unstableNewAll (optional)
Type:int
unstableNewHigh (optional)
Type:int
unstableNewLow (optional)
Type:int
unstableNewNormal (optional)
Type:int
unstableTotalAll (optional)
Type:int
unstableTotalHigh (optional)
Type:int
unstableTotalLow (optional)
Type:int
unstableTotalNormal (optional)
Type:int
resolveScm: Resolves an SCM from an SCM Source and a list of candidate target branch names
When you have a multi-branch pipeline that checks out other sibling repositories, you may want to check out the matching branch from that sibling repository (assuming it exists) but fall back to the main branch if there is no matching branch.

This step lets you create a branch in the primary repository and then when you need downstream / upstream changes in the sibling repository you can just create a matching branch and it will be resolved automatically. For example:

// checkout the main source
dir('main'){
    // this will checkout the source repository that is driving the multi-branch pipeline
    checkout scm
}
// now checkout the tests
dir('tests'){
    // this will check if there is a branch with the same name as the current branch in
    // https://example.com/example.git and use that for the checkout, but if there is no
    // branch with the same name it will fall back to the master branch
    checkout resolveScm(source: git('https://example.com/example.git'), targets: [BRANCH_NAME,'master']
}
// rest of pipeline

The return value is the resolved SCM instance (or null if ignoring errors). Where the SCM implementation supports it, the SCM instance will be pinned to the current head revision of the resolved branch. This can be useful if, for example, you want to check out the resolved branch on multiple nodes because all the nodes will get the same revision.

source
The source repository from which to resolve the target branches.
Nested choice of objects
github
repoOwner

Specify the name of the GitHub Organization or GitHub User Account.

Type:String
repository
The repository to scan.
Type:String
repositoryUrl

Specify the HTTPS URL of the GitHub Organization / User Account and repository.

GitHub examples:

  • https://github.com/jenkinsci/github-branch-source-plugin
  • https://github.com/jenkinsci/github-branch-source-plugin.git

GitHub Enterprise examples:

  • https://myccompany.github.com/jenkinsci/github-branch-source-plugin
  • https://myccompany.github.com/jenkinsci/github-branch-source-plugin.git

Type:String
configuredByUrl
Type:boolean
apiUri (optional)
The server to connect to. The list of servers is configured in the Manage Jenkins » Configure System » GitHub Enterprise Servers screen.
Type:String
buildForkPRHead (optional)
Type:boolean
buildForkPRMerge (optional)
Type:boolean
buildOriginBranch (optional)
Type:boolean
buildOriginBranchWithPR (optional)
Type:boolean
buildOriginPRHead (optional)
Type:boolean
buildOriginPRMerge (optional)
Type:boolean
credentialsId (optional)

Credentials used to scan branches and pull requests, check out sources and mark commit statuses.

Note that only "username with password" credentials are supported. Existing credentials of other kinds will be filtered out. This is because Jenkins uses the GitHub API, which does not support other ways of authentication.

If none is given, only the public repositories will be scanned, and commit status will not be set on GitHub.

If your organization contains private repositories, then you need to specify a credential from a user who has access to those repositories. This is done by creating a "username with password" credential where the password is GitHub personal access tokens. The necessary scope is "repo".

Type:String
excludes (optional)
Type:String
id (optional)
Type:String
includes (optional)
Type:String
traits (optional)
The behaviours control what is discovered from the GitHub repository. The behaviours are grouped into a number of categories:
Within repository
These behaviours determine what gets discovered. If you do not configure at least one discovery behaviour then nothing will be found!
General
These behaviours affect the configuration of each discovered branch / pull request.
Array/List:
Nested choice of objects
authorInChangelog
buildStatusNameCustomPart
Customize the pipeline status name used by Jenkins
buildStatusNameCustomPart (optional)
Enter a string to customize the status/context name for status updates published to GitLab. For a branch build the default name would be 'jenkinsci/branch'. With the buildStatusNameCustomPart 'custom' the name would be 'jenkinsci/custom/branch'. This allows to have multiple GitLab-Branch-Sources for the same GitLab-project configured.
Type:String
buildStatusNameOverwrite (optional)
Overwrites the build status name including the jenkinsci default part.
Instead of 'jenkinsci/custom/branch' just 'custom/branch'.
Type:boolean
ignoreTypeInStatusName (optional)
Type:boolean
checkoutOption
extension
checkoutOption
timeout
Specify a timeout (in minutes) for checkout.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
cleanAfterCheckout
extension
cleanAfterCheckout
Clean up the workspace after every checkout by deleting all untracked files and directories, including those which are specified in .gitignore. It also resets all tracked files to their versioned state. This ensures that the workspace is in the same state as if you cloned and checked out in a brand-new empty directory, and ensures that your build is not affected by the files generated by the previous build.
deleteUntrackedNestedRepositories (optional)
Deletes untracked submodules and any other subdirectories which contain .git directories.
Type:boolean
cleanBeforeCheckout
extension
cleanBeforeCheckout
Clean up the workspace before every checkout by deleting all untracked files and directories, including those which are specified in .gitignore. It also resets all tracked files to their versioned state. This ensures that the workspace is in the same state as if you cloned and checked out in a brand-new empty directory, and ensures that your build is not affected by the files generated by the previous build.
deleteUntrackedNestedRepositories (optional)
Deletes untracked submodules and any other subdirectories which contain .git directories.
Type:boolean
cloneOption
extension
cloneOption
shallow
Perform shallow clone, so that git will not download the history of the project, saving time and disk space when you just want to access the latest version of a repository.
Type:boolean
noTags
Deselect this to perform a clone without tags, saving time and disk space when you just want to access what is specified by the refspec.
Type:boolean
reference
Specify a folder containing a repository that will be used by Git as a reference during clone operations.
This option will be ignored if the folder is not available on the controller or agent where the clone is being executed.
Type:String
timeout
Specify a timeout (in minutes) for clone and fetch operations.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
depth (optional)
Set shallow clone depth, so that git will only download recent history of the project, saving time and disk space when you just want to access the latest commits of a repository.
Type:int
honorRefspec (optional)
Perform initial clone using the refspec defined for the repository. This can save time, data transfer and disk space when you only need to access the references specified by the refspec.
Type:boolean
discoverOtherRefs
Discovers other specified refs on the repository.
ref

The pattern under /refs on the remote repository to discover, can contain a wildcard.
Example: test/*/merged

Type:String
nameMapping (optional)

Mapping for how the ref can be named in for example the @Library.
Example: test-@{1}
Where @{1} replaces the first wildcard in the ref when discovered.

By default it will be "namespace_before_wildcard-@{1}". E.g. if ref is "test/*/merged" the default mapping would be "test-@{1}".

Type:String
gitLabForkDiscovery
Discovers merge requests where the origin project is a fork of the target project.
strategyId
Determines how merge requests are discovered:
Merging the merge request with the current target branch revision
Discover each merge request once with the discovered revision corresponding to the result of merging with the current revision of the target branch
The current merge request revision
Discover each merge request once with the discovered revision corresponding to the merge request head revision without merging
Both the current merge request revision and the merge request merged with the current target branch revision
Discover each merge request twice. The first discovered revision corresponds to the result of merging with the current revision of the target branch in each scan. The second parallel discovered revision corresponds to the merge request head revision without merging
Type:int
trust

One of the great powers of merge requests is that anyone with read access to a project can fork it, commit some changes to their fork and then create a merge request against the original project with their changes. There are some files stored in source control that are important. For example, a Jenkinsfile may contain configuration details to sandbox merge requests in order to mitigate against malicious merge requests. In order to protect against a malicious merge request itself modifying the Jenkinsfile to remove the protections, you can define the trust policy for merge requests from forks.

Other plugins can extend the available trust policies. The default policies are:

Nobody
Merge requests from forks will all be treated as untrusted. This means that where Jenkins requires a trusted file (e.g. Jenkinsfile) the contents of that file will be retrieved from the target branch on the origin project and not from the merge request branch on the fork project.
Members
Merge requests from collaborators to the origin project will be treated as trusted, all other merge requests from fork repositories will be treated as untrusted. Note that if credentials used by Jenkins for scanning the project does not have permission to query the list of contributors to the origin project then only the origin account will be treated as trusted - i.e. this will fall back to Nobody.
Trusted Members
Merge requests forks will be treated as trusted if and only if the fork owner has either Developer or Maintainer or Owner Access Level in the origin project. This is the recommended policy.
Everyone
All merge requests from forks will be treated as trusted. NOTE: this option can be dangerous if used on a public project hosted on a GitLab instance.
java.lang.UnsupportedOperationException: do not know how to categorize attributes of type jenkins.scm.api.trait.SCMHeadAuthority<? super io.jenkins.plugins.gitlabbranchsource.GitLabSCMSourceRequest, ? extends jenkins.scm.api.mixin.ChangeRequestSCMHead2, ? extends jenkins.scm.api.SCMRevision>
buildMRForksNotMirror (optional)
Add discovery of merge requests where the origin project is a fork of a certain project, but the target project is not the original forked project. To be used in case one has a GitLab project which is a fork of another project from another team, in order to isolate artefacts and allow an MR flow. This means using MRs inside that fork from branches in the fork back to the fork's default branch. (Implements https://github.com/jenkinsci/gitlab-branch-source-plugin/issues/167)
Type:boolean
gitHubForkDiscovery
Discovers pull requests where the origin repository is a fork of the target repository.
strategyId
Determines how pull requests are discovered:
Merging the pull request with the current target branch revision
Discover each pull request once with the discovered revision corresponding to the result of merging with the current revision of the target branch. Note that pushes to the target branch will result in new pull request builds.
The current pull request revision
Discover each pull request once with the discovered revision corresponding to the pull request head revision without merging.
Both the current pull request revision and the pull request merged with the current target branch revision
Discover each pull request twice. The first discovered revision corresponds to the result of merging with the current revision of the target branch in each scan. The second parallel discovered revision corresponds to the pull request head revision without merging.
Type:int
trust

One of the great powers of pull requests is that anyone with read access to a repository can fork it, commit some changes to their fork and then create a pull request against the original repository with their changes. There are some files stored in source control that are important. For example, a Jenkinsfile may contain configuration details to sandbox pull requests in order to mitigate against malicious pull requests. In order to protect against a malicious pull request itself modifying the Jenkinsfile to remove the protections, you can define the trust policy for pull requests from forks.

Other plugins can extend the available trust policies. The default policies are:

Nobody
Pull requests from forks will all be treated as untrusted. This means that where Jenkins requires a trusted file (e.g. Jenkinsfile) the contents of that file will be retrieved from the target branch on the origin repository and not from the pull request branch on the fork repository.
Collaborators
Pull requests from collaborators to the origin repository will be treated as trusted, all other pull requests from fork repositories will be treated as untrusted. Note that if credentials used by Jenkins for scanning the repository does not have permission to query the list of collaborators to the origin repository then only the origin account will be treated as trusted - i.e. this will fall back to Nobody. NOTE: all collaborators are trusted, even if they are only members of a team with read permission.
Everyone
All pull requests from forks will be treated as trusted. NOTE: this option can be dangerous if used on a public repository hosted on GitHub.
From users with Admin or Write permission
Pull requests forks will be treated as trusted if and only if the fork owner has either Admin or Write permissions on the origin repository. This is the recommended policy. Note that this strategy requires the Review a user's permission level API, as a result on GitHub Enterprise Server versions before 2.12 this is the same as trusting Nobody.
Nested choice of objects
gitHubTrustContributors
gitHubTrustEveryone
gitHubTrustNobody
gitHubTrustPermissions
browser
browser
Nested choice of objects
assembla
repoUrl
Specify the root URL serving this repository (such as https://www.assembla.com/code/PROJECT/git/).
Type:String
bitbucketServer
repoUrl
Specify the Bitbucket Server root URL for this repository (such as https://bitbucket:7990/OWNER/REPO/).
Type:String
bitbucket
repoUrl
Specify the root URL serving this repository (such as https://bitbucket.org/OWNER/REPO/).
Type:String
cgit
repoUrl
Specify the root URL serving this repository (such as https://cgit.example.com:port/group/REPO/).
Type:String
fisheye
repoUrl
Specify the URL of this repository in FishEye (such as https://fisheye.example.com/browse/project/).
Type:String
gitblit
repoUrl
Specify the root URL serving this repository.
Type:String
projectName
Specify the name of the project in GitBlit.
Type:String
gitLab
repoUrl
Specify the root URL serving this repository (such as https://gitlab.com/username/repository/).
Type:String
version (optional)
Specify the major and minor version of GitLab you use (such as 9.1). If you don't specify a version, a modern version of GitLab (>= 8.0) is assumed.
Type:String
gitLabBrowser
Specify the HTTP URL for this project's GitLab page so that links to changes can be automatically generated by Jenkins. The URL needs to include the owner and project. If the GitLab server is https://gitLab.example.com then the URL for bob's skunkworks project might be https://gitLab.example.com/bob/skunkworks.
projectUrl
Specify the HTTP URL for this project's GitLab page. The URL needs to include the owner and project so, for example, if the GitLab server is https://gitLab.example.com then the URL for bob's skunkworks project might be https://gitLab.example.com/bob/skunkworks
Type:String
gitList
repoUrl
Specify the root URL serving this repository (such as https://gitlist.example.com/repo/).
Type:String
gitWeb
repoUrl
Specify the root URL serving this repository (such as https://github.com/jenkinsci/jenkins.git).
Type:String
github
repoUrl
Specify the HTTP URL for this repository's GitHub page (such as https://github.com/jquery/jquery).
Type:String
gitiles
repoUrl
Specify the root URL serving this repository (such as https://gwt.googlesource.com/gwt/).
Type:String
$class: 'GitoriousWeb'
repoUrl
Specify the root URL serving this repository (such as https://gitorious.org/gitorious/mainline).
Type:String
gogs
repoUrl
Specify the root URL serving this repository (such as https://gogs.example.com/username/some-repo-url.git).
Type:String
kiln
repoUrl
Specify the root URL serving this repository (such as https://khanacademy.kilnhg.com/Code/Website/Group/webapp).
Type:String
phabricator
repoUrl
Specify the phabricator instance root URL (such as https://phabricator.example.com).
Type:String
repo
Specify the repository name in phabricator (such as the foo part of phabricator.example.com/diffusion/foo/browse).
Type:String
redmine
repoUrl
Specify the root URL serving this repository (such as https://redmine.example.com/PATH/projects/PROJECT/repository).
Type:String
rhodeCode
repoUrl
Specify the HTTP URL for this repository's RhodeCode page (such as https://rhodecode.example.com/projects/PROJECT/repos/REPO/).
Type:String
$class: 'Stash'
repoUrl
Specify the HTTP URL for this repository's Stash page (such as https://stash.example.com/projects/PROJECT/repos/REPO/).
Type:String
teamFoundation
repoUrl
Either the name of the remote whose URL should be used, or the URL of this module in TFS (such as https://tfs.example.com/tfs/PROJECT/_git/REPO/). If empty (default), the URL of the "origin" repository is used.

If TFS is also used as the repository server, this can usually be left blank.

Type:String
viewgit
repoUrl
Specify the root URL serving this repository (such as https://git.example.com/viewgit/).
Type:String
projectName
Specify the name of the project in ViewGit (e.g. scripts, scuttle etc. from https://code.fealdia.org/viewgit/).
Type:String
lfs
gitlabAvatar
disableProjectAvatar (optional)
Due to a GitLab bug, sometimes it is not possible to GitLab API to fetch GitLab Avatar for private projects or when the api doesn't have token access. You may choose to skip avatar for projects if you want to avoid broken or self generated avatars.
Type:boolean
gitlabMarkUnstableAsSuccess
markUnstableAsSuccess (optional)
Type:boolean
gitlabSkipNotifications
gitTool
gitTool
Type:String
gitLabHookRegistration
webHookMode
Type:String
systemHookMode
Type:String
gitHubIgnoreDraftPullRequestFilter
ignoreOnPush
localBranch
logComment
logSuccess (optional)
Sometimes the user doesn't want to log the builds that succeeded. The trait only enable logging of failed/aborted builds by default. Select this option to include logging of successful builds as well.
Type:boolean
sudoUser (optional)
Enter a sudo username of the user you want to comment as on GitLab Server. Remember the token specified should have api and sudo access both (which can only be created by your GitLab Server Admin). It is recommended to create a dummy user in your GitLab Server with an appropriate username like `jenkinsadmin` etc. Leave empty if you want use the owner of the project as the commenter.
Type:String
multiBranchProjectDisplayNaming
Some branch source plugins provide additional information about discovered branches like a title or subject of merge or change requests.
With this trait, that additional information can be used for the job display names.
Note: Job display name changes do not trigger builds.
displayNamingStrategy
The different strategies:
  • Job display name with fallback to name:
    Uses the branch source plugin's display name for the PR instead of the raw name
    Value for configuration-as-code: OBJECT_DISPLAY_NAME

  • Name and, if available, display name:
    Joins the raw name and the branch source plugin's display name
    Value for configuration-as-code: RAW_AND_OBJECT_DISPLAY_NAME

Values:
OBJECT_DISPLAY_NAME
RAW_AND_OBJECT_DISPLAY_NAME
gitLabOriginDiscovery
Discovers merge requests where the origin project is the same as the target project.
strategyId
Determines how merge requests are discovered:
Merging the merge request with the current target branch revision
Discover each merge request once with the discovered revision corresponding to the result of merging with the current revision of the target branch
The current merge request revision
Discover each merge request once with the discovered revision corresponding to the merge request head revision without merging
Both the current merge request revision and the merge request merged with the current target branch revision
Discover each merge request twice. The first discovered revision corresponds to the result of merging with the current revision of the target branch in each scan. The second parallel discovered revision corresponds to the merge request head revision without merging
Type:int
gitHubPullRequestDiscovery
Discovers pull requests where the origin repository is the same as the target repository.
strategyId
Determines how pull requests are discovered:
Merging the pull request with the current target branch revision
Discover each pull request once with the discovered revision corresponding to the result of merging with the current revision of the target branch. Note that pushes to the target branch will result in new pull request builds.
The current pull request revision
Discover each pull request once with the discovered revision corresponding to the pull request head revision without merging.
Both the current pull request revision and the pull request merged with the current target branch revision
Discover each pull request twice. The first discovered revision corresponds to the result of merging with the current revision of the target branch in each scan. The second parallel discovered revision corresponds to the pull request head revision without merging.
Type:int
pruneStaleBranch
pruneStaleTag
refSpecs
templates
Array/List:
Nested object
value
A ref spec to fetch. Any occurrences of @{remote} will be replaced by the remote name (which defaults to origin) before use.
Type:String
headRegexFilter
regex
A Java regular expression to restrict the names. Names that do not match the supplied regular expression will be ignored.
NOTE: this filter will be applied to all branch like things, including change requests
Type:String
remoteName
remoteName
Type:String
sparseCheckoutPaths
extension
Nested object

Specify the paths that you'd like to sparse checkout. This may be used for saving space (Think about a reference repository). Be sure to use a recent version of Git, at least above 1.7.10

sparseCheckoutPaths
Array/List:
Nested object
path
Type:String
submoduleOption
extension
submodule
depth (optional)
Set shallow clone depth, so that git will only download recent history of the project, saving time and disk space when you just want to access the latest commits of a repository.
Type:int
disableSubmodules (optional)
By disabling support for submodules you can still keep using basic git plugin functionality and just have Jenkins to ignore submodules completely as if they didn't exist.
Type:boolean
parentCredentials (optional)
Use credentials from the default remote of the parent project.
Type:boolean
recursiveSubmodules (optional)
Retrieve all submodules recursively (uses '--recursive' option which requires git>=1.6.5)
Type:boolean
reference (optional)
Specify a folder containing a repository that will be used by Git as a reference during clone operations.
This option will be ignored if the folder is not available on the controller or agent where the clone is being executed.
To prepare a reference folder with multiple subprojects, create a bare git repository and add all the remote urls then perform a fetch:
  git init --bare
  git remote add SubProject1 https://gitrepo.com/subproject1
  git remote add SubProject2 https://gitrepo.com/subproject2
  git fetch --all
  
Type:String
shallow (optional)
Perform shallow clone, so that git will not download the history of the project, saving time and disk space when you just want to access the latest version of a repository.
Type:boolean
threads (optional)
Specify the number of threads that will be used to update submodules.
If unspecified, the command line git default thread count is used.
Type:int
timeout (optional)
Specify a timeout (in minutes) for submodules operations.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
trackingSubmodules (optional)
Retrieve the tip of the configured branch in .gitmodules (Uses '--remote' option which requires git>=1.8.2)
Type:boolean
mrTriggerComment
commentBody
Add comment body you want to use to instruct Jenkins CI to rebuild the MR
Type:String
onlyTrustedMembersCanTrigger
Type:boolean
userIdentity
extension
Nested object
name

If given, "GIT_COMMITTER_NAME=[this]" and "GIT_AUTHOR_NAME=[this]" are set for builds. This overrides whatever is in the global settings.

Type:String
email

If given, "GIT_COMMITTER_EMAIL=[this]" and "GIT_AUTHOR_EMAIL=[this]" are set for builds. This overrides whatever is in the global settings.

Type:String
WebhookListenerBuildConditionsTrait
alwaysBuildMROpen (optional)
Type:boolean
alwaysBuildMRReOpen (optional)
Type:boolean
alwaysIgnoreMRApproval (optional)
Type:boolean
alwaysIgnoreMRApproved (optional)
Type:boolean
alwaysIgnoreMRUnApproval (optional)
Type:boolean
alwaysIgnoreMRUnApproved (optional)
Type:boolean
alwaysIgnoreMRWorkInProgress (optional)
Type:boolean
alwaysIgnoreNonCodeRelatedUpdates (optional)
GitLab will send a webhook to Jenkins when there are updates to the MR including title changes, labels removed/added, etc. Enabling this option will prevent a build running if the cause was one of these updates. Note: these settings do not have any impact on build from comment settings.
Type:boolean
headWildcardFilter
includes
Space-separated list of name patterns to consider. You may use * as a wildcard; for example: master release*
NOTE: this filter will be applied to all branch like things, including change requests
Type:String
excludes
Space-separated list of name patterns to ignore even if matched by the includes list. For example: release alpha-* beta-*
NOTE: this filter will be applied to all branch like things, including change requests
Type:String
$class: 'WipeWorkspaceTrait'
gitLabBranchDiscovery
Discovers branches on the repository.
strategyId
Determines which branches are discovered.
Only branches that are not also filed as MRs
If you are discovering origin merge requests, it may not make sense to discover the same changes both as a merge request and as a branch.
Only branches that are also filed as MRs
This option exists to preserve legacy behaviour when upgrading from older versions of the plugin. NOTE: If you have an actual use case for this option please file a merge request against this text.
All branches
Ignores whether the branch is also filed as a merge request and instead discovers all branches on the origin project.
Type:int
gitLabSshCheckout
By default the discovered branches / merge requests will all use the same username / password credentials that were used for discovery when checking out sources. This means that the checkout will be using the https:// protocol for the Git repository.

This behaviour allows you to select the SSH private key to be used for checking out sources, which will consequently force the checkout to use the ssh:// protocol.

credentialsId
Credentials used to check out sources. Must be a SSH key based credential.
Type:String
gitLabTagDiscovery
gitBranchDiscovery
Discovers branches on the repository.
gitTagDiscovery
Discovers tags on the repository.
gitHubBranchDiscovery
Discovers branches on the repository.
strategyId
Determines which branches are discovered.
Exclude branches that are also filed as PRs
If you are discovering origin pull requests, you may not want to also build the source branches for those pull requests.
Only branches that are also filed as PRs
Similar to discovering origin pull requests, but discovers the branch rather than the pull request. This means env.GIT_BRANCH will be set to the branch name rather than PR-#. Also, status notifications for these builds will only be applied to the commit and not to the pull request.
All branches
Ignores whether the branch is also filed as a pull request and instead discovers all branches on the origin repository.
Type:int
gitHubSshCheckout
By default the discovered branches / pull requests will all use the same username / password credentials that were used for discovery when checking out sources. This means that the checkout will be using the https:// protocol for the Git repository.

This behaviour allows you to select the SSH private key to be used for checking out sources, which will consequently force the checkout to use the ssh:// protocol.

credentialsId
Credentials used to check out sources. Must be a SSH key based credential.
Type:String
gitHubTagDiscovery
Discovers tags on the repository.
gitlab
serverName
Select the GitLab Server where you want the projects to be discovered from.
Type:String
projectOwner
Specify the namespace which owns your projects. It can be a user, a group or a subgroup with full path. E.g: If you want projects from subgroup `a` inside group `b`, then `Owner` should be b/a
Type:String
projectPath
Select the project on which you want to perform the Multibranch Pipeline Job.
Type:String
credentialsId (optional)
Checkout credentials is only needed for private projects. Add `SSHPrivateKey` or `Username/Password` to checkout over SSH remote or HTTPS remote respectively.
Type:String
id (optional)
Type:String
projectId (optional)
Type:long
traits (optional)
Array/List:
Nested choice of objects
authorInChangelog
buildStatusNameCustomPart
Customize the pipeline status name used by Jenkins
buildStatusNameCustomPart (optional)
Enter a string to customize the status/context name for status updates published to GitLab. For a branch build the default name would be 'jenkinsci/branch'. With the buildStatusNameCustomPart 'custom' the name would be 'jenkinsci/custom/branch'. This allows to have multiple GitLab-Branch-Sources for the same GitLab-project configured.
Type:String
buildStatusNameOverwrite (optional)
Overwrites the build status name including the jenkinsci default part.
Instead of 'jenkinsci/custom/branch' just 'custom/branch'.
Type:boolean
ignoreTypeInStatusName (optional)
Type:boolean
checkoutOption
extension
checkoutOption
timeout
Specify a timeout (in minutes) for checkout.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
cleanAfterCheckout
extension
cleanAfterCheckout
Clean up the workspace after every checkout by deleting all untracked files and directories, including those which are specified in .gitignore. It also resets all tracked files to their versioned state. This ensures that the workspace is in the same state as if you cloned and checked out in a brand-new empty directory, and ensures that your build is not affected by the files generated by the previous build.
deleteUntrackedNestedRepositories (optional)
Deletes untracked submodules and any other subdirectories which contain .git directories.
Type:boolean
cleanBeforeCheckout
extension
cleanBeforeCheckout
Clean up the workspace before every checkout by deleting all untracked files and directories, including those which are specified in .gitignore. It also resets all tracked files to their versioned state. This ensures that the workspace is in the same state as if you cloned and checked out in a brand-new empty directory, and ensures that your build is not affected by the files generated by the previous build.
deleteUntrackedNestedRepositories (optional)
Deletes untracked submodules and any other subdirectories which contain .git directories.
Type:boolean
cloneOption
extension
cloneOption
shallow
Perform shallow clone, so that git will not download the history of the project, saving time and disk space when you just want to access the latest version of a repository.
Type:boolean
noTags
Deselect this to perform a clone without tags, saving time and disk space when you just want to access what is specified by the refspec.
Type:boolean
reference
Specify a folder containing a repository that will be used by Git as a reference during clone operations.
This option will be ignored if the folder is not available on the controller or agent where the clone is being executed.
Type:String
timeout
Specify a timeout (in minutes) for clone and fetch operations.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
depth (optional)
Set shallow clone depth, so that git will only download recent history of the project, saving time and disk space when you just want to access the latest commits of a repository.
Type:int
honorRefspec (optional)
Perform initial clone using the refspec defined for the repository. This can save time, data transfer and disk space when you only need to access the references specified by the refspec.
Type:boolean
discoverOtherRefs
Discovers other specified refs on the repository.
ref

The pattern under /refs on the remote repository to discover, can contain a wildcard.
Example: test/*/merged

Type:String
nameMapping (optional)

Mapping for how the ref can be named in for example the @Library.
Example: test-@{1}
Where @{1} replaces the first wildcard in the ref when discovered.

By default it will be "namespace_before_wildcard-@{1}". E.g. if ref is "test/*/merged" the default mapping would be "test-@{1}".

Type:String
gitLabForkDiscovery
Discovers merge requests where the origin project is a fork of the target project.
strategyId
Determines how merge requests are discovered:
Merging the merge request with the current target branch revision
Discover each merge request once with the discovered revision corresponding to the result of merging with the current revision of the target branch
The current merge request revision
Discover each merge request once with the discovered revision corresponding to the merge request head revision without merging
Both the current merge request revision and the merge request merged with the current target branch revision
Discover each merge request twice. The first discovered revision corresponds to the result of merging with the current revision of the target branch in each scan. The second parallel discovered revision corresponds to the merge request head revision without merging
Type:int
trust

One of the great powers of merge requests is that anyone with read access to a project can fork it, commit some changes to their fork and then create a merge request against the original project with their changes. There are some files stored in source control that are important. For example, a Jenkinsfile may contain configuration details to sandbox merge requests in order to mitigate against malicious merge requests. In order to protect against a malicious merge request itself modifying the Jenkinsfile to remove the protections, you can define the trust policy for merge requests from forks.

Other plugins can extend the available trust policies. The default policies are:

Nobody
Merge requests from forks will all be treated as untrusted. This means that where Jenkins requires a trusted file (e.g. Jenkinsfile) the contents of that file will be retrieved from the target branch on the origin project and not from the merge request branch on the fork project.
Members
Merge requests from collaborators to the origin project will be treated as trusted, all other merge requests from fork repositories will be treated as untrusted. Note that if credentials used by Jenkins for scanning the project does not have permission to query the list of contributors to the origin project then only the origin account will be treated as trusted - i.e. this will fall back to Nobody.
Trusted Members
Merge requests forks will be treated as trusted if and only if the fork owner has either Developer or Maintainer or Owner Access Level in the origin project. This is the recommended policy.
Everyone
All merge requests from forks will be treated as trusted. NOTE: this option can be dangerous if used on a public project hosted on a GitLab instance.
java.lang.UnsupportedOperationException: do not know how to categorize attributes of type jenkins.scm.api.trait.SCMHeadAuthority<? super io.jenkins.plugins.gitlabbranchsource.GitLabSCMSourceRequest, ? extends jenkins.scm.api.mixin.ChangeRequestSCMHead2, ? extends jenkins.scm.api.SCMRevision>
buildMRForksNotMirror (optional)
Add discovery of merge requests where the origin project is a fork of a certain project, but the target project is not the original forked project. To be used in case one has a GitLab project which is a fork of another project from another team, in order to isolate artefacts and allow an MR flow. This means using MRs inside that fork from branches in the fork back to the fork's default branch. (Implements https://github.com/jenkinsci/gitlab-branch-source-plugin/issues/167)
Type:boolean
gitHubForkDiscovery
Discovers pull requests where the origin repository is a fork of the target repository.
strategyId
Determines how pull requests are discovered:
Merging the pull request with the current target branch revision
Discover each pull request once with the discovered revision corresponding to the result of merging with the current revision of the target branch. Note that pushes to the target branch will result in new pull request builds.
The current pull request revision
Discover each pull request once with the discovered revision corresponding to the pull request head revision without merging.
Both the current pull request revision and the pull request merged with the current target branch revision
Discover each pull request twice. The first discovered revision corresponds to the result of merging with the current revision of the target branch in each scan. The second parallel discovered revision corresponds to the pull request head revision without merging.
Type:int
trust

One of the great powers of pull requests is that anyone with read access to a repository can fork it, commit some changes to their fork and then create a pull request against the original repository with their changes. There are some files stored in source control that are important. For example, a Jenkinsfile may contain configuration details to sandbox pull requests in order to mitigate against malicious pull requests. In order to protect against a malicious pull request itself modifying the Jenkinsfile to remove the protections, you can define the trust policy for pull requests from forks.

Other plugins can extend the available trust policies. The default policies are:

Nobody
Pull requests from forks will all be treated as untrusted. This means that where Jenkins requires a trusted file (e.g. Jenkinsfile) the contents of that file will be retrieved from the target branch on the origin repository and not from the pull request branch on the fork repository.
Collaborators
Pull requests from collaborators to the origin repository will be treated as trusted, all other pull requests from fork repositories will be treated as untrusted. Note that if credentials used by Jenkins for scanning the repository does not have permission to query the list of collaborators to the origin repository then only the origin account will be treated as trusted - i.e. this will fall back to Nobody. NOTE: all collaborators are trusted, even if they are only members of a team with read permission.
Everyone
All pull requests from forks will be treated as trusted. NOTE: this option can be dangerous if used on a public repository hosted on GitHub.
From users with Admin or Write permission
Pull requests forks will be treated as trusted if and only if the fork owner has either Admin or Write permissions on the origin repository. This is the recommended policy. Note that this strategy requires the Review a user's permission level API, as a result on GitHub Enterprise Server versions before 2.12 this is the same as trusting Nobody.
Nested choice of objects
gitHubTrustContributors
gitHubTrustEveryone
gitHubTrustNobody
gitHubTrustPermissions
browser
browser
Nested choice of objects
assembla
repoUrl
Specify the root URL serving this repository (such as https://www.assembla.com/code/PROJECT/git/).
Type:String
bitbucketServer
repoUrl
Specify the Bitbucket Server root URL for this repository (such as https://bitbucket:7990/OWNER/REPO/).
Type:String
bitbucket
repoUrl
Specify the root URL serving this repository (such as https://bitbucket.org/OWNER/REPO/).
Type:String
cgit
repoUrl
Specify the root URL serving this repository (such as https://cgit.example.com:port/group/REPO/).
Type:String
fisheye
repoUrl
Specify the URL of this repository in FishEye (such as https://fisheye.example.com/browse/project/).
Type:String
gitblit
repoUrl
Specify the root URL serving this repository.
Type:String
projectName
Specify the name of the project in GitBlit.
Type:String
gitLab
repoUrl
Specify the root URL serving this repository (such as https://gitlab.com/username/repository/).
Type:String
version (optional)
Specify the major and minor version of GitLab you use (such as 9.1). If you don't specify a version, a modern version of GitLab (>= 8.0) is assumed.
Type:String
gitLabBrowser
Specify the HTTP URL for this project's GitLab page so that links to changes can be automatically generated by Jenkins. The URL needs to include the owner and project. If the GitLab server is https://gitLab.example.com then the URL for bob's skunkworks project might be https://gitLab.example.com/bob/skunkworks.
projectUrl
Specify the HTTP URL for this project's GitLab page. The URL needs to include the owner and project so, for example, if the GitLab server is https://gitLab.example.com then the URL for bob's skunkworks project might be https://gitLab.example.com/bob/skunkworks
Type:String
gitList
repoUrl
Specify the root URL serving this repository (such as https://gitlist.example.com/repo/).
Type:String
gitWeb
repoUrl
Specify the root URL serving this repository (such as https://github.com/jenkinsci/jenkins.git).
Type:String
github
repoUrl
Specify the HTTP URL for this repository's GitHub page (such as https://github.com/jquery/jquery).
Type:String
gitiles
repoUrl
Specify the root URL serving this repository (such as https://gwt.googlesource.com/gwt/).
Type:String
$class: 'GitoriousWeb'
repoUrl
Specify the root URL serving this repository (such as https://gitorious.org/gitorious/mainline).
Type:String
gogs
repoUrl
Specify the root URL serving this repository (such as https://gogs.example.com/username/some-repo-url.git).
Type:String
kiln
repoUrl
Specify the root URL serving this repository (such as https://khanacademy.kilnhg.com/Code/Website/Group/webapp).
Type:String
phabricator
repoUrl
Specify the phabricator instance root URL (such as https://phabricator.example.com).
Type:String
repo
Specify the repository name in phabricator (such as the foo part of phabricator.example.com/diffusion/foo/browse).
Type:String
redmine
repoUrl
Specify the root URL serving this repository (such as https://redmine.example.com/PATH/projects/PROJECT/repository).
Type:String
rhodeCode
repoUrl
Specify the HTTP URL for this repository's RhodeCode page (such as https://rhodecode.example.com/projects/PROJECT/repos/REPO/).
Type:String
$class: 'Stash'
repoUrl
Specify the HTTP URL for this repository's Stash page (such as https://stash.example.com/projects/PROJECT/repos/REPO/).
Type:String
teamFoundation
repoUrl
Either the name of the remote whose URL should be used, or the URL of this module in TFS (such as https://tfs.example.com/tfs/PROJECT/_git/REPO/). If empty (default), the URL of the "origin" repository is used.

If TFS is also used as the repository server, this can usually be left blank.

Type:String
viewgit
repoUrl
Specify the root URL serving this repository (such as https://git.example.com/viewgit/).
Type:String
projectName
Specify the name of the project in ViewGit (e.g. scripts, scuttle etc. from https://code.fealdia.org/viewgit/).
Type:String
lfs
gitlabAvatar
disableProjectAvatar (optional)
Due to a GitLab bug, sometimes it is not possible to GitLab API to fetch GitLab Avatar for private projects or when the api doesn't have token access. You may choose to skip avatar for projects if you want to avoid broken or self generated avatars.
Type:boolean
gitlabMarkUnstableAsSuccess
markUnstableAsSuccess (optional)
Type:boolean
gitlabSkipNotifications
gitTool
gitTool
Type:String
gitLabHookRegistration
webHookMode
Type:String
systemHookMode
Type:String
gitHubIgnoreDraftPullRequestFilter
ignoreOnPush
localBranch
logComment
logSuccess (optional)
Sometimes the user doesn't want to log the builds that succeeded. The trait only enable logging of failed/aborted builds by default. Select this option to include logging of successful builds as well.
Type:boolean
sudoUser (optional)
Enter a sudo username of the user you want to comment as on GitLab Server. Remember the token specified should have api and sudo access both (which can only be created by your GitLab Server Admin). It is recommended to create a dummy user in your GitLab Server with an appropriate username like `jenkinsadmin` etc. Leave empty if you want use the owner of the project as the commenter.
Type:String
multiBranchProjectDisplayNaming
Some branch source plugins provide additional information about discovered branches like a title or subject of merge or change requests.
With this trait, that additional information can be used for the job display names.
Note: Job display name changes do not trigger builds.
displayNamingStrategy
The different strategies:
  • Job display name with fallback to name:
    Uses the branch source plugin's display name for the PR instead of the raw name
    Value for configuration-as-code: OBJECT_DISPLAY_NAME

  • Name and, if available, display name:
    Joins the raw name and the branch source plugin's display name
    Value for configuration-as-code: RAW_AND_OBJECT_DISPLAY_NAME

Values:
OBJECT_DISPLAY_NAME
RAW_AND_OBJECT_DISPLAY_NAME
gitLabOriginDiscovery
Discovers merge requests where the origin project is the same as the target project.
strategyId
Determines how merge requests are discovered:
Merging the merge request with the current target branch revision
Discover each merge request once with the discovered revision corresponding to the result of merging with the current revision of the target branch
The current merge request revision
Discover each merge request once with the discovered revision corresponding to the merge request head revision without merging
Both the current merge request revision and the merge request merged with the current target branch revision
Discover each merge request twice. The first discovered revision corresponds to the result of merging with the current revision of the target branch in each scan. The second parallel discovered revision corresponds to the merge request head revision without merging
Type:int
gitHubPullRequestDiscovery
Discovers pull requests where the origin repository is the same as the target repository.
strategyId
Determines how pull requests are discovered:
Merging the pull request with the current target branch revision
Discover each pull request once with the discovered revision corresponding to the result of merging with the current revision of the target branch. Note that pushes to the target branch will result in new pull request builds.
The current pull request revision
Discover each pull request once with the discovered revision corresponding to the pull request head revision without merging.
Both the current pull request revision and the pull request merged with the current target branch revision
Discover each pull request twice. The first discovered revision corresponds to the result of merging with the current revision of the target branch in each scan. The second parallel discovered revision corresponds to the pull request head revision without merging.
Type:int
pruneStaleBranch
pruneStaleTag
refSpecs
templates
Array/List:
Nested object
value
A ref spec to fetch. Any occurrences of @{remote} will be replaced by the remote name (which defaults to origin) before use.
Type:String
headRegexFilter
regex
A Java regular expression to restrict the names. Names that do not match the supplied regular expression will be ignored.
NOTE: this filter will be applied to all branch like things, including change requests
Type:String
remoteName
remoteName
Type:String
sparseCheckoutPaths
extension
Nested object

Specify the paths that you'd like to sparse checkout. This may be used for saving space (Think about a reference repository). Be sure to use a recent version of Git, at least above 1.7.10

sparseCheckoutPaths
Array/List:
Nested object
path
Type:String
submoduleOption
extension
submodule
depth (optional)
Set shallow clone depth, so that git will only download recent history of the project, saving time and disk space when you just want to access the latest commits of a repository.
Type:int
disableSubmodules (optional)
By disabling support for submodules you can still keep using basic git plugin functionality and just have Jenkins to ignore submodules completely as if they didn't exist.
Type:boolean
parentCredentials (optional)
Use credentials from the default remote of the parent project.
Type:boolean
recursiveSubmodules (optional)
Retrieve all submodules recursively (uses '--recursive' option which requires git>=1.6.5)
Type:boolean
reference (optional)
Specify a folder containing a repository that will be used by Git as a reference during clone operations.
This option will be ignored if the folder is not available on the controller or agent where the clone is being executed.
To prepare a reference folder with multiple subprojects, create a bare git repository and add all the remote urls then perform a fetch:
  git init --bare
  git remote add SubProject1 https://gitrepo.com/subproject1
  git remote add SubProject2 https://gitrepo.com/subproject2
  git fetch --all
  
Type:String
shallow (optional)
Perform shallow clone, so that git will not download the history of the project, saving time and disk space when you just want to access the latest version of a repository.
Type:boolean
threads (optional)
Specify the number of threads that will be used to update submodules.
If unspecified, the command line git default thread count is used.
Type:int
timeout (optional)
Specify a timeout (in minutes) for submodules operations.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
trackingSubmodules (optional)
Retrieve the tip of the configured branch in .gitmodules (Uses '--remote' option which requires git>=1.8.2)
Type:boolean
mrTriggerComment
commentBody
Add comment body you want to use to instruct Jenkins CI to rebuild the MR
Type:String
onlyTrustedMembersCanTrigger
Type:boolean
userIdentity
extension
Nested object
name

If given, "GIT_COMMITTER_NAME=[this]" and "GIT_AUTHOR_NAME=[this]" are set for builds. This overrides whatever is in the global settings.

Type:String
email

If given, "GIT_COMMITTER_EMAIL=[this]" and "GIT_AUTHOR_EMAIL=[this]" are set for builds. This overrides whatever is in the global settings.

Type:String
WebhookListenerBuildConditionsTrait
alwaysBuildMROpen (optional)
Type:boolean
alwaysBuildMRReOpen (optional)
Type:boolean
alwaysIgnoreMRApproval (optional)
Type:boolean
alwaysIgnoreMRApproved (optional)
Type:boolean
alwaysIgnoreMRUnApproval (optional)
Type:boolean
alwaysIgnoreMRUnApproved (optional)
Type:boolean
alwaysIgnoreMRWorkInProgress (optional)
Type:boolean
alwaysIgnoreNonCodeRelatedUpdates (optional)
GitLab will send a webhook to Jenkins when there are updates to the MR including title changes, labels removed/added, etc. Enabling this option will prevent a build running if the cause was one of these updates. Note: these settings do not have any impact on build from comment settings.
Type:boolean
headWildcardFilter
includes
Space-separated list of name patterns to consider. You may use * as a wildcard; for example: master release*
NOTE: this filter will be applied to all branch like things, including change requests
Type:String
excludes
Space-separated list of name patterns to ignore even if matched by the includes list. For example: release alpha-* beta-*
NOTE: this filter will be applied to all branch like things, including change requests
Type:String
$class: 'WipeWorkspaceTrait'
gitLabBranchDiscovery
Discovers branches on the repository.
strategyId
Determines which branches are discovered.
Only branches that are not also filed as MRs
If you are discovering origin merge requests, it may not make sense to discover the same changes both as a merge request and as a branch.
Only branches that are also filed as MRs
This option exists to preserve legacy behaviour when upgrading from older versions of the plugin. NOTE: If you have an actual use case for this option please file a merge request against this text.
All branches
Ignores whether the branch is also filed as a merge request and instead discovers all branches on the origin project.
Type:int
gitLabSshCheckout
By default the discovered branches / merge requests will all use the same username / password credentials that were used for discovery when checking out sources. This means that the checkout will be using the https:// protocol for the Git repository.

This behaviour allows you to select the SSH private key to be used for checking out sources, which will consequently force the checkout to use the ssh:// protocol.

credentialsId
Credentials used to check out sources. Must be a SSH key based credential.
Type:String
gitLabTagDiscovery
gitBranchDiscovery
Discovers branches on the repository.
gitTagDiscovery
Discovers tags on the repository.
gitHubBranchDiscovery
Discovers branches on the repository.
strategyId
Determines which branches are discovered.
Exclude branches that are also filed as PRs
If you are discovering origin pull requests, you may not want to also build the source branches for those pull requests.
Only branches that are also filed as PRs
Similar to discovering origin pull requests, but discovers the branch rather than the pull request. This means env.GIT_BRANCH will be set to the branch name rather than PR-#. Also, status notifications for these builds will only be applied to the commit and not to the pull request.
All branches
Ignores whether the branch is also filed as a pull request and instead discovers all branches on the origin repository.
Type:int
gitHubSshCheckout
By default the discovered branches / pull requests will all use the same username / password credentials that were used for discovery when checking out sources. This means that the checkout will be using the https:// protocol for the Git repository.

This behaviour allows you to select the SSH private key to be used for checking out sources, which will consequently force the checkout to use the ssh:// protocol.

credentialsId
Credentials used to check out sources. Must be a SSH key based credential.
Type:String
gitHubTagDiscovery
Discovers tags on the repository.
git
remote
Specify the URL of this remote repository. This uses the same syntax as your git clone command.
Type:String
browser (optional)
Nested choice of objects
assembla
repoUrl
Specify the root URL serving this repository (such as https://www.assembla.com/code/PROJECT/git/).
Type:String
bitbucketServer
repoUrl
Specify the Bitbucket Server root URL for this repository (such as https://bitbucket:7990/OWNER/REPO/).
Type:String
bitbucket
repoUrl
Specify the root URL serving this repository (such as https://bitbucket.org/OWNER/REPO/).
Type:String
cgit
repoUrl
Specify the root URL serving this repository (such as https://cgit.example.com:port/group/REPO/).
Type:String
fisheye
repoUrl
Specify the URL of this repository in FishEye (such as https://fisheye.example.com/browse/project/).
Type:String
gitblit
repoUrl
Specify the root URL serving this repository.
Type:String
projectName
Specify the name of the project in GitBlit.
Type:String
gitLab
repoUrl
Specify the root URL serving this repository (such as https://gitlab.com/username/repository/).
Type:String
version (optional)
Specify the major and minor version of GitLab you use (such as 9.1). If you don't specify a version, a modern version of GitLab (>= 8.0) is assumed.
Type:String
gitLabBrowser
Specify the HTTP URL for this project's GitLab page so that links to changes can be automatically generated by Jenkins. The URL needs to include the owner and project. If the GitLab server is https://gitLab.example.com then the URL for bob's skunkworks project might be https://gitLab.example.com/bob/skunkworks.
projectUrl
Specify the HTTP URL for this project's GitLab page. The URL needs to include the owner and project so, for example, if the GitLab server is https://gitLab.example.com then the URL for bob's skunkworks project might be https://gitLab.example.com/bob/skunkworks
Type:String
gitList
repoUrl
Specify the root URL serving this repository (such as https://gitlist.example.com/repo/).
Type:String
gitWeb
repoUrl
Specify the root URL serving this repository (such as https://github.com/jenkinsci/jenkins.git).
Type:String
github
repoUrl
Specify the HTTP URL for this repository's GitHub page (such as https://github.com/jquery/jquery).
Type:String
gitiles
repoUrl
Specify the root URL serving this repository (such as https://gwt.googlesource.com/gwt/).
Type:String
$class: 'GitoriousWeb'
repoUrl
Specify the root URL serving this repository (such as https://gitorious.org/gitorious/mainline).
Type:String
gogs
repoUrl
Specify the root URL serving this repository (such as https://gogs.example.com/username/some-repo-url.git).
Type:String
kiln
repoUrl
Specify the root URL serving this repository (such as https://khanacademy.kilnhg.com/Code/Website/Group/webapp).
Type:String
phabricator
repoUrl
Specify the phabricator instance root URL (such as https://phabricator.example.com).
Type:String
repo
Specify the repository name in phabricator (such as the foo part of phabricator.example.com/diffusion/foo/browse).
Type:String
redmine
repoUrl
Specify the root URL serving this repository (such as https://redmine.example.com/PATH/projects/PROJECT/repository).
Type:String
rhodeCode
repoUrl
Specify the HTTP URL for this repository's RhodeCode page (such as https://rhodecode.example.com/projects/PROJECT/repos/REPO/).
Type:String
$class: 'Stash'
repoUrl
Specify the HTTP URL for this repository's Stash page (such as https://stash.example.com/projects/PROJECT/repos/REPO/).
Type:String
teamFoundation
repoUrl
Either the name of the remote whose URL should be used, or the URL of this module in TFS (such as https://tfs.example.com/tfs/PROJECT/_git/REPO/). If empty (default), the URL of the "origin" repository is used.

If TFS is also used as the repository server, this can usually be left blank.

Type:String
viewgit
repoUrl
Specify the root URL serving this repository (such as https://git.example.com/viewgit/).
Type:String
projectName
Specify the name of the project in ViewGit (e.g. scripts, scuttle etc. from https://code.fealdia.org/viewgit/).
Type:String
credentialsId (optional)
Credentials used to scan branches and check out sources.
Type:String
extensions (optional)
Array/List:
Nested choice of objects
authorInChangelog
The default behavior is to use the Git commit's "Committer" value in Jenkins' build changesets. If this option is selected, the Git commit's "Author" value would be used instead.
$class: 'BuildChooserSetting'
When you are interested in using a job to build multiple heads (most typically multiple branches), you can choose how Jenkins choose what branches to build in what order.

This extension point in Jenkins is used by many other plugins to control the job to build specific commits. When you activate those plugins, you may see them installing a custom strategy here.

buildChooser
Nested choice of objects
$class: 'AncestryBuildChooser'
maximumAgeInDays
Type:int
ancestorCommitSha1
Type:String
$class: 'DefaultBuildChooser'
$class: 'InverseBuildChooser'
buildSingleRevisionOnly
Disable scheduling for multiple candidate revisions.
If we have 3 branches:
----A--.---.--- B
         \-----C
jenkins would try to build (B) and (C).
This behaviour disables this and only builds one of them.
It is helpful to reduce the load of the Jenkins infrastructure when the SCM system like Bitbucket or GitHub should decide what commits to build.
changelogToBranch
This method calculates the changelog against the specified branch.
options
changelogBase
compareRemote
Name of the repository, such as origin, that contains the branch you specify below.
Type:String
compareTarget
The name of the branch within the named repository to compare against.
Type:String
checkoutOption
timeout
Specify a timeout (in minutes) for checkout.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
cleanBeforeCheckout
Clean up the workspace before every checkout by deleting all untracked files and directories, including those which are specified in .gitignore. It also resets all tracked files to their versioned state. This ensures that the workspace is in the same state as if you cloned and checked out in a brand-new empty directory, and ensures that your build is not affected by the files generated by the previous build.
deleteUntrackedNestedRepositories (optional)
Deletes untracked submodules and any other subdirectories which contain .git directories.
Type:boolean
cleanAfterCheckout
Clean up the workspace after every checkout by deleting all untracked files and directories, including those which are specified in .gitignore. It also resets all tracked files to their versioned state. This ensures that the workspace is in the same state as if you cloned and checked out in a brand-new empty directory, and ensures that your build is not affected by the files generated by the previous build.
deleteUntrackedNestedRepositories (optional)
Deletes untracked submodules and any other subdirectories which contain .git directories.
Type:boolean
cloneOption
shallow
Perform shallow clone, so that git will not download the history of the project, saving time and disk space when you just want to access the latest version of a repository.
Type:boolean
noTags
Deselect this to perform a clone without tags, saving time and disk space when you just want to access what is specified by the refspec.
Type:boolean
reference
Specify a folder containing a repository that will be used by Git as a reference during clone operations.
This option will be ignored if the folder is not available on the controller or agent where the clone is being executed.
Type:String
timeout
Specify a timeout (in minutes) for clone and fetch operations.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
depth (optional)
Set shallow clone depth, so that git will only download recent history of the project, saving time and disk space when you just want to access the latest commits of a repository.
Type:int
honorRefspec (optional)
Perform initial clone using the refspec defined for the repository. This can save time, data transfer and disk space when you only need to access the references specified by the refspec.
Type:boolean
$class: 'DisableRemotePoll'
Git plugin uses git ls-remote polling mechanism by default when configured with a single branch (no wildcards!). This compare the latest built commit SHA with the remote branch without cloning a local copy of the repo.

If you don't want to / can't use this.

If this option is selected, polling will require a workspace and might trigger unwanted builds (see JENKINS-10131).
lfs
Enable git large file support for the workspace by pulling large files after the checkout completes. Requires that the controller and each agent performing an LFS checkout have installed `git lfs`.
$class: 'IgnoreNotifyCommit'
If checked, this repository will be ignored when the notifyCommit-URL is accessed regardless of if the repository matches or not.
localBranch
If given, checkout the revision to build as HEAD on this branch.

If selected, and its value is an empty string or "**", then the branch name is computed from the remote branch without the origin. In that case, a remote branch origin/master will be checked out to a local branch named master, and a remote branch origin/develop/new-feature will be checked out to a local branch named develop/newfeature.

Please note that this has not been tested with submodules.

localBranch
Type:String
$class: 'MessageExclusion'
excludedMessage
If set, and Jenkins is set to poll for changes, Jenkins will ignore any revisions committed with message matched to Pattern when determining if a build needs to be triggered. This can be used to exclude commits done by the build itself from triggering another build, assuming the build server commits the change with a distinct message.

Exclusion uses Pattern matching

.*\[maven-release-plugin\].*
The example above illustrates that if only revisions with "[maven-release-plugin]" message in first comment line have been committed to the SCM a build will not occur.

You can create more complex patterns using embedded flag expressions.

(?s).*FOO.*
This example will search FOO message in all comment lines.
Type:String
$class: 'PathRestriction'
If set, and Jenkins is set to poll for changes, Jenkins will pay attention to included and/or excluded files and/or folders when determining if a build needs to be triggered.

Using this behaviour will preclude the faster git ls-remote polling mechanism, forcing polling to require a workspace thus sometimes triggering unwanted builds, as if you had selected the Force polling using workspace extension as well.

includedRegions
Each inclusion uses java regular expression pattern matching, and must be separated by a new line. An empty list implies that everything is included.

    myapp/src/main/web/.*\.html
    myapp/src/main/web/.*\.jpeg
    myapp/src/main/web/.*\.gif
  
The example above illustrates that a build will only occur, if html/jpeg/gif files have been committed to the SCM. Exclusions take precedence over inclusions, if there is an overlap between included and excluded regions.
Type:String
excludedRegions
Each exclusion uses java regular expression pattern matching, and must be separated by a new line.

    myapp/src/main/web/.*\.html
    myapp/src/main/web/.*\.jpeg
    myapp/src/main/web/.*\.gif
  
The example above illustrates that if only html/jpeg/gif files have been committed to the SCM a build will not occur.
Type:String
perBuildTag
Create a tag in the workspace for every build to unambiguously mark the commit that was built. You can combine this with Git publisher to push the tags to the remote repository.
$class: 'PreBuildMerge'
These options allow you to perform a merge to a particular branch before building. For example, you could specify an integration branch to be built, and to merge to master. In this scenario, on every change of integration, Jenkins will perform a merge with the master branch, and try to perform a build if the merge is successful. It then may push the merge back to the remote repository if the Git Push post-build action is selected.
options
Nested object
mergeTarget
The name of the branch within the named repository to merge to, such as master.
Type:String
fastForwardMode (optional)
Merge fast-forward mode selection.
The default, --ff, gracefully falls back to a merge commit when required.
For more information, see the Git Merge Documentation
Values:
FF
FF_ONLY
NO_FF
mergeRemote (optional)
Name of the repository, such as origin, that contains the branch you specify below. If left blank, it'll default to the name of the first repository configured above.
Type:String
mergeStrategy (optional)
Merge strategy selection. This feature is not fully implemented in JGIT.
Values:
DEFAULT
RESOLVE
RECURSIVE
OCTOPUS
OURS
SUBTREE
RECURSIVE_THEIRS
pruneStaleBranch
Run "git remote prune" for each remote, to prune obsolete local branches.
pruneTags
pruneTags
Type:boolean
$class: 'RelativeTargetDirectory'
relativeTargetDir
Specify a local directory (relative to the workspace root) where the Git repository will be checked out. If left empty, the workspace root itself will be used.

This extension should not be used in Jenkins Pipeline (either declarative or scripted). Jenkins Pipeline already provides standard techniques for checkout to a subdirectory. Use ws and dir in Jenkins Pipeline rather than this extension.

Type:String
$class: 'ScmName'

Unique name for this SCM. Needed when using Git within the Multi SCM plugin.

name
Type:String
$class: 'SparseCheckoutPaths'

Specify the paths that you'd like to sparse checkout. This may be used for saving space (Think about a reference repository). Be sure to use a recent version of Git, at least above 1.7.10

sparseCheckoutPaths
Array/List:
Nested object
path
Type:String
submodule
depth (optional)
Set shallow clone depth, so that git will only download recent history of the project, saving time and disk space when you just want to access the latest commits of a repository.
Type:int
disableSubmodules (optional)
By disabling support for submodules you can still keep using basic git plugin functionality and just have Jenkins to ignore submodules completely as if they didn't exist.
Type:boolean
parentCredentials (optional)
Use credentials from the default remote of the parent project.
Type:boolean
recursiveSubmodules (optional)
Retrieve all submodules recursively (uses '--recursive' option which requires git>=1.6.5)
Type:boolean
reference (optional)
Specify a folder containing a repository that will be used by Git as a reference during clone operations.
This option will be ignored if the folder is not available on the controller or agent where the clone is being executed.
To prepare a reference folder with multiple subprojects, create a bare git repository and add all the remote urls then perform a fetch:
  git init --bare
  git remote add SubProject1 https://gitrepo.com/subproject1
  git remote add SubProject2 https://gitrepo.com/subproject2
  git fetch --all
  
Type:String
shallow (optional)
Perform shallow clone, so that git will not download the history of the project, saving time and disk space when you just want to access the latest version of a repository.
Type:boolean
threads (optional)
Specify the number of threads that will be used to update submodules.
If unspecified, the command line git default thread count is used.
Type:int
timeout (optional)
Specify a timeout (in minutes) for submodules operations.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
trackingSubmodules (optional)
Retrieve the tip of the configured branch in .gitmodules (Uses '--remote' option which requires git>=1.8.2)
Type:boolean
$class: 'UserExclusion'
excludedUsers
If set, and Jenkins is set to poll for changes, Jenkins will ignore any revisions committed by users in this list when determining if a build needs to be triggered. This can be used to exclude commits done by the build itself from triggering another build, assuming the build server commits the change with a distinct SCM user.

Using this behaviour will preclude the faster git ls-remote polling mechanism, forcing polling to require a workspace thus sometimes triggering unwanted builds, as if you had selected the Force polling using workspace extension as well.

Each exclusion uses exact string comparison and must be separated by a new line. User names are only excluded if they exactly match one of the names in this list.

auto_build_user
The example above illustrates that if only revisions by "auto_build_user" have been committed to the SCM a build will not occur.
Type:String
$class: 'UserIdentity'
name

If given, "GIT_COMMITTER_NAME=[this]" and "GIT_AUTHOR_NAME=[this]" are set for builds. This overrides whatever is in the global settings.

Type:String
email

If given, "GIT_COMMITTER_EMAIL=[this]" and "GIT_AUTHOR_EMAIL=[this]" are set for builds. This overrides whatever is in the global settings.

Type:String
$class: 'WipeWorkspace'
Delete the contents of the workspace before building, ensuring a fully fresh workspace.
gitTool (optional)
Type:String
id (optional)
Type:String
traits (optional)
Array/List:
Nested choice of objects
authorInChangelog
buildStatusNameCustomPart
Customize the pipeline status name used by Jenkins
buildStatusNameCustomPart (optional)
Enter a string to customize the status/context name for status updates published to GitLab. For a branch build the default name would be 'jenkinsci/branch'. With the buildStatusNameCustomPart 'custom' the name would be 'jenkinsci/custom/branch'. This allows to have multiple GitLab-Branch-Sources for the same GitLab-project configured.
Type:String
buildStatusNameOverwrite (optional)
Overwrites the build status name including the jenkinsci default part.
Instead of 'jenkinsci/custom/branch' just 'custom/branch'.
Type:boolean
ignoreTypeInStatusName (optional)
Type:boolean
checkoutOption
extension
checkoutOption
timeout
Specify a timeout (in minutes) for checkout.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
cleanAfterCheckout
extension
cleanAfterCheckout
Clean up the workspace after every checkout by deleting all untracked files and directories, including those which are specified in .gitignore. It also resets all tracked files to their versioned state. This ensures that the workspace is in the same state as if you cloned and checked out in a brand-new empty directory, and ensures that your build is not affected by the files generated by the previous build.
deleteUntrackedNestedRepositories (optional)
Deletes untracked submodules and any other subdirectories which contain .git directories.
Type:boolean
cleanBeforeCheckout
extension
cleanBeforeCheckout
Clean up the workspace before every checkout by deleting all untracked files and directories, including those which are specified in .gitignore. It also resets all tracked files to their versioned state. This ensures that the workspace is in the same state as if you cloned and checked out in a brand-new empty directory, and ensures that your build is not affected by the files generated by the previous build.
deleteUntrackedNestedRepositories (optional)
Deletes untracked submodules and any other subdirectories which contain .git directories.
Type:boolean
cloneOption
extension
cloneOption
shallow
Perform shallow clone, so that git will not download the history of the project, saving time and disk space when you just want to access the latest version of a repository.
Type:boolean
noTags
Deselect this to perform a clone without tags, saving time and disk space when you just want to access what is specified by the refspec.
Type:boolean
reference
Specify a folder containing a repository that will be used by Git as a reference during clone operations.
This option will be ignored if the folder is not available on the controller or agent where the clone is being executed.
Type:String
timeout
Specify a timeout (in minutes) for clone and fetch operations.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
depth (optional)
Set shallow clone depth, so that git will only download recent history of the project, saving time and disk space when you just want to access the latest commits of a repository.
Type:int
honorRefspec (optional)
Perform initial clone using the refspec defined for the repository. This can save time, data transfer and disk space when you only need to access the references specified by the refspec.
Type:boolean
discoverOtherRefs
Discovers other specified refs on the repository.
ref

The pattern under /refs on the remote repository to discover, can contain a wildcard.
Example: test/*/merged

Type:String
nameMapping (optional)

Mapping for how the ref can be named in for example the @Library.
Example: test-@{1}
Where @{1} replaces the first wildcard in the ref when discovered.

By default it will be "namespace_before_wildcard-@{1}". E.g. if ref is "test/*/merged" the default mapping would be "test-@{1}".

Type:String
gitLabForkDiscovery
Discovers merge requests where the origin project is a fork of the target project.
strategyId
Determines how merge requests are discovered:
Merging the merge request with the current target branch revision
Discover each merge request once with the discovered revision corresponding to the result of merging with the current revision of the target branch
The current merge request revision
Discover each merge request once with the discovered revision corresponding to the merge request head revision without merging
Both the current merge request revision and the merge request merged with the current target branch revision
Discover each merge request twice. The first discovered revision corresponds to the result of merging with the current revision of the target branch in each scan. The second parallel discovered revision corresponds to the merge request head revision without merging
Type:int
trust

One of the great powers of merge requests is that anyone with read access to a project can fork it, commit some changes to their fork and then create a merge request against the original project with their changes. There are some files stored in source control that are important. For example, a Jenkinsfile may contain configuration details to sandbox merge requests in order to mitigate against malicious merge requests. In order to protect against a malicious merge request itself modifying the Jenkinsfile to remove the protections, you can define the trust policy for merge requests from forks.

Other plugins can extend the available trust policies. The default policies are:

Nobody
Merge requests from forks will all be treated as untrusted. This means that where Jenkins requires a trusted file (e.g. Jenkinsfile) the contents of that file will be retrieved from the target branch on the origin project and not from the merge request branch on the fork project.
Members
Merge requests from collaborators to the origin project will be treated as trusted, all other merge requests from fork repositories will be treated as untrusted. Note that if credentials used by Jenkins for scanning the project does not have permission to query the list of contributors to the origin project then only the origin account will be treated as trusted - i.e. this will fall back to Nobody.
Trusted Members
Merge requests forks will be treated as trusted if and only if the fork owner has either Developer or Maintainer or Owner Access Level in the origin project. This is the recommended policy.
Everyone
All merge requests from forks will be treated as trusted. NOTE: this option can be dangerous if used on a public project hosted on a GitLab instance.
java.lang.UnsupportedOperationException: do not know how to categorize attributes of type jenkins.scm.api.trait.SCMHeadAuthority<? super io.jenkins.plugins.gitlabbranchsource.GitLabSCMSourceRequest, ? extends jenkins.scm.api.mixin.ChangeRequestSCMHead2, ? extends jenkins.scm.api.SCMRevision>
buildMRForksNotMirror (optional)
Add discovery of merge requests where the origin project is a fork of a certain project, but the target project is not the original forked project. To be used in case one has a GitLab project which is a fork of another project from another team, in order to isolate artefacts and allow an MR flow. This means using MRs inside that fork from branches in the fork back to the fork's default branch. (Implements https://github.com/jenkinsci/gitlab-branch-source-plugin/issues/167)
Type:boolean
gitHubForkDiscovery
Discovers pull requests where the origin repository is a fork of the target repository.
strategyId
Determines how pull requests are discovered:
Merging the pull request with the current target branch revision
Discover each pull request once with the discovered revision corresponding to the result of merging with the current revision of the target branch. Note that pushes to the target branch will result in new pull request builds.
The current pull request revision
Discover each pull request once with the discovered revision corresponding to the pull request head revision without merging.
Both the current pull request revision and the pull request merged with the current target branch revision
Discover each pull request twice. The first discovered revision corresponds to the result of merging with the current revision of the target branch in each scan. The second parallel discovered revision corresponds to the pull request head revision without merging.
Type:int
trust

One of the great powers of pull requests is that anyone with read access to a repository can fork it, commit some changes to their fork and then create a pull request against the original repository with their changes. There are some files stored in source control that are important. For example, a Jenkinsfile may contain configuration details to sandbox pull requests in order to mitigate against malicious pull requests. In order to protect against a malicious pull request itself modifying the Jenkinsfile to remove the protections, you can define the trust policy for pull requests from forks.

Other plugins can extend the available trust policies. The default policies are:

Nobody
Pull requests from forks will all be treated as untrusted. This means that where Jenkins requires a trusted file (e.g. Jenkinsfile) the contents of that file will be retrieved from the target branch on the origin repository and not from the pull request branch on the fork repository.
Collaborators
Pull requests from collaborators to the origin repository will be treated as trusted, all other pull requests from fork repositories will be treated as untrusted. Note that if credentials used by Jenkins for scanning the repository does not have permission to query the list of collaborators to the origin repository then only the origin account will be treated as trusted - i.e. this will fall back to Nobody. NOTE: all collaborators are trusted, even if they are only members of a team with read permission.
Everyone
All pull requests from forks will be treated as trusted. NOTE: this option can be dangerous if used on a public repository hosted on GitHub.
From users with Admin or Write permission
Pull requests forks will be treated as trusted if and only if the fork owner has either Admin or Write permissions on the origin repository. This is the recommended policy. Note that this strategy requires the Review a user's permission level API, as a result on GitHub Enterprise Server versions before 2.12 this is the same as trusting Nobody.
Nested choice of objects
gitHubTrustContributors
gitHubTrustEveryone
gitHubTrustNobody
gitHubTrustPermissions
browser
browser
Nested choice of objects
assembla
repoUrl
Specify the root URL serving this repository (such as https://www.assembla.com/code/PROJECT/git/).
Type:String
bitbucketServer
repoUrl
Specify the Bitbucket Server root URL for this repository (such as https://bitbucket:7990/OWNER/REPO/).
Type:String
bitbucket
repoUrl
Specify the root URL serving this repository (such as https://bitbucket.org/OWNER/REPO/).
Type:String
cgit
repoUrl
Specify the root URL serving this repository (such as https://cgit.example.com:port/group/REPO/).
Type:String
fisheye
repoUrl
Specify the URL of this repository in FishEye (such as https://fisheye.example.com/browse/project/).
Type:String
gitblit
repoUrl
Specify the root URL serving this repository.
Type:String
projectName
Specify the name of the project in GitBlit.
Type:String
gitLab
repoUrl
Specify the root URL serving this repository (such as https://gitlab.com/username/repository/).
Type:String
version (optional)
Specify the major and minor version of GitLab you use (such as 9.1). If you don't specify a version, a modern version of GitLab (>= 8.0) is assumed.
Type:String
gitLabBrowser
Specify the HTTP URL for this project's GitLab page so that links to changes can be automatically generated by Jenkins. The URL needs to include the owner and project. If the GitLab server is https://gitLab.example.com then the URL for bob's skunkworks project might be https://gitLab.example.com/bob/skunkworks.
projectUrl
Specify the HTTP URL for this project's GitLab page. The URL needs to include the owner and project so, for example, if the GitLab server is https://gitLab.example.com then the URL for bob's skunkworks project might be https://gitLab.example.com/bob/skunkworks
Type:String
gitList
repoUrl
Specify the root URL serving this repository (such as https://gitlist.example.com/repo/).
Type:String
gitWeb
repoUrl
Specify the root URL serving this repository (such as https://github.com/jenkinsci/jenkins.git).
Type:String
github
repoUrl
Specify the HTTP URL for this repository's GitHub page (such as https://github.com/jquery/jquery).
Type:String
gitiles
repoUrl
Specify the root URL serving this repository (such as https://gwt.googlesource.com/gwt/).
Type:String
$class: 'GitoriousWeb'
repoUrl
Specify the root URL serving this repository (such as https://gitorious.org/gitorious/mainline).
Type:String
gogs
repoUrl
Specify the root URL serving this repository (such as https://gogs.example.com/username/some-repo-url.git).
Type:String
kiln
repoUrl
Specify the root URL serving this repository (such as https://khanacademy.kilnhg.com/Code/Website/Group/webapp).
Type:String
phabricator
repoUrl
Specify the phabricator instance root URL (such as https://phabricator.example.com).
Type:String
repo
Specify the repository name in phabricator (such as the foo part of phabricator.example.com/diffusion/foo/browse).
Type:String
redmine
repoUrl
Specify the root URL serving this repository (such as https://redmine.example.com/PATH/projects/PROJECT/repository).
Type:String
rhodeCode
repoUrl
Specify the HTTP URL for this repository's RhodeCode page (such as https://rhodecode.example.com/projects/PROJECT/repos/REPO/).
Type:String
$class: 'Stash'
repoUrl
Specify the HTTP URL for this repository's Stash page (such as https://stash.example.com/projects/PROJECT/repos/REPO/).
Type:String
teamFoundation
repoUrl
Either the name of the remote whose URL should be used, or the URL of this module in TFS (such as https://tfs.example.com/tfs/PROJECT/_git/REPO/). If empty (default), the URL of the "origin" repository is used.

If TFS is also used as the repository server, this can usually be left blank.

Type:String
viewgit
repoUrl
Specify the root URL serving this repository (such as https://git.example.com/viewgit/).
Type:String
projectName
Specify the name of the project in ViewGit (e.g. scripts, scuttle etc. from https://code.fealdia.org/viewgit/).
Type:String
lfs
gitlabAvatar
disableProjectAvatar (optional)
Due to a GitLab bug, sometimes it is not possible to GitLab API to fetch GitLab Avatar for private projects or when the api doesn't have token access. You may choose to skip avatar for projects if you want to avoid broken or self generated avatars.
Type:boolean
gitlabMarkUnstableAsSuccess
markUnstableAsSuccess (optional)
Type:boolean
gitlabSkipNotifications
gitTool
gitTool
Type:String
gitLabHookRegistration
webHookMode
Type:String
systemHookMode
Type:String
gitHubIgnoreDraftPullRequestFilter
ignoreOnPush
localBranch
logComment
logSuccess (optional)
Sometimes the user doesn't want to log the builds that succeeded. The trait only enable logging of failed/aborted builds by default. Select this option to include logging of successful builds as well.
Type:boolean
sudoUser (optional)
Enter a sudo username of the user you want to comment as on GitLab Server. Remember the token specified should have api and sudo access both (which can only be created by your GitLab Server Admin). It is recommended to create a dummy user in your GitLab Server with an appropriate username like `jenkinsadmin` etc. Leave empty if you want use the owner of the project as the commenter.
Type:String
multiBranchProjectDisplayNaming
Some branch source plugins provide additional information about discovered branches like a title or subject of merge or change requests.
With this trait, that additional information can be used for the job display names.
Note: Job display name changes do not trigger builds.
displayNamingStrategy
The different strategies:
  • Job display name with fallback to name:
    Uses the branch source plugin's display name for the PR instead of the raw name
    Value for configuration-as-code: OBJECT_DISPLAY_NAME

  • Name and, if available, display name:
    Joins the raw name and the branch source plugin's display name
    Value for configuration-as-code: RAW_AND_OBJECT_DISPLAY_NAME

Values:
OBJECT_DISPLAY_NAME
RAW_AND_OBJECT_DISPLAY_NAME
gitLabOriginDiscovery
Discovers merge requests where the origin project is the same as the target project.
strategyId
Determines how merge requests are discovered:
Merging the merge request with the current target branch revision
Discover each merge request once with the discovered revision corresponding to the result of merging with the current revision of the target branch
The current merge request revision
Discover each merge request once with the discovered revision corresponding to the merge request head revision without merging
Both the current merge request revision and the merge request merged with the current target branch revision
Discover each merge request twice. The first discovered revision corresponds to the result of merging with the current revision of the target branch in each scan. The second parallel discovered revision corresponds to the merge request head revision without merging
Type:int
gitHubPullRequestDiscovery
Discovers pull requests where the origin repository is the same as the target repository.
strategyId
Determines how pull requests are discovered:
Merging the pull request with the current target branch revision
Discover each pull request once with the discovered revision corresponding to the result of merging with the current revision of the target branch. Note that pushes to the target branch will result in new pull request builds.
The current pull request revision
Discover each pull request once with the discovered revision corresponding to the pull request head revision without merging.
Both the current pull request revision and the pull request merged with the current target branch revision
Discover each pull request twice. The first discovered revision corresponds to the result of merging with the current revision of the target branch in each scan. The second parallel discovered revision corresponds to the pull request head revision without merging.
Type:int
pruneStaleBranch
pruneStaleTag
refSpecs
templates
Array/List:
Nested object
value
A ref spec to fetch. Any occurrences of @{remote} will be replaced by the remote name (which defaults to origin) before use.
Type:String
headRegexFilter
regex
A Java regular expression to restrict the names. Names that do not match the supplied regular expression will be ignored.
NOTE: this filter will be applied to all branch like things, including change requests
Type:String
remoteName
remoteName
Type:String
sparseCheckoutPaths
extension
Nested object

Specify the paths that you'd like to sparse checkout. This may be used for saving space (Think about a reference repository). Be sure to use a recent version of Git, at least above 1.7.10

sparseCheckoutPaths
Array/List:
Nested object
path
Type:String
submoduleOption
extension
submodule
depth (optional)
Set shallow clone depth, so that git will only download recent history of the project, saving time and disk space when you just want to access the latest commits of a repository.
Type:int
disableSubmodules (optional)
By disabling support for submodules you can still keep using basic git plugin functionality and just have Jenkins to ignore submodules completely as if they didn't exist.
Type:boolean
parentCredentials (optional)
Use credentials from the default remote of the parent project.
Type:boolean
recursiveSubmodules (optional)
Retrieve all submodules recursively (uses '--recursive' option which requires git>=1.6.5)
Type:boolean
reference (optional)
Specify a folder containing a repository that will be used by Git as a reference during clone operations.
This option will be ignored if the folder is not available on the controller or agent where the clone is being executed.
To prepare a reference folder with multiple subprojects, create a bare git repository and add all the remote urls then perform a fetch:
  git init --bare
  git remote add SubProject1 https://gitrepo.com/subproject1
  git remote add SubProject2 https://gitrepo.com/subproject2
  git fetch --all
  
Type:String
shallow (optional)
Perform shallow clone, so that git will not download the history of the project, saving time and disk space when you just want to access the latest version of a repository.
Type:boolean
threads (optional)
Specify the number of threads that will be used to update submodules.
If unspecified, the command line git default thread count is used.
Type:int
timeout (optional)
Specify a timeout (in minutes) for submodules operations.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
trackingSubmodules (optional)
Retrieve the tip of the configured branch in .gitmodules (Uses '--remote' option which requires git>=1.8.2)
Type:boolean
mrTriggerComment
commentBody
Add comment body you want to use to instruct Jenkins CI to rebuild the MR
Type:String
onlyTrustedMembersCanTrigger
Type:boolean
userIdentity
extension
Nested object
name

If given, "GIT_COMMITTER_NAME=[this]" and "GIT_AUTHOR_NAME=[this]" are set for builds. This overrides whatever is in the global settings.

Type:String
email

If given, "GIT_COMMITTER_EMAIL=[this]" and "GIT_AUTHOR_EMAIL=[this]" are set for builds. This overrides whatever is in the global settings.

Type:String
WebhookListenerBuildConditionsTrait
alwaysBuildMROpen (optional)
Type:boolean
alwaysBuildMRReOpen (optional)
Type:boolean
alwaysIgnoreMRApproval (optional)
Type:boolean
alwaysIgnoreMRApproved (optional)
Type:boolean
alwaysIgnoreMRUnApproval (optional)
Type:boolean
alwaysIgnoreMRUnApproved (optional)
Type:boolean
alwaysIgnoreMRWorkInProgress (optional)
Type:boolean
alwaysIgnoreNonCodeRelatedUpdates (optional)
GitLab will send a webhook to Jenkins when there are updates to the MR including title changes, labels removed/added, etc. Enabling this option will prevent a build running if the cause was one of these updates. Note: these settings do not have any impact on build from comment settings.
Type:boolean
headWildcardFilter
includes
Space-separated list of name patterns to consider. You may use * as a wildcard; for example: master release*
NOTE: this filter will be applied to all branch like things, including change requests
Type:String
excludes
Space-separated list of name patterns to ignore even if matched by the includes list. For example: release alpha-* beta-*
NOTE: this filter will be applied to all branch like things, including change requests
Type:String
$class: 'WipeWorkspaceTrait'
gitLabBranchDiscovery
Discovers branches on the repository.
strategyId
Determines which branches are discovered.
Only branches that are not also filed as MRs
If you are discovering origin merge requests, it may not make sense to discover the same changes both as a merge request and as a branch.
Only branches that are also filed as MRs
This option exists to preserve legacy behaviour when upgrading from older versions of the plugin. NOTE: If you have an actual use case for this option please file a merge request against this text.
All branches
Ignores whether the branch is also filed as a merge request and instead discovers all branches on the origin project.
Type:int
gitLabSshCheckout
By default the discovered branches / merge requests will all use the same username / password credentials that were used for discovery when checking out sources. This means that the checkout will be using the https:// protocol for the Git repository.

This behaviour allows you to select the SSH private key to be used for checking out sources, which will consequently force the checkout to use the ssh:// protocol.

credentialsId
Credentials used to check out sources. Must be a SSH key based credential.
Type:String
gitLabTagDiscovery
gitBranchDiscovery
Discovers branches on the repository.
gitTagDiscovery
Discovers tags on the repository.
gitHubBranchDiscovery
Discovers branches on the repository.
strategyId
Determines which branches are discovered.
Exclude branches that are also filed as PRs
If you are discovering origin pull requests, you may not want to also build the source branches for those pull requests.
Only branches that are also filed as PRs
Similar to discovering origin pull requests, but discovers the branch rather than the pull request. This means env.GIT_BRANCH will be set to the branch name rather than PR-#. Also, status notifications for these builds will only be applied to the commit and not to the pull request.
All branches
Ignores whether the branch is also filed as a pull request and instead discovers all branches on the origin repository.
Type:int
gitHubSshCheckout
By default the discovered branches / pull requests will all use the same username / password credentials that were used for discovery when checking out sources. This means that the checkout will be using the https:// protocol for the Git repository.

This behaviour allows you to select the SSH private key to be used for checking out sources, which will consequently force the checkout to use the ssh:// protocol.

credentialsId
Credentials used to check out sources. Must be a SSH key based credential.
Type:String
gitHubTagDiscovery
Discovers tags on the repository.
fromScm
name
The name of the SCM head/trunk/branch/tag that this source provides.
Type:String
scm
Nested choice of objects
scmGit

The git plugin provides fundamental git operations for Jenkins projects. It can poll, fetch, checkout, and merge contents of git repositories.

The git plugin provides an SCM implementation to be used with the Pipeline SCM checkout step. The Pipeline Syntax Snippet Generator guides the user to select git plugin checkout options and provides online help for each of the options.

Use the Pipeline Snippet Generator to generate a sample pipeline script for the checkout step. Examples of the checkout step include:

See the argument descriptions for more details.

The checkout step provides access to all the Pipeline capabilities provided by the git plugin:

checkout scmGit(userRemoteConfigs: [
                    [ url: 'https://github.com/jenkinsci/git-plugin' ]
                ])


NOTE: The checkout step is the preferred SCM checkout method. For simpler cases that do not require all the capabilities of the git plugin, the git step can also be used.

Use the Pipeline Snippet Generator to generate a sample pipeline script for the checkout step.

The checkout step can be used in many cases where the git step cannot be used. Refer to the git plugin documentation for detailed descriptions of options available to the checkout step. For example, the checkout step supports:

  • SHA-1 checkout
  • Tag checkout
  • Submodule checkout
  • Sparse checkout
  • Large file checkout (LFS)
  • Reference repositories
  • Branch merges
  • Repository tagging
  • Custom refspecs
  • Timeout configuration
  • Changelog calculation against a non-default reference
  • Stale branch pruning


Example: Checkout step with defaults

Checkout from the git plugin source repository using https protocol, no credentials, and the master branch.

The Pipeline Snippet Generator generates this example:

checkout scmGit(userRemoteConfigs: [
                    [ url: 'https://github.com/jenkinsci/git-plugin' ]
                ])

Example: Checkout step with https and a specific branch

Checkout from the Jenkins source repository using https protocol, no credentials, and a specific branch (stable-2.289).

The Pipeline Snippet Generator generates this example:

checkout scmGit(branches: [[name: 'stable-2.289']],
                userRemoteConfigs: [
                    [ url: 'https://github.com/jenkinsci/jenkins.git' ]
                ])

Example: Checkout step with ssh and a private key credential

Checkout from the git client plugin source repository using ssh protocol, private key credentials, and the master branch. The credential must be a private key credential if the remote git repository is accessed with the ssh protocol. The credential must be a username / password credential if the remote git repository is accessed with http or https protocol.

The Pipeline Snippet Generator generates this example:

checkout changelog: false,
         scm: scmGit(userRemoteConfigs: [
                         [ credentialsId: 'my-private-key-credential-id',
                           url: 'git@github.com:jenkinsci/git-client-plugin.git' ]
                         ])

Example: Checkout step with https and changelog disabled

Checkout from the Jenkins source repository using https protocol, no credentials, the master branch, and changelog calculation disabled. If changelog is false, then the changelog will not be computed for this job. If changelog is true or is not set, then the changelog will be computed. See the workflow scm step documentation for more changelog details.

The Pipeline Snippet Generator generates this example:

checkout changelog: false,
         scmGit(userRemoteConfigs: [
                    [ url: 'https://github.com/jenkinsci/credentials-plugin' ]
                ])

Example: Checkout step with git protocol and polling disabled

Checkout from the command line git repository using git protocol, no credentials, the master branch, and no polling for changes. If poll is false, then the remote repository will not be polled for changes. If poll is true or is not set, then the remote repository will be polled for changes. See the workflow scm step documentation for more polling details.

The Pipeline Snippet Generator generates this example:

checkout poll: false,
         scmGit(userRemoteConfigs: [
                    [ url: 'git://git.kernel.org/pub/scm/git/git.git ]
                ])


Argument Descriptions
userRemoteConfigs
Specify the repository to track. This can be a URL or a local file path. Note that for super-projects (repositories with submodules), only a local file path or a complete URL is valid. The following are examples of valid git URLs.
  • ssh://git@github.com/github/git.git
  • git@github.com:github/git.git (short notation for ssh protocol)
  • ssh://user@other.host.com/~/repos/R.git (to access the repos/R.git repository in the user's home directory)
  • https://github.com/github/git.git

If the repository is a super-project, the location from which to clone submodules is dependent on whether the repository is bare or non-bare (i.e. has a working directory).
  • If the super-project is bare, the location of the submodules will be taken from .gitmodules.
  • If the super-project is not bare, it is assumed that the repository has each of its submodules cloned and checked out appropriately. Thus, the submodules will be taken directly from a path like ${SUPER_PROJECT_URL}/${SUBMODULE}, rather than relying on information from .gitmodules.
For a local URL/path to a super-project, git rev-parse --is-bare-repository is used to detect whether the super-project is bare or not.
For a remote URL to a super-project, the ending of the URL determines whether a bare or non-bare repository is assumed:
  • If the remote URL ends with .git, a non-bare repository is assumed.
  • If the remote URL does NOT end with .git, a bare repository is assumed.
Array/List:
Nested object
url
Specify the URL or path of the git repository. This uses the same syntax as your git clone command.
Type:String
name
ID of the repository, such as origin, to uniquely identify this repository among other remote repositories. This is the same "name" that you use in your git remote command. If left empty, Jenkins will generate unique names for you.

You normally want to specify this when you have multiple remote repositories.

Type:String
refspec
A refspec controls the remote refs to be retrieved and how they map to local refs. If left blank, it will default to the normal behaviour of git fetch, which retrieves all the branch heads as remotes/REPOSITORYNAME/BRANCHNAME. This default behaviour is OK for most cases.

In other words, the default refspec is "+refs/heads/*:refs/remotes/REPOSITORYNAME/*" where REPOSITORYNAME is the value you specify in the above "name of repository" textbox.

When do you want to modify this value? A good example is when you want to just retrieve one branch. For example, +refs/heads/master:refs/remotes/origin/master would only retrieve the master branch and nothing else.

The plugin uses a default refspec for its initial fetch, unless the "Advanced Clone Option" is set to honor refspec. This keeps compatibility with previous behavior, and allows the job definition to decide if the refspec should be honored on initial clone.

Multiple refspecs can be entered by separating them with a space character. +refs/heads/master:refs/remotes/origin/master +refs/heads/develop:refs/remotes/origin/develop retrieves the master branch and the develop branch and nothing else.

See the refspec definition in Git user manual for more details.

Type:String
credentialsId
Credential used to check out sources.
Type:String
branches
List of branches to build. Jenkins jobs are most effective when each job builds only a single branch. When a single job builds multiple branches, the changelog comparisons between branches often show no changes or incorrect changes.
Array/List:
Nested object
name

Specify the branches if you'd like to track a specific branch in a repository. If left blank, all branches will be examined for changes and built.

The safest way is to use the refs/heads/<branchName> syntax. This way the expected branch is unambiguous.

If your branch name has a / in it make sure to use the full reference above. When not presented with a full path the plugin will only use the part of the string right of the last slash. Meaning foo/bar will actually match bar.

If you use a wildcard branch specifier, with a slash (e.g. release/), you'll need to specify the origin repository in the branch names to make sure changes are picked up. So e.g. origin/release/

Possible options:

  • <branchName>
    Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily the expected one. Better use refs/heads/<branchName>.
    E.g. master, feature1, ...
  • refs/heads/<branchName>
    Tracks/checks out the specified branch.
    E.g. refs/heads/master, refs/heads/feature1/master, ...
  • <remoteRepoName>/<branchName>
    Tracks/checks out the specified branch. If ambiguous the first result is taken, which is not necessarily the expected one.
    Better use refs/heads/<branchName>.
    E.g. origin/master
  • remotes/<remoteRepoName>/<branchName>
    Tracks/checks out the specified branch.
    E.g. remotes/origin/master
  • refs/remotes/<remoteRepoName>/<branchName>
    Tracks/checks out the specified branch.
    E.g. refs/remotes/origin/master
  • <tagName>
    This does not work since the tag will not be recognized as tag.
    Use refs/tags/<tagName> instead.
    E.g. git-2.3.0
  • refs/tags/<tagName>
    Tracks/checks out the specified tag.
    E.g. refs/tags/git-2.3.0
  • <commitId>
    Checks out the specified commit.
    E.g. 5062ac843f2b947733e6a3b105977056821bd352, 5062ac84, ...
  • ${ENV_VARIABLE}
    It is also possible to use environment variables. In this case the variables are evaluated and the result is used as described above.
    E.g. ${TREEISH}, refs/tags/${TAGNAME}, ...
  • <Wildcards>
    The syntax is of the form: REPOSITORYNAME/BRANCH. In addition, BRANCH is recognized as a shorthand of */BRANCH, '*' is recognized as a wildcard, and '**' is recognized as wildcard that includes the separator '/'. Therefore, origin/branches* would match origin/branches-foo but not origin/branches/foo, while origin/branches** would match both origin/branches-foo and origin/branches/foo.
  • :<regular expression>
    The syntax is of the form: :regexp. Regular expression syntax in branches to build will only build those branches whose names match the regular expression.
    Examples:
    • :^(?!(origin/prefix)).*
      • matches: origin or origin/master or origin/feature
      • does not match: origin/prefix or origin/prefix_123 or origin/prefix-abc
    • :origin/release-\d{8}
      • matches: origin/release-20150101
      • does not match: origin/release-2015010 or origin/release-201501011 or origin/release-20150101-something
    • :^(?!origin/master$|origin/develop$).*
      • matches: origin/branch1 or origin/branch-2 or origin/master123 or origin/develop-123
      • does not match: origin/master or origin/develop

Type:String
browser
Defines the repository browser that displays changes detected by the git plugin.
Nested choice of objects
assembla
repoUrl
Specify the root URL serving this repository (such as https://www.assembla.com/code/PROJECT/git/).
Type:String
bitbucketServer
repoUrl
Specify the Bitbucket Server root URL for this repository (such as https://bitbucket:7990/OWNER/REPO/).
Type:String
bitbucket
repoUrl
Specify the root URL serving this repository (such as https://bitbucket.org/OWNER/REPO/).
Type:String
cgit
repoUrl
Specify the root URL serving this repository (such as https://cgit.example.com:port/group/REPO/).
Type:String
fisheye
repoUrl
Specify the URL of this repository in FishEye (such as https://fisheye.example.com/browse/project/).
Type:String
gitblit
repoUrl
Specify the root URL serving this repository.
Type:String
projectName
Specify the name of the project in GitBlit.
Type:String
gitLab
repoUrl
Specify the root URL serving this repository (such as https://gitlab.com/username/repository/).
Type:String
version (optional)
Specify the major and minor version of GitLab you use (such as 9.1). If you don't specify a version, a modern version of GitLab (>= 8.0) is assumed.
Type:String
gitLabBrowser
Specify the HTTP URL for this project's GitLab page so that links to changes can be automatically generated by Jenkins. The URL needs to include the owner and project. If the GitLab server is https://gitLab.example.com then the URL for bob's skunkworks project might be https://gitLab.example.com/bob/skunkworks.
projectUrl
Specify the HTTP URL for this project's GitLab page. The URL needs to include the owner and project so, for example, if the GitLab server is https://gitLab.example.com then the URL for bob's skunkworks project might be https://gitLab.example.com/bob/skunkworks
Type:String
gitList
repoUrl
Specify the root URL serving this repository (such as https://gitlist.example.com/repo/).
Type:String
gitWeb
repoUrl
Specify the root URL serving this repository (such as https://github.com/jenkinsci/jenkins.git).
Type:String
github
repoUrl
Specify the HTTP URL for this repository's GitHub page (such as https://github.com/jquery/jquery).
Type:String
gitiles
repoUrl
Specify the root URL serving this repository (such as https://gwt.googlesource.com/gwt/).
Type:String
$class: 'GitoriousWeb'
repoUrl
Specify the root URL serving this repository (such as https://gitorious.org/gitorious/mainline).
Type:String
gogs
repoUrl
Specify the root URL serving this repository (such as https://gogs.example.com/username/some-repo-url.git).
Type:String
kiln
repoUrl
Specify the root URL serving this repository (such as https://khanacademy.kilnhg.com/Code/Website/Group/webapp).
Type:String
phabricator
repoUrl
Specify the phabricator instance root URL (such as https://phabricator.example.com).
Type:String
repo
Specify the repository name in phabricator (such as the foo part of phabricator.example.com/diffusion/foo/browse).
Type:String
redmine
repoUrl
Specify the root URL serving this repository (such as https://redmine.example.com/PATH/projects/PROJECT/repository).
Type:String
rhodeCode
repoUrl
Specify the HTTP URL for this repository's RhodeCode page (such as https://rhodecode.example.com/projects/PROJECT/repos/REPO/).
Type:String
$class: 'Stash'
repoUrl
Specify the HTTP URL for this repository's Stash page (such as https://stash.example.com/projects/PROJECT/repos/REPO/).
Type:String
teamFoundation
repoUrl
Either the name of the remote whose URL should be used, or the URL of this module in TFS (such as https://tfs.example.com/tfs/PROJECT/_git/REPO/). If empty (default), the URL of the "origin" repository is used.

If TFS is also used as the repository server, this can usually be left blank.

Type:String
viewgit
repoUrl
Specify the root URL serving this repository (such as https://git.example.com/viewgit/).
Type:String
projectName
Specify the name of the project in ViewGit (e.g. scripts, scuttle etc. from https://code.fealdia.org/viewgit/).
Type:String
gitTool

Name of the git tool to be used for this job. Git tool names are defined in "Global Tool Configuration".

Type:String
extensions

Extensions add new behavior or modify existing plugin behavior for different uses. Extensions help users more precisely tune plugin behavior to meet their needs.

Extensions include:

  • Clone extensions modify the git operations that retrieve remote changes into the agent workspace. The extensions can adjust the amount of history retrieved, how long the retrieval is allowed to run, and other retrieval details.
  • Checkout extensions modify the git operations that place files in the workspace from the git repository on the agent. The extensions can adjust the maximum duration of the checkout operation, the use and behavior of git submodules, the location of the workspace on the disc, and more.
  • Changelog extensions adapt the source code difference calculations for different cases.
  • Tagging extensions allow the plugin to apply tags in the current workspace.
  • Build initiation extensions control the conditions that start a build. They can ignore notifications of a change or force a deeper evaluation of the commits when polling.
  • Merge extensions can optionally merge changes from other branches into the current branch of the agent workspace. They control the source branch for the merge and the options applied to the merge.

Array/List:
Nested choice of objects
authorInChangelog
The default behavior is to use the Git commit's "Committer" value in Jenkins' build changesets. If this option is selected, the Git commit's "Author" value would be used instead.
$class: 'BuildChooserSetting'
When you are interested in using a job to build multiple heads (most typically multiple branches), you can choose how Jenkins choose what branches to build in what order.

This extension point in Jenkins is used by many other plugins to control the job to build specific commits. When you activate those plugins, you may see them installing a custom strategy here.

buildChooser
Nested choice of objects
$class: 'AncestryBuildChooser'
maximumAgeInDays
Type:int
ancestorCommitSha1
Type:String
$class: 'DefaultBuildChooser'
$class: 'InverseBuildChooser'
buildSingleRevisionOnly
Disable scheduling for multiple candidate revisions.
If we have 3 branches:
----A--.---.--- B
         \-----C
jenkins would try to build (B) and (C).
This behaviour disables this and only builds one of them.
It is helpful to reduce the load of the Jenkins infrastructure when the SCM system like Bitbucket or GitHub should decide what commits to build.
changelogToBranch
This method calculates the changelog against the specified branch.
options
changelogBase
compareRemote
Name of the repository, such as origin, that contains the branch you specify below.
Type:String
compareTarget
The name of the branch within the named repository to compare against.
Type:String
checkoutOption
timeout
Specify a timeout (in minutes) for checkout.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
cleanBeforeCheckout
Clean up the workspace before every checkout by deleting all untracked files and directories, including those which are specified in .gitignore. It also resets all tracked files to their versioned state. This ensures that the workspace is in the same state as if you cloned and checked out in a brand-new empty directory, and ensures that your build is not affected by the files generated by the previous build.
deleteUntrackedNestedRepositories (optional)
Deletes untracked submodules and any other subdirectories which contain .git directories.
Type:boolean
cleanAfterCheckout
Clean up the workspace after every checkout by deleting all untracked files and directories, including those which are specified in .gitignore. It also resets all tracked files to their versioned state. This ensures that the workspace is in the same state as if you cloned and checked out in a brand-new empty directory, and ensures that your build is not affected by the files generated by the previous build.
deleteUntrackedNestedRepositories (optional)
Deletes untracked submodules and any other subdirectories which contain .git directories.
Type:boolean
cloneOption
shallow
Perform shallow clone, so that git will not download the history of the project, saving time and disk space when you just want to access the latest version of a repository.
Type:boolean
noTags
Deselect this to perform a clone without tags, saving time and disk space when you just want to access what is specified by the refspec.
Type:boolean
reference
Specify a folder containing a repository that will be used by Git as a reference during clone operations.
This option will be ignored if the folder is not available on the controller or agent where the clone is being executed.
Type:String
timeout
Specify a timeout (in minutes) for clone and fetch operations.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
depth (optional)
Set shallow clone depth, so that git will only download recent history of the project, saving time and disk space when you just want to access the latest commits of a repository.
Type:int
honorRefspec (optional)
Perform initial clone using the refspec defined for the repository. This can save time, data transfer and disk space when you only need to access the references specified by the refspec.
Type:boolean
$class: 'DisableRemotePoll'
Git plugin uses git ls-remote polling mechanism by default when configured with a single branch (no wildcards!). This compare the latest built commit SHA with the remote branch without cloning a local copy of the repo.

If you don't want to / can't use this.

If this option is selected, polling will require a workspace and might trigger unwanted builds (see JENKINS-10131).
lfs
Enable git large file support for the workspace by pulling large files after the checkout completes. Requires that the controller and each agent performing an LFS checkout have installed `git lfs`.
$class: 'IgnoreNotifyCommit'
If checked, this repository will be ignored when the notifyCommit-URL is accessed regardless of if the repository matches or not.
localBranch
If given, checkout the revision to build as HEAD on this branch.

If selected, and its value is an empty string or "**", then the branch name is computed from the remote branch without the origin. In that case, a remote branch origin/master will be checked out to a local branch named master, and a remote branch origin/develop/new-feature will be checked out to a local branch named develop/newfeature.

Please note that this has not been tested with submodules.

localBranch
Type:String
$class: 'MessageExclusion'
excludedMessage
If set, and Jenkins is set to poll for changes, Jenkins will ignore any revisions committed with message matched to Pattern when determining if a build needs to be triggered. This can be used to exclude commits done by the build itself from triggering another build, assuming the build server commits the change with a distinct message.

Exclusion uses Pattern matching

.*\[maven-release-plugin\].*
The example above illustrates that if only revisions with "[maven-release-plugin]" message in first comment line have been committed to the SCM a build will not occur.

You can create more complex patterns using embedded flag expressions.

(?s).*FOO.*
This example will search FOO message in all comment lines.
Type:String
$class: 'PathRestriction'
If set, and Jenkins is set to poll for changes, Jenkins will pay attention to included and/or excluded files and/or folders when determining if a build needs to be triggered.

Using this behaviour will preclude the faster git ls-remote polling mechanism, forcing polling to require a workspace thus sometimes triggering unwanted builds, as if you had selected the Force polling using workspace extension as well.

includedRegions
Each inclusion uses java regular expression pattern matching, and must be separated by a new line. An empty list implies that everything is included.

    myapp/src/main/web/.*\.html
    myapp/src/main/web/.*\.jpeg
    myapp/src/main/web/.*\.gif
  
The example above illustrates that a build will only occur, if html/jpeg/gif files have been committed to the SCM. Exclusions take precedence over inclusions, if there is an overlap between included and excluded regions.
Type:String
excludedRegions
Each exclusion uses java regular expression pattern matching, and must be separated by a new line.

    myapp/src/main/web/.*\.html
    myapp/src/main/web/.*\.jpeg
    myapp/src/main/web/.*\.gif
  
The example above illustrates that if only html/jpeg/gif files have been committed to the SCM a build will not occur.
Type:String
perBuildTag
Create a tag in the workspace for every build to unambiguously mark the commit that was built. You can combine this with Git publisher to push the tags to the remote repository.
$class: 'PreBuildMerge'
These options allow you to perform a merge to a particular branch before building. For example, you could specify an integration branch to be built, and to merge to master. In this scenario, on every change of integration, Jenkins will perform a merge with the master branch, and try to perform a build if the merge is successful. It then may push the merge back to the remote repository if the Git Push post-build action is selected.
options
Nested object
mergeTarget
The name of the branch within the named repository to merge to, such as master.
Type:String
fastForwardMode (optional)
Merge fast-forward mode selection.
The default, --ff, gracefully falls back to a merge commit when required.
For more information, see the Git Merge Documentation
Values:
FF
FF_ONLY
NO_FF
mergeRemote (optional)
Name of the repository, such as origin, that contains the branch you specify below. If left blank, it'll default to the name of the first repository configured above.
Type:String
mergeStrategy (optional)
Merge strategy selection. This feature is not fully implemented in JGIT.
Values:
DEFAULT
RESOLVE
RECURSIVE
OCTOPUS
OURS
SUBTREE
RECURSIVE_THEIRS
pruneStaleBranch
Run "git remote prune" for each remote, to prune obsolete local branches.
pruneTags
pruneTags
Type:boolean
$class: 'RelativeTargetDirectory'
relativeTargetDir
Specify a local directory (relative to the workspace root) where the Git repository will be checked out. If left empty, the workspace root itself will be used.

This extension should not be used in Jenkins Pipeline (either declarative or scripted). Jenkins Pipeline already provides standard techniques for checkout to a subdirectory. Use ws and dir in Jenkins Pipeline rather than this extension.

Type:String
$class: 'ScmName'

Unique name for this SCM. Needed when using Git within the Multi SCM plugin.

name
Type:String
$class: 'SparseCheckoutPaths'

Specify the paths that you'd like to sparse checkout. This may be used for saving space (Think about a reference repository). Be sure to use a recent version of Git, at least above 1.7.10

sparseCheckoutPaths
Array/List:
Nested object
path
Type:String
submodule
depth (optional)
Set shallow clone depth, so that git will only download recent history of the project, saving time and disk space when you just want to access the latest commits of a repository.
Type:int
disableSubmodules (optional)
By disabling support for submodules you can still keep using basic git plugin functionality and just have Jenkins to ignore submodules completely as if they didn't exist.
Type:boolean
parentCredentials (optional)
Use credentials from the default remote of the parent project.
Type:boolean
recursiveSubmodules (optional)
Retrieve all submodules recursively (uses '--recursive' option which requires git>=1.6.5)
Type:boolean
reference (optional)
Specify a folder containing a repository that will be used by Git as a reference during clone operations.
This option will be ignored if the folder is not available on the controller or agent where the clone is being executed.
To prepare a reference folder with multiple subprojects, create a bare git repository and add all the remote urls then perform a fetch:
  git init --bare
  git remote add SubProject1 https://gitrepo.com/subproject1
  git remote add SubProject2 https://gitrepo.com/subproject2
  git fetch --all
  
Type:String
shallow (optional)
Perform shallow clone, so that git will not download the history of the project, saving time and disk space when you just want to access the latest version of a repository.
Type:boolean
threads (optional)
Specify the number of threads that will be used to update submodules.
If unspecified, the command line git default thread count is used.
Type:int
timeout (optional)
Specify a timeout (in minutes) for submodules operations.
This option overrides the default timeout of 10 minutes.
You can change the global git timeout via the property org.jenkinsci.plugins.gitclient.Git.timeOut (see JENKINS-11286). Note that property should be set on both controller and agent to have effect (see JENKINS-22547).
Type:int
trackingSubmodules (optional)
Retrieve the tip of the configured branch in .gitmodules (Uses '--remote' option which requires git>=1.8.2)
Type:boolean
$class: 'UserExclusion'
excludedUsers
If set, and Jenkins is set to poll for changes, Jenkins will ignore any revisions committed by users in this list when determining if a build needs to be triggered. This can be used to exclude commits done by the build itself from triggering another build, assuming the build server commits the change with a distinct SCM user.

Using this behaviour will preclude the faster git ls-remote polling mechanism, forcing polling to require a workspace thus sometimes triggering unwanted builds, as if you had selected the Force polling using workspace extension as well.

Each exclusion uses exact string comparison and must be separated by a new line. User names are only excluded if they exactly match one of the names in this list.

auto_build_user
The example above illustrates that if only revisions by "auto_build_user" have been committed to the SCM a build will not occur.
Type:String
$class: 'UserIdentity'
name

If given, "GIT_COMMITTER_NAME=[this]" and "GIT_AUTHOR_NAME=[this]" are set for builds. This overrides whatever is in the global settings.

Type:String
email

If given, "GIT_COMMITTER_EMAIL=[this]" and "GIT_AUTHOR_EMAIL=[this]" are set for builds. This overrides whatever is in the global settings.

Type:String
$class: 'WipeWorkspace'
Delete the contents of the workspace before building, ensuring a fully fresh workspace.
doGenerateSubmoduleConfigurations (optional)

Removed facility that was intended to test combinations of git submodule versions. Removed in git plugin 4.6.0. Ignores the user provided value and always uses false as its value.

Type:boolean
submoduleCfg (optional)

Removed facility that was intended to test combinations of git submodule versions. Removed in git plugin 4.6.0. Ignores the user provided value(s) and always uses empty values.

Array/List:
Nested object
submoduleName

Removed in git plugin 4.6.0.

Type:String
branches

Removed in git plugin 4.6.0.

Array/List:
Type:String
none
id (optional)
Type:String
targets
The branch names to try and resolve from the source, in order of preference.
Array/List:
Type:String
ignoreErrors (optional)
When selected, the step will return null in the event that no matching branch can be resolved.
Type:boolean
retry: Retry the body up to N times
Retry the block (up to N times) if any exception happens during its body execution. If an exception happens on the final attempt then it will lead to aborting the build (unless it is caught and processed somehow). User aborts of the build are not caught.
count
Type:int
conditions (optional)
Conditions under which the block should be retried. If none match, the block will fail. If there are no specified conditions, the block will always be retried except in case of user aborts.
Array/List:
Nested choice of objects
agent
Detects that a node block, or certain steps inside it such as sh, failed for reasons which are likely due to infrastructure rather than the behavior of the build. If the connection to an agent is broken or the agent is removed from the list of executors while in use (typically in response to the disappearance of underlying cloud resources), this condition will allow retry to allocate a fresh agent and try the whole block again.
kubernetesAgent
Similar to agent() (Agent errors) but tailored to agents provisioned from a Kubernetes cloud. Unlike the generic agent error condition, this will ignore certain pod termination reasons which are likely to be under the control of the Pipeline author (e.g., OOMKilled) while still allowing retry to recover after common cases of pod deletion.
handleNonKubernetes (optional)
Behave like the generic agent() (Agent errors) when applied to a non-Kubernetes agent. Useful in cases where it is hard to predict in a job definition whether a Kubernetes or other sort of agent will be used.
Type:boolean
nonresumable
The Jenkins controller was restarted while the build was running a step which cannot be resumed. Some steps like sh or input are written to survive a Jenkins restart and simply pick up where they left off when the build resumes. Others like checkout or junit normally complete promptly but cannot tolerate a restart. In case one of these steps happened to be in progress when Jenkins shut down, the resumed build will throw an error; using this condition with retry allows the step (or the whole enclosing node block) to be rerun.
scanForIssues: Scan files or the console log for warnings or issues
blameDisabled (optional)
If this option is unchecked, then the plugin automatically shows what revision and author (name and email) last modified the lines of the affected files that contain issues. If this operation slows down your build or you don't want to publish sensitive user data, you can use this option to deactivate this feature.
Type:boolean
filters (optional)
The created report of issues can be filtered afterwards. You can specify an arbitrary number of include or exclude filters. Currently, there is support for filtering issues by module name, package or namespace name, file name, category or type. Include filters will be combined with or, exclude filters with and. If no filter is defined, then all issues will be published. Filters with empty regular expression will be ignored.
Array/List:
Nested choice of objects
excludeCategory
pattern
Type:String
excludeFile
pattern
Type:String
excludeMessage
pattern
Type:String
excludeModule
pattern
Type:String
excludePackage
pattern
Type:String
excludeType
pattern
Type:String
includeCategory
pattern
Type:String
includeFile
pattern
Type:String
includeMessage
pattern
Type:String
includeModule
pattern
Type:String
includePackage
pattern
Type:String
includeType
pattern
Type:String
forensicsDisabled (optional)
Type:boolean
quiet (optional)
Type:boolean
scm (optional)
Type:String
skipPostProcessing (optional)
If this option is unchecked, then the plugin automatically resolves absolute paths, fingerprints, package and module names from the source files in the workspace. If this operation slows down your build, you can use this option to deactivate this feature.
Type:boolean
sourceCodeEncoding (optional)
In order to correctly show all your affected source code files in the detail views, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
sourceDirectories (optional)
Some plugins copy source code files to Jenkins' build folder so that these files can be rendered in the user interface together with build results (coverage, warnings, etc.). If these files are not part of the workspace of a build then Jenkins will not show them by default: otherwise sensitive files could be shown by accident. You can provide a list of additional source code directories that are allowed to be shown in Jenkins user interface here. Note, that such a directory must be an absolute path on the agent that executes the build.
Array/List:
Nested object
path
Select the path to your source code files. This plugin copies source code files to Jenkins' build folder so that these files can be rendered in the user interface together with the plugin results. If these files are referenced with relative paths then they cannot be found by the plugin. In these cases you need to specify one or more relative paths within the workspace where the plugin can locate them. Alternatively, you can also specify absolute paths if the source code files are stored outside the workspace (in a directory on the agent). All absolute paths must be additionally approved by an administrator in Jenkins' global configuration page.
Type:String
sourceDirectory (optional)
Type:String
tool (optional)
For each static analysis tool a dedicated parser or scanner will be used to read report files or produce issues in any other way. If your tool is not yet supported you can define a new Groovy based parser in Jenkins system configuration. You can reference this new parser afterwards when you select the tool 'Groovy Parser'. Additionally, you provide a new parser within a new small plug-in. If the parser is useful for other teams as well please share it and provide pull requests for the Warnings Next Generation Plug-in and the Analysis Parsers Library.
Nested choice of objects
acuCobol
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ajc
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
androidLintParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ansibleLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
aquaScanner
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
armCc
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
axivionSuite
basedir (optional)
Type:String
credentialsId (optional)
Type:String
id (optional)
Type:String
ignoreSuppressedOrJustified (optional)
Type:boolean
name (optional)
Type:String
namedFilter (optional)
Type:String
projectUrl (optional)
Type:String
bluepearl
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
brakeman
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
buckminster
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
cadence
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
cargo
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ccm
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
checkStyle
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
clair
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
clang
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
clangAnalyzer
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
clangTidy
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
cmake
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
codeAnalysis
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
codeChecker
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
codeGeneratorParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
codeNarc
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
coolflux
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
cpd
highThreshold (optional)
Type:int
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
normalThreshold (optional)
Type:int
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
cppCheck
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
cppLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
CrossCoreEmbeddedStudioParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
cssLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
dscanner
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
dart
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
detekt
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
diabC
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
docFx
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
dockerLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
doxygen
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
drMemory
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
dupFinder
highThreshold (optional)
Type:int
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
normalThreshold (optional)
Type:int
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
eclipse
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
embeddedEngineerParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
erlc
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
errorProne
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
esLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
findBugs
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
useRankAsPriority (optional)
Type:boolean
flake8
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
flawfinder
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
flexSdk
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
fxcop
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
gcc3
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
gcc
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
gendarme
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ghsMulti
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
gnat
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
gnuFortran
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
goLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
goVet
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
groovyScript
parserId
Type:String
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
grype
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
hadoLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
iar
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
iarCstat
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ibLinter
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ideaInspection
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
infer
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
intel
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
invalids
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
junitParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
java
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
javaDoc
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
jcReport
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
jsHint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
jsLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
klocWork
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
kotlin
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ktLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
mavenConsole
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
modelsim
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
metrowerksCodeWarrior
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
msBuild
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
myPy
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
nagFortran
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
oelintAdv
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
otDockerLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
taskScanner
excludePattern (optional)
Type:String
highTags (optional)
Type:String
id (optional)
Type:String
ignoreCase (optional)
Type:boolean
includePattern (optional)
You can define multiple filesets using comma as a separator, e.g. '**/*.c, **/*.h'. Basedir of the fileset is the workspace root.
Type:String
isRegularExpression (optional)
Note that the regular expression must contain two capturing groups: the first one is interpreted as tag name, the second one as message. An example of such a regular expression would be ^.*(TODO(?:[0-9]*))(.*)$.
Type:boolean
lowTags (optional)
Type:String
name (optional)
Type:String
normalTags (optional)
Type:String
owaspDependencyCheck
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
PVSStudio
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
pcLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
pep8
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
perforce
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
perlCritic
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
php
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
phpCodeSniffer
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
phpStan
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
pit
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
pmdParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
polyspaceParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
prefast
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
protoLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
puppetLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
pyDocStyle
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
pyLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
qacSourceCodeAnalyser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
qtTranslation
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
analysisParser
analysisModelId
Type:String
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
resharperInspectCode
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
revApi
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
rfLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
robocopy
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
ruboCop
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
sarif
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
scala
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
simian
highThreshold (optional)
Type:int
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
normalThreshold (optional)
Type:int
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
simulinkCheckParser
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
sonarQube
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
sphinxBuild
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
spotBugs
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
useRankAsPriority (optional)
Type:boolean
styleCop
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
styleLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
sunC
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
swiftLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
tagList
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
taskingVx
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
tiCss
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
tnsdl
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
trivy
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
tsLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
veracodePipelineScanner
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
issues
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
xlc
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
xmlLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
yamlLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
yuiCompressor
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
zptLint
id (optional)
The results of the selected tool are published using a unique ID (i.e. URL) which must not be already used by another tool in this job. This ID is used as link to the results, so choose a short and meaningful name. Allowed elements are characters, digits, dashes and underscores (more precisely, the ID must match the regular expression `\p{Alnum}[\p{Alnum}-_]*`). If you leave the ID field empty, then the built-in default ID of the registered tool will be used.
Type:String
name (optional)
You can override the display name of the tool. This name is used in details views, trend captions, and hyper links. If you leave the name field empty, then the built-in default name of the registered tool will be used.
Type:String
pattern (optional)
Type:String
reportEncoding (optional)
In order to read all characters of your reports correctly, the plugin must open these files with the correct character encoding (UTF-8, ISO-8859-1, etc.). If you leave this field empty then the default encoding of the platform will be used. This might work but is not recommended.
Type:String
skipSymbolicLinks (optional)
Skipping symbolic links is useful when the scanned directory contains links that create a recursive structure. Note that this option may not work on Windows, since symbolic links are not fully supported here.
Type:boolean
script: Run arbitrary Pipeline script
sh: Shell Script
script

Runs a Bourne shell script, typically on a Unix node. Multiple lines are accepted.

An interpreter selector may be used, for example: #!/usr/bin/perl

Otherwise the system default shell will be run, using the -xe flags (you can specify set +e and/or set +x to disable those).

Type:String
encoding (optional)
Encoding of process output. In the case of returnStdout, applies to the return value of this step; otherwise, or always for standard error, controls how text is copied to the build log. If unspecified, uses the system default encoding of the node on which the step is run. If there is any expectation that process output might include non-ASCII characters, it is best to specify the encoding explicitly. For example, if you have specific knowledge that a given process is going to be producing UTF-8 yet will be running on a node with a different system encoding (typically Windows, since every Linux distribution has defaulted to UTF-8 for a long time), you can ensure correct output by specifying: encoding: 'UTF-8'
Type:String
label (optional)
Label to be displayed in the pipeline step view and blue ocean details for the step instead of the step type. So the view is more meaningful and domain specific instead of technical.
Type:String
returnStatus (optional)
Normally, a script which exits with a nonzero status code will cause the step to fail with an exception. If this option is checked, the return value of the step will instead be the status code. You may then compare it to zero, for example.
Type:boolean
returnStdout (optional)
If checked, standard output from the task is returned as the step value as a String, rather than being printed to the build log. (Standard error, if any, will still be printed to the log.) You will often want to call .trim() on the result to strip off a trailing newline.
Type:boolean
sleep: Sleep
Simply pauses the Pipeline build until the given amount of time has expired. Equivalent to (on Unix) sh 'sleep …'. May be used to pause one branch of parallel while another proceeds.
time
The length of time for which the step will sleep.
Type:int
unit (optional)
The unit for the time parameter. Defaults to 'SECONDS' if not specified.
Values:
NANOSECONDS
MICROSECONDS
MILLISECONDS
SECONDS
MINUTES
HOURS
DAYS
sshagent: SSH Agent

node {
  sshagent (credentials: ['deploy-dev']) {
    sh 'ssh -o StrictHostKeyChecking=no -l cloudbees 192.168.1.106 uname -a'
  }
}

Multiple credentials could be passed in the array but it is not supported using Snippet Generator.

credentials
List of credentials to be used by the sshagent step. The Pipeline Syntax Snippet Generator will guide the user to select a single credential from the list of available, like this:
sshagent(credentials: ['my-credential-id']) {
    // some block
}
The step also accepts a list of credentials, like this:
sshagent(credentials: ['my-credential-id', 'my-alternate-credential', 'another-credential']) {
    // some block
}
Array/List:
Type:String
ignoreMissing (optional)
When set to true, any missing credentials will be ignored. When set to false, then the build fails if any of the required credentials cannot be resolved. Defaults to false.
Type:boolean
stage: Stage
Creates a labeled block.
name
Type:String
concurrency (optional)
Type:int
stash: Stash some files to be used later in the build
Saves a set of files for later use on any node/workspace in the same Pipeline run. By default, stashed files are discarded at the end of a pipeline run. Other plugins may change this behavior to preserve stashes for longer. For example, Declarative Pipeline includes a preserveStashes() option to allow stashes from a run to be retained and used if that run is restarted.
Stashes from one Pipeline run are not available in other runs, other Pipelines, or other jobs. If you want to persist artifacts for use outside of a single run, consider using archiveArtifacts instead. Note that the stash and unstash steps are designed for use with small files. For large data transfers, use the External Workspace Manager plugin, or use an external repository manager such as Nexus or Artifactory. This is because stashed files are archived in a compressed TAR, and with large files this demands considerable resources on the controller, particularly CPU time. There's not a hard stash size limit, but between 5-100 MB you should probably consider alternatives. If you use the Artifact Manager on S3 plugin, or another plugin with a remote atifact manager, you can use this step without affecting controller performance since stashes will be sent directly to S3 from the agent (and similarly for unstash).
name
Name of a stash. Should be a simple identifier akin to a job name.
Type:String
allowEmpty (optional)
Create stash even if no files are included. If false (default), an error is raised when the stash does not contain files.
Type:boolean
excludes (optional)
Optional set of Ant-style exclude patterns.
Use a comma separated list to add more than one expression.
If blank, no files will be excluded.
Type:String
includes (optional)
Optional set of Ant-style include patterns.
Use a comma separated list to add more than one expression.
If blank, treated like **: all files.
The current working directory is the base directory for the saved files, which will later be restored in the same relative locations, so if you want to use a subdirectory wrap this in dir.
Type:String
useDefaultExcludes (optional)
If selected, use the default excludes from Ant - see here for the list. Defaults to true.
Type:boolean
step: General Build Step

This is a special step that allows to call builders or post-build actions (as in freestyle or similar projects), in general "build steps". Just select the build step to call from the dropdown list and configure it as needed.

Note that only Pipeline-compatible steps will be shown in the list.

delegate
Nested choice of objects
archiveArtifacts
Archives the build artifacts (for example, distribution zip files or jar files) so that they can be downloaded later. Archived files will be accessible from the Jenkins webpage.
Normally, Jenkins keeps artifacts for a build as long as a build log itself is kept, but if you don't need old artifacts and would rather save disk space, you can do so.

Note that the Maven job type automatically archives any produced Maven artifacts. Any artifacts configured here will be archived on top of that. Automatic artifact archiving can be disabled under the advanced Maven options.

The Pipeline Snippet Generator generates this example when all arguments are set to true (some arguments by default are true):
archiveArtifacts artifacts: '**/*.txt',
                   allowEmptyArchive: true,
                   fingerprint: true,
                   onlyIfSuccessful: true

artifacts
You can use wildcards like 'module/dist/**/*.zip'. See the includes attribute of Ant fileset for the exact format -- except that "," ( comma ) is the only supported separator. The base directory is the workspace . You can only archive files that are located in your workspace.

Here are some examples of usage for pipeline:

  • How to archive multiple artifacts from a specific folder:
    archiveArtifacts artifacts: 'target/*.jar'

  • How to archive multiple artifacts with different patterns:
    archiveArtifacts artifacts: 'target/*.jar, target/*.war'

  • How to archive multiple nested artifacts:
    archiveArtifacts artifacts: '**/*.jar'

Type:String
allowEmptyArchive (optional)
Normally, a build fails if archiving returns zero artifacts. This option allows the archiving process to return nothing without failing the build. Instead, the build will simply throw a warning.
Type:boolean
caseSensitive (optional)
Artifact archiver uses Ant org.apache.tools.ant.DirectoryScanner which by default is case sensitive. For instance, if the job produces *.hpi files, pattern "**/*.HPI" will fail to find them.

This option can be used to disable case sensitivity. When it's unchecked, pattern "**/*.HPI" will match any *.hpi files, or pattern "**/cAsEsEnSiTiVe.jar" will match a file called caseSensitive.jar.
Type:boolean
defaultExcludes (optional)
Type:boolean
excludes (optional)
Optionally specify the 'excludes' pattern, such as "foo/bar/**/*". Use "," to set a list of patterns. A file that matches this mask will not be archived even if it matches the mask specified in 'files to archive' section.
Type:String
fingerprint (optional)
Type:boolean
followSymlinks (optional)
By disabling this option all symbolic links found in the workspace will be ignored.
Type:boolean
onlyIfSuccessful (optional)
Type:boolean
fingerprint
Jenkins can record the 'fingerprint' of files (most often jar files) to keep track of where/when those files are produced and used. When you have inter-dependent projects on Jenkins, this allows you to quickly find out answers to questions like:
  • I have foo.jar on my HDD but which build number of FOO did it come from?
  • My BAR project depends on foo.jar from the FOO project.
    • Which build of foo.jar is used in BAR #51?
    • Which build of BAR contains my bug fix to foo.jar #32?

To use this feature, all of the involved projects (not just the project in which a file is produced, but also the projects in which the file is used) need to use this and record fingerprints.

See this document for more details.

targets
Can use wildcards like module/dist/**/*.zip (see the @includes of Ant fileset for the exact format). The base directory is the workspace .
Type:String
caseSensitive (optional)
Fingerprinter uses Ant org.apache.tools.ant.DirectoryScanner which by default is case sensitive. For instance, if the job produces *.hpi files, pattern "**/*.HPI" will fail to find them.

This option can be used to disable case sensitivity. When it's unchecked, pattern "**/*.HPI" will match any *.hpi files, or pattern "**/cAsEsEnSiTiVe.jar" will match a file called caseSensitive.jar.
Type:boolean
defaultExcludes (optional)
Type:boolean
excludes (optional)
Optionally specify the 'excludes' pattern, such as "foo/bar/**/*". Use "," to set a list of patterns. A file that matches this mask will not be fingerprinted even if it matches the mask specified in 'files to fingerprint' section.
Type:String
$class: 'GhprbPullRequestMerge'
mergeComment
Comment that should show up when the merge command is sent to GitHub.
Type:String
onlyAdminsMerge
Only allow admin users to trigger a pull request merge.
Type:boolean
disallowOwnCode
Disallow a user to merge their own code.
Type:boolean
failOnNonMerge
Type:boolean
deleteOnMerge
Type:boolean
allowMergeWithoutTriggerPhrase
Allow merging even if the trigger phrase is not present. This can be used with the permitAll ("Build every pull request automatically without asking (Dangerous!).")
Type:boolean
$class: 'GitHubCommitNotifier'
This notifier will set GH commit status. This step is DEPRECATED and will be migrated to new step in one of the next major plugin releases.
Please refer to new universal step.
resultOnFailure
Type:String
statusMessage (optional)
Nested object
content
Message content that will be expanded using core variable expansion i.e. ${WORKSPACE}
and Token Macro Plugin tokens.
Type:String
$class: 'GitHubCommitStatusSetter'
Using GitHub status api sets status of the commit.
commitShaSource (optional)
Nested choice of objects
$class: 'BuildDataRevisionShaSource'
Uses data-action (located at ${build.url}/git/) to determine actual SHA.
$class: 'ManuallyEnteredShaSource'
Allows to define commit SHA manually.
sha
Allows env vars and token macro.
Type:String
contextSource (optional)
Nested choice of objects
$class: 'DefaultCommitContextSource'
Uses display name property defined in "GitHub project property" with fallback to job name.
$class: 'ManuallyEnteredCommitContextSource'
You can define context name manually.
context
Allows env vars and token macros.
Type:String
errorHandlers (optional)
Array/List:
Nested choice of objects
$class: 'ChangingBuildStatusErrorHandler'
result
Type:String
$class: 'ShallowAnyErrorHandler'
reposSource (optional)
Nested choice of objects
$class: 'AnyDefinedRepositorySource'
Any repository provided by the programmatic contributors list.
$class: 'ManuallyEnteredRepositorySource'
A manually entered repository URL.
url
A GitHub repository URL.
Type:String
statusBackrefSource (optional)
Nested choice of objects
$class: 'BuildRefBackrefSource'
Points commit status backref back to the producing build page.
$class: 'ManuallyEnteredBackrefSource'
A manually entered backref URL.
backref
A backref URL. Allows env vars and token macro.
Type:String
statusResultSource (optional)
Nested choice of objects
$class: 'ConditionalStatusResultSource'
You can define in which cases you want to publish exact state and message for the commit. You can define multiple cases. First match (starting from top) wins. If no one matches, PENDING status + warn message will be used.
results
Array/List:
Nested choice of objects
$class: 'AnyBuildResult'
message (optional)
Type:String
state (optional)
Type:String
$class: 'BetterThanOrEqualBuildResult'
message (optional)
Allows env vars and token macro.
Type:String
result (optional)
Type:String
state (optional)
Type:String
$class: 'DefaultStatusResultSource'
Writes simple message about build result and duration.
$class: 'GitHubSetCommitStatusBuilder'
contextSource (optional)
Nested choice of objects
$class: 'DefaultCommitContextSource'
Uses display name property defined in "GitHub project property" with fallback to job name.
$class: 'ManuallyEnteredCommitContextSource'
You can define context name manually.
context
Allows env vars and token macros.
Type:String
statusMessage (optional)
Nested object
content
Message content that will be expanded using core variable expansion i.e. ${WORKSPACE}
and Token Macro Plugin tokens.
Type:String
$class: 'JUnitResultArchiver'
Jenkins understands the JUnit test report XML format (which is also used by TestNG). When this option is configured, Jenkins can provide useful information about test results, such as historical test result trends, a web UI for viewing test reports, tracking failures, and so on.

To use this feature, first set up your build to run tests, then specify the path to JUnit XML files in the Ant glob syntax, such as **/build/test-reports/*.xml. Be sure not to include any non-report files into this pattern. You can specify multiple patterns of files separated by commas.

testResults
Type:String
allowEmptyResults (optional)
If checked, the default behavior of failing a build on missing test result files or empty test results is changed to not affect the status of the build. Please note that this setting make it harder to spot misconfigured jobs or build failures where the test tool does not exit with an error code when not producing test report files.
Type:boolean
checksName (optional)
If provided, and publishing checks enabled, the plugin will use this name when publishing results to corresponding SCM hosting platforms. If not, a default of "Tests" will be used.
Type:String
healthScaleFactor (optional)
The amplification factor to apply to test failures when computing the test result contribution to the build health score.
The default factor is 1.0
  • A factor of 0.0 will disable the test result contribution to build health score.
  • A factor of 0.1 means that 10% of tests failing will score 99% health
  • A factor of 0.5 means that 10% of tests failing will score 95% health
  • A factor of 1.0 means that 10% of tests failing will score 90% health
  • A factor of 2.0 means that 10% of tests failing will score 80% health
  • A factor of 2.5 means that 10% of tests failing will score 75% health
  • A factor of 5.0 means that 10% of tests failing will score 50% health
  • A factor of 10.0 means that 10% of tests failing will score 0% health
The factor is persisted with the build results, so changes will only be reflected in new builds.
Type:double
keepLongStdio (optional)
If checked, any standard output or error from a test suite will be retained in the test results after the build completes. (This refers only to additional messages printed to console, not to a failure stack trace.) Such output is always kept if the test failed, but by default lengthy output from passing tests is truncated to save space. Check this option if you need to see every log message from even passing tests, but beware that Jenkins's memory consumption can substantially increase as a result, even if you never look at the test results!
Type:boolean
keepProperties (optional)
Type:boolean
skipMarkingBuildUnstable (optional)
If this option is unchecked, then the plugin will mark the build as unstable when it finds at least 1 test failure. If this option is checked, then the build will still be successful even if there are test failures reported.
Type:boolean
skipOldReports (optional)
Type:boolean
skipPublishingChecks (optional)
If this option is unchecked, then the plugin automatically publishes the test results to corresponding SCM hosting platforms. For example, if you are using this feature for a GitHub organization project, the warnings will be published to GitHub through the Checks API. If this operation slows down your build, or you don't want to publish the warnings to SCM platforms, you can use this option to deactivate this feature.
Type:boolean
testDataPublishers (optional)
Array/List:
Nested choice of objects
javadoc
javadocDir
Type:String
keepAll
If you check this option, Jenkins will retain Javadoc for each successful build. This allows you to browse Javadoc for older builds, at the expense of additional disk space requirement.

If you leave this option unchecked, Jenkins will only keep the latest Javadoc, so older Javadoc will be overwritten as new builds succeed.

Type:boolean
$class: 'Mailer'
If configured, Jenkins will send out an e-mail to the specified recipients when a certain important event occurs.
  1. Every failed build triggers a new e-mail.
  2. A successful build after a failed (or unstable) build triggers a new e-mail, indicating that a crisis is over.
  3. An unstable build after a successful build triggers a new e-mail, indicating that there's a regression.
  4. Unless configured, every unstable build triggers a new e-mail, indicating that regression is still there.
For lazy projects where unstable builds are the norm, Uncheck "Send e-mail for every unstable build".
recipients
Type:String
notifyEveryUnstableBuild
Type:boolean
sendToIndividuals
If this option is checked, the notification e-mail will be sent to individuals who have committed changes for the broken build (by assuming that those changes broke the build).

If e-mail addresses are also specified in the recipient list, then both the individuals as well as the specified addresses get the notification e-mail. If the recipient list is empty, then only the individuals will receive e-mails.

Type:boolean
mineRepository
scm (optional)
Type:String
discoverReferenceBuild
referenceJob (optional)
The reference job is the baseline that is used to determine which of the issues in the current build are new, outstanding, or fixed. This baseline is also used to determine the number of new issues for the quality gate evaluation.
Type:String
cleanWs
cleanWhenAborted (optional)
Type:boolean
cleanWhenFailure (optional)
Type:boolean
cleanWhenNotBuilt (optional)
Type:boolean
cleanWhenSuccess (optional)
Type:boolean
cleanWhenUnstable (optional)
Type:boolean
cleanupMatrixParent (optional)
Type:boolean
deleteDirs (optional)
Type:boolean
disableDeferredWipeout (optional)
Type:boolean
externalDelete (optional)
Type:String
notFailBuild (optional)
Type:boolean
patterns (optional)
Array/List:
Nested object
pattern
Type:String
type
Values:
INCLUDE
EXCLUDE
skipWhenFailed (optional)
Type:boolean
throttle: Throttle execution of node blocks within this body
categories

One or more throttle categories in a list.

Array/List:
Type:String
timeout: Enforce time limit
Executes the code inside the block with a determined time out limit. If the time limit is reached, an exception (org.jenkinsci.plugins.workflow.steps.FlowInterruptedException) is thrown, which leads to aborting the build (unless it is caught and processed somehow).
time
The length of time for which this step will wait before cancelling the nested block.
Type:int
activity (optional)
Timeout after no activity in logs for this block instead of absolute duration. Defaults to false.
Type:boolean
unit (optional)
The unit of the time parameter. Defaults to 'MINUTES' if not specified.
Values:
NANOSECONDS
MICROSECONDS
MILLISECONDS
SECONDS
MINUTES
HOURS
DAYS
timestamps: Timestamps
tm: Expand a string containing macros
stringWithMacro
Type:String
tool: Use a tool from a predefined Tool Installation
Binds a tool installation to a variable (the tool home directory is returned). Only tools already configured in Configure System are available here. If the original tool installer has the auto-provision feature, then the tool will be installed as required.
name
The name of the tool. The tool name must be pre-configured in Jenkins under Manage JenkinsGlobal Tool Configuration.
Type:String
type (optional)
Select the type from the available built-in tool providers.
Type:String
unstable: Set stage result to unstable
Prints a message to the log and sets the overall build result and the stage result to UNSTABLE. The message will also be associated with the stage result and may be shown in visualizations.
message
A message that will be logged to the console. The message will also be associated with the stage result and may be shown in visualizations.
Type:String
unstash: Restore files previously stashed
Restores a set of files previously stashed into the current workspace.
name
Name of a previously saved stash.
Type:String
updateGitlabCommitStatus: Update the commit status in GitLab
name (optional)
Type:String
state (optional)
Values:
pending
running
canceled
success
failed
skipped
validateDeclarativePipeline: Validate a file containing a Declarative Pipeline
Checks if the given file (as relative path to current directory) contains a valid Declarative Pipeline. Returns true | false.
path
Relative (/-separated) path to file within a workspace to validate as a Declarative Pipeline.
Type:String
waitForBuild: Wait for build to complete

Wait on a build to complete.

Use the Pipeline Snippet Generator to generate a sample pipeline script for the waitforBuild step.

runId

The externalizableId of the build to wait on.

Type:String
propagate (optional)

If enabled, then the result of this step is that of the downstream build being waited on (e.g., success, unstable, failure, not built, or aborted). If disabled (default state), then this step succeeds even if the downstream build is unstable, failed, etc.; use the result property of the return value as needed.

Type:boolean
propagateAbort (optional)
Type:boolean
waitForQualityGate: Wait for SonarQube analysis to be completed and return quality gate status

This step pauses Pipeline execution and wait for previously submitted SonarQube analysis to be completed and returns quality gate status. Setting the parameter abortPipeline to true will abort the pipeline if quality gate status is not green.

Note: This step doesn't require an executor.

Requirements:

  • SonarQube server 6.2+
  • Configure a webhook in your SonarQube server pointing to <your Jenkins instance>/sonarqube-webhook/. The trailing slash is mandatory!
  • Use withSonarQubeEnv step to run your analysis prior to use this step

Example using declarative pipeline:

      pipeline {
        agent none
        stages {
          stage("build & SonarQube analysis") {
            agent any
            steps {
              withSonarQubeEnv('My SonarQube Server') {
                sh 'mvn clean package sonar:sonar'
              }
            }
          }
          stage("Quality Gate") {
            steps {
              timeout(time: 1, unit: 'HOURS') {
                waitForQualityGate abortPipeline: true
              }
            }
          }
        }
      }
      

Example using scripted pipeline:

      stage("build & SonarQube analysis") {
          node {
              withSonarQubeEnv('My SonarQube Server') {
                 sh 'mvn clean package sonar:sonar'
              }    
          }
      }
      
      stage("Quality Gate"){
          timeout(time: 1, unit: 'HOURS') {
              def qg = waitForQualityGate()
              if (qg.status != 'OK') {
                  error "Pipeline aborted due to quality gate failure: ${qg.status}"
              }
          }
      }        
      

abortPipeline
Type:boolean
credentialsId (optional)
Type:String
webhookSecretId (optional)
Type:String
waitUntil: Wait for condition
Runs its body repeatedly until it returns true. If it returns false, waits a while and tries again. (Subsequent failures will slow down the delay between attempts up to a maximum of 15 seconds.) There is no limit to the number of retries, but if the body throws an error that is thrown up immediately.
initialRecurrencePeriod (optional)
Sets the initial wait period, in milliseconds, between retries. Defaults to 250ms.
Each failure will slow down the delay between attempts up to a maximum of 15 seconds.
Type:long
quiet (optional)
If true, the step does not log a message each time the condition is checked. Defaults to false.
Type:boolean
warnError: Catch error and set build and stage result to unstable
Executes its body, and if an exception is thrown, sets the overall build result and the stage result to UNSTABLE, prints a specified message and the thrown exception to the build log, and associates the stage result with the message so that it can be displayed by visualizations.

Equivalent to catchError(message: message, buildResult: 'UNSTABLE', stageResult: 'UNSTABLE').

message
A message that will be logged to the console if an error is caught. The message will also be associated with the stage result and may be shown in visualizations.
Type:String
catchInterruptions (optional)
If true, certain types of exceptions that are used to interrupt the flow of execution for Pipelines will be caught and handled by the step. If false, those types of exceptions will be caught and immediately rethrown. Examples of these types of exceptions include those thrown when a build is manually aborted through the UI and those thrown by the timeout step. Defaults to true.
Type:boolean
withAnt: With Ant
Prepares an environment for Jenkins to run builds using Apache Ant. Annotates Ant-specific output to display executed targets. Optionally sets up an Ant and/or JDK installation.
installation (optional)

Name of an Ant installation to use so that ant will be in the path.

Type:String
jdk (optional)

Name of an Java installation to use when running Ant.

Type:String
withChecks: Inject checks properties into its closure
name
Type:String
withCredentials: Bind credentials to variables

Allows various kinds of credentials (secrets) to be used in idiosyncratic ways. (Some steps explicitly ask for credentials of a particular kind, usually as a credentialsId parameter, in which case this step is unnecessary.) Each binding will define an environment variable active within the scope of the step. You can then use them directly from any other steps that expect environment variables to be set:

node {
  withCredentials([usernameColonPassword(credentialsId: 'mylogin', variable: 'USERPASS')]) {
    sh '''
      set +x
      curl -u "$USERPASS" https://private.server/ > output
    '''
  }
}

As another example (use Snippet Generator to see all options):

node {
  withCredentials([string(credentialsId: 'mytoken', variable: 'TOKEN')]) {
    sh '''
      set +x
      curl -H "Token: $TOKEN" https://some.api/
    '''
  }
}

Note the use of single quotes to define the script (implicit parameter to sh) in Groovy above. You want the secret to be expanded by the shell as an environment variable. The following idiom is potentially less secure, as the secret is interpolated by Groovy and so (for example) typical operating system process listings will accidentally disclose it:

node {
  withCredentials([string(credentialsId: 'mytoken', variable: 'TOKEN')]) {
    sh /* WRONG! */ """
      set +x
      curl -H 'Token: $TOKEN' https://some.api/
    """
  }
}

At least on Linux, environment variables can be obtained by other processes running in the same account, so you should not run a job which uses secrets on the same node as a job controlled by untrusted parties. In any event, you should always prefer expansion as environment variables to inclusion in the command, since Jenkins visualizations such as Blue Ocean will attempt to detect step parameters containing secrets and refuse to display them.

The secret(s) will be masked (****) in case they are printed to the build log. This prevents you from accidentally disclosing passwords and the like via the log. (Bourne shell set +x, or Windows batch @echo off, blocks secrets from being displayed in echoed commands; but build tools in debug mode might dump all environment variables to standard output/error, or poorly designed network clients might display authentication, etc.) The masking could of course be trivially circumvented; anyone permitted to configure a job or define Pipeline steps is assumed to be trusted to use any credentials in scope however they like.

Beware that certain tools mangle secrets when displaying them. As one example, Bash (as opposed to Ubuntu’s plainer Dash) does so with text containing ' in echo mode:

$ export PASS=foo"'"bar
$ env|fgrep PASS
PASS=foo'bar
$ sh -xc 'echo $PASS'
+ echo foo'bar
foo'bar
$ bash -xc 'echo $PASS'
+ echo 'foo'\''bar'
foo'bar

Mangled secrets can only be detected on a best-effort basis. By default, Jenkins will attempt to mask mangled secrets as they would appear in output of Bourne shell, Bash, Almquist shell and Windows batch. Without these strategies in place, mangled secrets would appear in plain text in log files. In the example above, this would result in:

+ echo 'foo'\''bar'
****

This particular issue can be more safely prevented by turning off echo with set +x or avoiding the use of shell metacharacters in secrets.

For bindings which store a secret file, beware that

node {
  dir('subdir') {
    withCredentials([file(credentialsId: 'secret', variable: 'FILE')]) {
      sh 'use $FILE'
    }
  }
}

is not safe, as $FILE might be inside the workspace (in subdir@tmp/secretFiles/), and thus visible to anyone able to browse the job’s workspace. If you need to run steps in a different directory than the usual workspace, you should instead use

node {
  withCredentials([file(credentialsId: 'secret', variable: 'FILE')]) {
    dir('subdir') {
      sh 'use $FILE'
    }
  }
}

to ensure that the secrets are outside the workspace; or choose a different workspace entirely:

node {
  ws {
    withCredentials([file(credentialsId: 'secret', variable: 'FILE')]) {
      sh 'use $FILE'
    }
  }
}

Also see the Limitations of Credentials Masking blog post for more background.

bindings
Array/List:
Nested choice of objects
certificate
Sets one variable to the username and one variable to the password given in the credentials.
Warning: if the Jenkins controller or agent node has multiple executors, any other build running concurrently on the same node will be able to read the text of the secret, for example on Linux using ps e.
keystoreVariable
Name of an environment variable to be set to the temporary keystore location during the build. The contents of this file are not masked.
Type:String
credentialsId
Credentials of an appropriate type to be set to the variable.
Type:String
aliasVariable (optional)
Name of an environment variable to be set to the keystore alias name of the certificate during the build.
Type:String
passwordVariable (optional)
Name of an environment variable to be set to the password during the build.
Type:String
file
Copies the file given in the credentials to a temporary location, then sets the variable to that location. (The file is deleted when the build completes.)
Warning: if the Jenkins controller or agent node has multiple executors, any other build running concurrently on the same node will be able to read the contents of this file.
variable
Name of an environment variable to be set during the build. The contents of this location are not masked.
Type:String
credentialsId
Credentials of an appropriate type to be set to the variable.
Type:String
gitUsernamePassword
gitToolName

Specify the Git tool installation name

Type:String
credentialsId
Set the git username / password credential for HTTP and HTTPS protocols.

Shell example

withCredentials([gitUsernamePassword(credentialsId: 'my-credentials-id',
                 gitToolName: 'git-tool')]) {
  sh 'git fetch --all'
}

Batch example

withCredentials([gitUsernamePassword(credentialsId: 'my-credentials-id',
                 gitToolName: 'git-tool')]) {
  bat 'git submodule update --init --recursive'
}

Powershell example

withCredentials([gitUsernamePassword(credentialsId: 'my-credentials-id',
                 gitToolName: 'git-tool')]) {
  powershell 'git push'
}

Type:String
sshUserPrivateKey
Copies the SSH key file given in the credentials to a temporary location, then sets a variable to that location. (The file is deleted when the build completes.) Also optionally sets variables for the SSH key's username and passphrase.
Warning: if the Jenkins controller or agent node has multiple executors, any other build running concurrently on the same node will be able to read the contents of this file.
keyFileVariable
Name of an environment variable to be set to the temporary path of the SSH key file during the build. The contents of this file are not masked.
Type:String
credentialsId
Credentials of an appropriate type to be set to the variable.
Type:String
passphraseVariable (optional)
Name of an environment variable to be set to the password during the build. (optional)
Type:String
usernameVariable (optional)
Name of an environment variable to be set to the username during the build. (optional)
Type:String
string
Sets a variable to the text given in the credentials.
Warning: if the Jenkins controller or agent node has multiple executors, any other build running concurrently on the same node will be able to read the text of the secret, for example on Linux using ps e.
variable
Name of an environment variable to be set during the build. The contents of this location are not masked.
Type:String
credentialsId
Credentials of an appropriate type to be set to the variable.
Type:String
usernameColonPassword
Sets a variable to the username and password given in the credentials, separated by a colon (:).
Warning: if the Jenkins controller or agent node has multiple executors, any other build running concurrently on the same node will be able to read the text of the secret, for example on Linux using ps e.
variable
Name of an environment variable to be set during the build. The contents of this location are not masked.
Type:String
credentialsId
Credentials of an appropriate type to be set to the variable.
Type:String
usernamePassword
Sets one variable to the username and one variable to the password given in the credentials.
Warning: if the Jenkins controller or agent node has multiple executors, any other build running concurrently on the same node will be able to read the text of the secret, for example on Linux using ps e.
usernameVariable
Name of an environment variable to be set to the username during the build.
Type:String
passwordVariable
Name of an environment variable to be set to the password during the build.
Type:String
credentialsId
Credentials of an appropriate type to be set to the variable.
Type:String
zip
Unpacks the ZIP file given in the credentials to a temporary directory, then sets the variable to that location. (The directory is deleted when the build completes.)
Warning: if the Jenkins controller or agent node has multiple executors, any other build running concurrently on the same node will be able to read the contents of this directory.
variable
Name of an environment variable to be set during the build. The contents of this location are not masked.
Type:String
credentialsId
Credentials of an appropriate type to be set to the variable.
Type:String
withEnv: Set environment variables
Sets one or more environment variables within a block. The names of environment variables are case-insensitive but case-preserving, that is, setting `Foo` will change the value of `FOO` if it already exists. Environment variables are available to any external processes spawned within that scope. For example:

node {
  withEnv(['MYTOOL_HOME=/usr/local/mytool']) {
    sh '$MYTOOL_HOME/bin/start'
  }
}

(Note that here we are using single quotes in Groovy, so the variable expansion is being done by the Bourne shell, not Jenkins.)

See the documentation for the env singleton for more information on environment variables.

overrides
A list of environment variables to set, each in the form VARIABLE=value or VARIABLE= to unset variables otherwise defined. You may also use the syntax PATH+WHATEVER=/something to prepend /something to $PATH.
Array/List:
Type:String
withMaven: Provide Maven environment
Configures maven environment to use within a pipeline job by calling sh mvn or bat mvn. The selected maven installation will be configured and prepended to the path.
globalMavenSettingsConfig (optional)
Select a global maven settings element from File Config Provider. The settings element in the settings.xml file contains elements used to define values which configure Maven execution in various ways, like the pom.xml, but should not be bundled to any specific project, or distributed to an audience. These include values such as the local repository location, alternate remote repository servers, and authentication information.

see also: settings.xml reference

Type:String
globalMavenSettingsFilePath (optional)
Specify a global maven settings.xml file. The specified path can be absolute or relative to the workspace. Shell-like environment variable expansions work in this field, by using the ${VARIABLE} syntax. The file existence is checked on the build agent, if found, that one is used. If not found it will be checked on the master. The settings element in the settings.xml file contains elements used to define values which configure Maven execution in various ways, like the pom.xml, but should not be bundled to any specific project, or distributed to an audience. These include values such as the local repository location, alternate remote repository servers, and authentication information.
There are two locations where a settings.xml file per default may live:
  • The Maven install - default: $M2_HOME/conf/settings.xml
  • A user's install - default: ${user.home}/.m2/settings.xml
The former settings.xml are also called global settings, the latter settings.xml are referred to as user settings. If both files exists, their contents gets merged, with the user-specific settings.xml being dominant.

see also: settings.xml reference

Type:String
jdk (optional)
Select a JDK installation. If auto-install is enabled, the JDK will be downloaded and made available for the pipeline job.

Note: This option does not work with docker.image('xxx').inside or container('xxx'), the preinstalled JDK on the docker image will be used.

Type:String
maven (optional)
Select a Maven installation. If auto-install is enabled, maven will be downloaded and made available for the pipeline job.

Note: This option does not work with docker.image('xxx').inside or container('xxx'), the preinstalled maven on the docker image will be used.

Type:String
mavenLocalRepo (optional)
Specify a custom local repository path. Shell-like environment variable expansions work with this field, by using the ${VARIABLE} syntax. Normally, Jenkins uses the local Maven repository as determined by Maven, by default ~/.m2/repository and can be overridden by <localRepository> in ~/.m2/settings.xml (see Configuring your Local Repository))

This normally means that all the jobs that are executed on the same node shares a single Maven repository. The upside of this is that you can save the disk space, the downside is that the repository is not multi process safe and having multiple builds run concurrently can corrupt it. Additionally builds could interfere with each other by sharing incorrect or partially built artifacts. For example, you might end up having builds incorrectly succeed, just because your have all the dependencies in your local repository, despite that fact that none of the repositories in POM might have them.

By using this option, Jenkins will tell Maven to use a custom path for the build as the local Maven repository by using -Dmaven.repo.local
If specified as a relative path then this value well be resolved against the workspace root and not the current working directory.
ie. if .repository is specified then $WORKSPACE/.repository will be used.

This means each job could get its own isolated Maven repository just for itself. It fixes the above problems, at the expense of additional disk space consumption.

When using this option, consider setting up a Maven artifact manager so that you don't have to hit remote Maven repositories too often.

Type:String
mavenOpts (optional)
Specify JVM specific options needed when launching Maven as an external process, these are not maven specific options. See: Java Options

Shell-like environment variable expansions work in this field, by using the ${VARIABLE} syntax.

Type:String
mavenSettingsConfig (optional)
Select a maven settings element from File Config Provider. The settings element in the settings.xml file contains elements used to define values which configure Maven execution in various ways, like the pom.xml, but should not be bundled to any specific project, or distributed to an audience. These include values such as the local repository location, alternate remote repository servers, and authentication information.

see also: settings.xml reference

Type:String
mavenSettingsFilePath (optional)
Specify a maven settings.xml file. The specified path can be absolute or relative to the workspace. Shell-like environment variable expansions work in this field, by using the ${VARIABLE} syntax. The file existence is checked on the build agent, if found, that one is used. If not found it will be checked on the master. The settings element in the settings.xml file contains elements used to define values which configure Maven execution in various ways, like the pom.xml, but should not be bundled to any specific project, or distributed to an audience. These include values such as the local repository location, alternate remote repository servers, and authentication information.
There are two locations where a settings.xml file per default may live:
  • The Maven install - default: $M2_HOME/conf/settings.xml
  • A user's install - default: ${user.home}/.m2/settings.xml
The former settings.xml are also called global settings, the latter settings.xml are referred to as user settings. If both files exists, their contents gets merged, with the user-specific settings.xml being dominant.

see also: settings.xml reference

Type:String
options (optional)
Array/List:
Nested choice of objects
concordionPublisher
Publish Concordion reports, if found, regarding the given pattern.
Test results are by default published if the Jenkins HTMLPublisher Plugin is installed.
disabled (optional)
Skip the publishing of tests reports.
Type:boolean
dependenciesFingerprintPublisher
Fingerprint the Maven dependencies used by the maven project.
disabled (optional)
Skip the fingerprinting of the dependencies of the maven project.
Type:boolean
includeReleaseVersions (optional)
Type:boolean
includeScopeCompile (optional)
Type:boolean
includeScopeProvided (optional)
Type:boolean
includeScopeRuntime (optional)
Type:boolean
includeScopeTest (optional)
Type:boolean
includeSnapshotVersions (optional)
Type:boolean
findbugsPublisher
Publish FindBugs reports generated by "org.codehaus.mojo:findbugs-maven-plugin:findbugs".
FindBugs results are by default published if the Jenkins FindBugs Plugin is installed.
disabled (optional)
Skip the publishing of findbugs reports.
Type:boolean
healthy (optional)
Type:String
thresholdLimit (optional)
Type:String
unHealthy (optional)
Type:String
artifactsPublisher
Archive and fingerprint the artifact and the attached artifacts generated by the maven project.
archiveFilesDisabled (optional)
Type:boolean
disabled (optional)
Skip the archiving and the fingerprinting of generated artifacts.
Type:boolean
fingerprintFilesDisabled (optional)
Type:boolean
invokerPublisher
Publish Invoker reports generated by "org.apache.maven.plugins:maven-invoker-plugin:run".
Invoker results are by default published if the Jenkins Maven Invoker Plugin is installed.
disabled (optional)
Skip the publishing of invoker reports.
Type:boolean
jgivenPublisher
Publish JGiven reports, if found.
Test results are by default published if the Jenkins JGiven Plugin is installed.
disabled (optional)
Skip the publishing of tests reports.
Type:boolean
jacocoPublisher
Publish JaCoCo Java Code Coverage Library reports, if found.
Test results are by default published if the Jenkins JaCoCo Plugin is installed.
disabled (optional)
Skip the publishing of JaCoCo reports.
Type:boolean
junitPublisher
Publish tests reports generated by "maven-surefire-plugin:test" or by "maven-failsafe-plugin:integration-test".
Test results are by default published if the Jenkins JUnit Plugin is installed.
disabled (optional)
Skip the publishing of tests reports.
Type:boolean
healthScaleFactor (optional)
The amplification factor to apply to test failures when computing the test result contribution to the build health score.
The default factor is 1.0
  • A factor of 0.0 will disable the test result contribution to build health score.
  • A factor of 0.1 means that 10% of tests failing will score 99% health
  • A factor of 0.5 means that 10% of tests failing will score 95% health
  • A factor of 1.0 means that 10% of tests failing will score 90% health
  • A factor of 2.0 means that 10% of tests failing will score 80% health
  • A factor of 2.5 means that 10% of tests failing will score 75% health
  • A factor of 5.0 means that 10% of tests failing will score 50% health
  • A factor of 10.0 means that 10% of tests failing will score 0% health
The factor is persisted with the build results, so changes will only be reflected in new builds.
Type:double
ignoreAttachments (optional)
Skip the publishing of tests reports attachments.
Test result attachments are by default published if the Jenkins JUnit Attachments Plugin is installed.
Type:boolean
keepLongStdio (optional)
If checked, any standard output or error from a test suite will be retained in the test results after the build completes. (This refers only to additional messages printed to console, not to a failure stack trace.) Such output is always kept if the test failed, but by default lengthy output from passing tests is truncated to save space. Check this option if you need to see every log message from even passing tests, but beware that Jenkins's memory consumption can substantially increase as a result, even if you never look at the test results!
Type:boolean
mavenLinkerPublisher
This publisher generates and publishes the links (url) of deployed Maven artifacts.
disabled (optional)
Skip generating and publishing the links.
Type:boolean
pipelineGraphPublisher
Build a graph of pipelines based on their Maven dependencies and on the Maven artifacts they generate.
disabled (optional)
Skip the depedencies graph computing of the maven project, and triggering of dependent pipelines.
Type:boolean
ignoreUpstreamTriggers (optional)
Type:boolean
includeReleaseVersions (optional)
Type:boolean
includeScopeCompile (optional)
Type:boolean
includeScopeProvided (optional)
Type:boolean
includeScopeRuntime (optional)
Type:boolean
includeScopeTest (optional)
Type:boolean
includeSnapshotVersions (optional)
Type:boolean
lifecycleThreshold (optional)

Threshold to trigger downstream pipelines based on the Maven lifecycle phase successfully reached during the Maven execution.

If "install" is selected then downstream pipelines will be triggered for "mvn clean install", "mvn clean deploy" but NOT "mvn clean verify" or "mvn clean package".

Example

Configure a Jenkins Multibranch Pipeline with

  • Threshold: "deploy"
  • execution of "mvn clean deploy" on branches (incl. master) and execution of "mvn clean verify on pull requests
So that:
  • The builds of branches (incl. "master") would upload the generated jar/war file to your enterprise Maven repository and would trigger downstream pipelines
  • The builds of pull request would only build the package but NOT upload the generated jar/war file to your enterprise Maven repository and would NOT trigger downstream pipelines

Type:String
skipDownstreamTriggers (optional)
Type:boolean
spotbugsPublisher
Publish SpotBugs reports generated by "com.github.spotbugs:spotbugs-maven-plugin:spotbugs".
SpotBugs results are by default published if the Jenkins FindBugs Plugin is installed.
disabled (optional)
Skip the publishing of SpotBugs reports.
Type:boolean
healthy (optional)
Type:String
thresholdLimit (optional)
Type:String
unHealthy (optional)
Type:String
openTasksPublisher
Publish Open Task Scanner reports.
Open Task Scanner reports are by default published if the Jenkins Task Scanner Plugin is installed.
The default setup is to look in Java source code for "FIXME" comments as high priority tasks and for "TODO" comments as normal priority tasks.
asRegexp (optional)
Use task identifiers as regular expressions.
Type:boolean
disabled (optional)
Skip the publishing of Task Scanner reports.
Type:boolean
excludePattern (optional)
Ant style pattern of exclude source code.
Type:String
healthy (optional)
Type:String
highPriorityTaskIdentifiers (optional)
Coma separated list of high priority task identifiers.
Type:String
ignoreCase (optional)
Ignore case when scanning task identifiers.
Type:boolean
lowPriorityTaskIdentifiers (optional)
Coma separated list of low priority task identifiers.
Type:String
normalPriorityTaskIdentifiers (optional)
Coma separated list of normal priority task identifiers.
Type:String
pattern (optional)
Ant style pattern of the source code to scan for task identifiers.
Type:String
thresholdLimit (optional)
Type:String
unHealthy (optional)
Type:String
publisherStrategy (optional)
IMPLICIT All Maven publishers are implicitly enabled and used, even if they are not configured in "withMaven(options:...)".
EXPLICIT Only the Maven publishers explicitly configured in "withMaven(options:...)" are used.
Values:
IMPLICIT
EXPLICIT
tempBinDir (optional)
Specify a custom temporary binaries directory. Allow to have a constant path to the maven binaries, then a constant environment for reproducible compilations. Some tools detect an environment change as a sources change, which will retrigger the compilation of all sources.
Type:String
traceability (optional)
Should additional information be added to the script execution.

Note: This option adds --show-version to the maven execution and marks the beginning of the maven wrapper script with ----- withMaven Wrapper script -----.

Type:boolean
withSonarQubeEnv: Prepare SonarQube Scanner environment
installationName
Type:String
credentialsId (optional)
Type:String
envOnly (optional)
Type:boolean
wrap: General Build Wrapper

This is a special step that allows to call build wrappers (also called "Environment Configuration" in freestyle or similar projects). Just select the wrapper to use from the dropdown list and configure it as needed. Everything inside the wrapper block is under its effect.

Note that only Pipeline-compatible wrappers will be shown in the list.

delegate
Nested choice of objects
withAnt
Prepares an environment for Jenkins to run builds using Apache Ant. Annotates Ant-specific output to display executed targets. Optionally sets up an Ant and/or JDK installation.
installation (optional)

Name of an Ant installation to use so that ant will be in the path.

Type:String
jdk (optional)

Name of an Java installation to use when running Ant.

Type:String
configFileProvider
Make globally configured files available in your local workspace. All files configured via the config-file-provider plugin are available and can be referenced.
managedFiles
Array/List:
configFile
fileId

Name of the file.

Type:String
replaceTokens (optional)

Decides whether the token should be replaced using macro.

Type:boolean
targetLocation (optional)

Name of the file (with optional file relative to workspace directory) where the config file should be copied.

Type:String
variable (optional)

Name of the variable which can be used as the reference for further configuration.

Type:String
kubeconfig
Configure Kubernetes client (kubectl) so it can be used in the build to run Kubernetes commands
serverUrl
URL of the Kubernetes API endpoint. If not set the connection options will be autoconfigured from service account or kube config file.
Type:String
credentialsId
Type:String
caCertificate
The base64 encoded certificate of the certificate authority (CA). It is used to verify the server certificate.

Leaving this field empty will skip the certificate verification.

Type:String
nodejs
nodeJSInstallationName
Type:String
cacheLocationStrategy (optional)
Nested choice of objects
default
executor
workspace
configId (optional)
Type:String
withSonarQubeEnv
installationName
Type:String
credentialsId (optional)
Type:String
envOnly (optional)
Type:boolean
$class: 'TimestamperBuildWrapper'
xvnc
If checked, Xvnc will be run during this build to provide X display. The X display number will be set to DISPLAY environment variable.
takeScreenshot (optional)
Optionally, upon completion of the build, a screenshot can be taken. This requires ImageMagick be installed.
Type:boolean
useXauthority (optional)
Type:boolean
writeFile: Write file to workspace
Write the given content to a named file in the current directory.
file
Relative path of a file within the workspace.
Type:String
text
The data to write in the file.
Type:String
encoding (optional)
The target encoding for the file. If left blank, the platform default encoding will be used. If the text is a Base64-encoded string, the decoded binary data can be written to the file by specifying "Base64" as the encoding.
Type:String
ws: Allocate workspace
Allocates a workspace. Note that a workspace is automatically allocated for you with the node step.
dir

A workspace is automatically allocated for you with the node step, or you can get an alternate workspace with this ws step, but by default the location is chosen automatically. (Something like AGENT_ROOT/workspace/JOB_NAME@2.)

You can instead specify a path here and that workspace will be locked instead. (The path may be relative to the build agent root, or absolute.)

If concurrent builds ask for the same workspace, a directory with a suffix such as @2 may be locked instead. Currently there is no option to wait to lock the exact directory requested; if you need to enforce that behavior, you can either fail (error) when pwd indicates that you got a different directory, or you may enforce serial execution of this part of the build by some other means such as the lock step.

If you do not care about locking, just use the dir step to change current directory.

Type:String
xvnc: Run Xvnc during build
If checked, Xvnc will be run during this build to provide X display. The X display number will be set to DISPLAY environment variable.
takeScreenshot (optional)
Optionally, upon completion of the build, a screenshot can be taken. This requires ImageMagick be installed.
Type:boolean
useXauthority (optional)
Type:boolean

Advanced/Deprecated Steps

archive: Archive artifacts
Archives build output artifacts for later use. As of Jenkins 2.x, this step is deprecated in favor of the more configurable archiveArtifacts.
includes
Include artifacts matching this Ant style pattern. Use a comma separated list to add more than one expression.
Type:String
excludes (optional)
Exclude artifacts matching this Ant-style pattern.
Use a comma-separated list to add more than one expression.
Type:String
containerLog: Get container log from Kubernetes
name
Name of the container, as specified in containerTemplate.
Type:String
limitBytes (optional)
If set, the number of bytes to read from the server before terminating the log output. This may not display a complete final line of logging, and may return slightly more or slightly less than the specified limit.
Type:int
returnLog (optional)
Return the container log. If not checked, the log will be printed to the build log.
Type:boolean
sinceSeconds (optional)
A relative time in seconds before the current time from which to show logs. If this value precedes the time a pod was started, only logs since the pod start will be returned. If this value is in the future, no logs will be returned.
Type:int
tailingLines (optional)
If set, the number of lines from the end of the log to show. If not specified, log is shown from the creation of the container or limited by "sinceSeconds".
Type:int
envVarsForTool: Fetches the environment variables for a given tool in a list of 'FOO=bar' strings suitable for the withEnv step.
toolId
Type:String
toolVersion
Type:String
getContext: Get contextual object from internal APIs

Obtains a contextual object as in StepContext.get; cf. withContext. Takes a single type argument. Example:

getContext hudson.FilePath

For use from trusted code, such as global libraries, which can manipulate internal Jenkins APIs.

type
java.lang.UnsupportedOperationException: do not know how to categorize attributes of type java.lang.Class<?>
unarchive: Copy archived artifacts into the workspace
mapping (optional)
java.lang.UnsupportedOperationException: do not know how to categorize attributes of type java.util.Map<java.lang.String, java.lang.String>
withContext: Use contextual object from internal APIs within a block

Wraps a block in a contextual object as in BodyInvoker.withContext; cf. getContext. Takes a single context argument plus a block. Example:

withContext(new MyConsoleLogFilter()) {
    sh 'process'
}

Automatically merges its argument with contextual objects in the case of ConsoleLogFilter, LauncherDecorator, and EnvironmentExpander.

For use from trusted code, such as global libraries, which can manipulate internal Jenkins APIs.

Do not attempt to pass objects defined in Groovy; only Java-defined objects are supported. Really you should avoid using this and getContext and just define a Step in a plugin instead.

context
Nested choice of objects
(not enumerable)