The following plugin provides functionality available through Pipeline-compatible steps. Read more about how to integrate steps into your Pipeline in the Steps section of the Pipeline Syntax page.

For a list of other such plugins, see the Pipeline Steps Reference page.

TICS Plugin

View this plugin on the Plugins site

step([$class: 'TicsAnalyzer']): Run TICS

  • ticsPath : String
    The fully qualified directory where TICS is located, e.g. C:\Program Files\TIOBE\TICS\BuildServer. This directory should contain the TICSQServer executable. You can leave this field empty if these executables can be found on the PATH environment variable of the Jenkins agent user or if you checked the "Install TICS command-line tools" checkbox.
  • ticsConfiguration : String

    Τhe TICS Configuration is a URL pointing to the 'cfg' API endpoint of the TICS Viewer. It is of the following format https://192.168.1.1/tiobeweb/TICS/api/cfg?name=-. This URL contains the name of the TICS Analyzer Configuration or '-' in case of the default configuration. Please ask your TICS Representative to provide you with a valid configuration name.

    For TICS installations using the legacy deployment architecture, TICS Configuration points to the configuration directory, e.g. C:\Program Files (x86)\TIOBE\TICS\FileServer\cfg. The TICS configuration directory contains the SERVER.yaml and PROJECTS.yaml configuration files, among others. This setting sets the TICS environment variable before executing TICSQServer. You can leave this field empty if this variable is already set on the Jenkins slave.

  • projectName : String
    The name of the project for which this run should be performed. This project should already exist in the TICS Configuration as you cannot create a new project using this plugin. You can create a new project by using the Build Configuration page of the Viewer or by using TICSMaintenance from the command line. Note that you can use Jenkins environment variables such as $JOB_NAME here.
  • branchName : String
    The name of the branch for which the run should be performed. Although most projects only have one branch (named "trunk", "main", or "master"), you still need to specify the branch name here because more branches might be added later. To find out the branches of a project you can use the Build Configuration page of the TICS Viewer.
  • branchDirectory : String
    The branch directory is the root directory of the source files for the branch. If this setting is provided, the branch directory will be updated prior to each TICSQServer run by invoking TICSMaintenance -branchdir. Note that you can use Jenkins variables (such as $WORKSPACE) here.
  • environmentVariables : String
    A new-line separated list of environment variables that will be set before invoking TICSQServer. Some TICS modules and code checkers might need configuration using environment variables. Note that you can use environment variables such as $WORKSPACE here. Example: 

    TICS_M2_OPTS=-s C:\Tools\apache-maven\conf\settings.xml
TICS_COVERITY_URL=http://localhost:8080
QACBIN=C:/QAC/common/bin
PATH=C:\Tools\bin;$PATH

  • createTmpdir : boolean
  • tmpdir : String
    TICSQServer will create a directory named "ticstmpdir" in this directory. This tmpdir will contain log files useful for debugging problems encountered during the TICSQServer analysis. You can use Jenkins variables here. Example: C:/temp/$JOB_NAME.
  • extraArguments : String
    Extra arguments to pass to the TICSQServer invocation.
  • calc
    Check one or more metrics to have TICSQServer only calculate these metrics (for changed files). If nothing is checked, all metrics will be calculated.
      Nested Object
    • ABSTRACTINTERPRETATION : boolean
    • ACCUCHANGERATE : boolean
    • ACCUFIXRATE : boolean
    • ACCULINESADDED : boolean
    • ACCULINESCHANGED : boolean
    • ACCULINESDELETED : boolean
    • ALL : boolean
    • AVGCYCLOMATICCOMPLEXITY : boolean
    • BUILDRELATIONS : boolean
    • CHANGEDFILES : boolean
    • CHANGERATE : boolean
    • CODINGSTANDARD : boolean
    • COMPILERWARNING : boolean
    • DEADCODE : boolean
    • DUPLICATEDCODE : boolean
    • ELOC : boolean
    • FANOUT : boolean
    • FINALIZE : boolean
    • FIXRATE : boolean
    • GLOC : boolean
    • INCLUDERELATIONS : boolean
    • INTEGRATIONTESTCOVERAGE : boolean
    • LINESADDED : boolean
    • LINESCHANGED : boolean
    • LINESDELETED : boolean
    • LOC : boolean
    • MAXCYCLOMATICCOMPLEXITY : boolean
    • PREPARE : boolean
    • SECURITY : boolean
    • SYSTEMTESTCOVERAGE : boolean
    • TOTALTESTCOVERAGE : boolean
    • UNITTESTCOVERAGE : boolean
  • recalc
    Check one or more metrics to have TICSQServer recalculate these metrics, even for unchanged files. If nothing is checked, TICSQServer does not force recalculation of metrics for unchanged files.
      Nested Object
    • ABSTRACTINTERPRETATION : boolean
    • ACCUCHANGERATE : boolean
    • ACCUFIXRATE : boolean
    • ACCULINESADDED : boolean
    • ACCULINESCHANGED : boolean
    • ACCULINESDELETED : boolean
    • ALL : boolean
    • AVGCYCLOMATICCOMPLEXITY : boolean
    • BUILDRELATIONS : boolean
    • CHANGEDFILES : boolean
    • CHANGERATE : boolean
    • CODINGSTANDARD : boolean
    • COMPILERWARNING : boolean
    • DEADCODE : boolean
    • DUPLICATEDCODE : boolean
    • ELOC : boolean
    • FANOUT : boolean
    • FINALIZE : boolean
    • FIXRATE : boolean
    • GLOC : boolean
    • INCLUDERELATIONS : boolean
    • INTEGRATIONTESTCOVERAGE : boolean
    • LINESADDED : boolean
    • LINESCHANGED : boolean
    • LINESDELETED : boolean
    • LOC : boolean
    • MAXCYCLOMATICCOMPLEXITY : boolean
    • PREPARE : boolean
    • SECURITY : boolean
    • SYSTEMTESTCOVERAGE : boolean
    • TOTALTESTCOVERAGE : boolean
    • UNITTESTCOVERAGE : boolean
  • installTics : boolean
    By enabling this checkbox the TICS command-line tools will be installed. For TICS installations using the legacy deployment architecture, this checkbox should not be used and TICS should be installed manually on the machine that runs this job.
  • credentialsId : String

publishTicsResults:

  • viewerUrl : String
  • branchName : String (optional)
  • checkQualityGate : boolean (optional)
  • credentialsId : String (optional)
  • failIfQualityGateFails : boolean (optional)
  • projectName : String (optional)
  • ticsProjectPath : String (optional)
  • userId : String (optional)
  • userName : String (optional)

runTics:

  • projectName : String
  • branchName : String
  • branchDirectory : String (optional)
  • calc : Array / List of String (optional)
    • credentialsId : String (optional)
    • environmentVariables (optional)
      • Type: java.util.LinkedHashMap<java.lang.String, java.lang.String>
    • extraArguments : String (optional)
    • installTics : boolean (optional)
    • recalc : Array / List of String (optional)
      • ticsBin : String (optional)
      • ticsConfiguration : String (optional)
      • tmpdir : String (optional)

      step([$class: 'TicsPublisher']): Publish TICS results

      • viewerUrl : String
        URL where the TICS Viewer can be found, including the section name. Example: http://192.168.1.1:8080/tiobeweb/TICS. To determine this URL, open your TICS Viewer, and copy and paste the first part of the URL from your browser's address bar here. The URL should include the name of the section, which in this case is TICS.

        If you have configured this URL in the global settings, you can leave it empty here.
      • ticsPath : String
        Fully qualified path to a branch. The path should be of the form HIE://PROJECT/BRANCH, where PROJECT should be substituted by the actual name of the project and BRANCH by the branch name for which you want to get the results. The name of the project and the name of the default branch can be found in the top part of the TIOBE Quality Indicator Label on the TQI Dashboard, when you select the project. Note that you can use the variable $JOB_NAME here.
      • credentialsId : String
      • checkQualityGate : boolean
        Enabling Quality Gate will perform the configured quality gate checks. If no quality gate is configured, no check will be performed. The configuration can be done in the Viewer through the Administration pages.
      • failIfQualityGateFails : boolean

      Was this page helpful?

      Please submit your feedback about this page through this quick form.

      Alternatively, if you don't wish to complete the quick form, you can simply indicate if you found this page helpful?

          


      See existing feedback here.