Default path for Jenkins projects when the relative path is specified for a field

The default path for any Jenkins project is relative to the workspace project folder. The following table defines the default path for a project depending on where the project is created and the type of system:

Location of project creation

Type of execution environment configuration

Default path

Directly on the Jenkins web user interface Dashboard

Master or stand-alone

installationDirectory/Jenkins/workspace/projectName

For example:

Operating system

Path

Windows

JENKINS_HOME\workspace\projectName

Linux

JENKINS_HOME/workspace/projectName


Agent

rootDirectory/workspace/projectName

For example:

Operating system

Path

Windows

rootDirectory\workspace\projectName

Linux

rootDirectory/workspace/projectName


Inside a folder

Master or stand-alone

installationDirectory/Jenkins/workspace/folderName/subfolderName/projectName

For example:

Operating system

Path

Windows

JENKINS_HOME\workspace\folderName\subfolderName\projectName

Linux

JENKINS_HOME/workspace/folderName/subfolderName/projectName


Agent

 rootDirectory/workspace/folderName/subfolderName/projectName

For example:

Operating system

Path

Windows

rootDirectory\workspace\folderName\subfolderName\projectName

Linux

rootDirectory/workspace/folderName/subfolderName/projectName

Related topics

Command-and-syntax-reference

Creating-a-project

In these paths:

  • The installationDirectory variable represents the directory on the master or stand-alone system on which Jenkins is installed.
  • The projectName variable represents the name of the project.
  • The rootDirectory variable represents the root directory on the system on which the agent execution environment is configured.
  • The folderName/subfolderName variable represents the folder structure in which the new project is created. The folder structure can include multiple subfolders.

Examples of specifying the relative path for a field

The project workspace folder or any of its subfolders can contain the files that SQL Assurance might use. Some fields in the project configuration define the paths of the required files. For these fields, you can also enter the relative path of the file.

The following fields support relative paths:

Build step

Field

BMC AMI DevOps Common - Authentication

Plug-in Variables File Path

BMC AMI DevOps Common - File Transmission

Source PDS or Directory Name

Destination PDS or Directory Name

BMC AMI DevOps Common - JCL Execution

Execution JCL PDS or Directory Name

BMC AMI SQL Assurance for Db2 - Analyze Static SQL

Object List File Path

The following examples illustrate the default path that SQL Assurance considers when you specify the relative path of a file.

Example of specifying the relative path of a file located in the project workspace folder

When configuring Project1 on a stand-alone Windows system, if you enter any of the values in the following table, SQL Assurance searches for the AMI_DevOps.properties file name at the following path:

JENKINS_HOME\workspace\Project1\AMI_DevOps.properties

Field

Value

Plug-in Variables File Path

AMI_DevOps.properties

or

.\AMI_DevOps.properties

Example of specifying the relative path of a file located in a subfolder of the project workspace folder

When configuring Project2 on a stand-alone Linux system, where PropFolder is a subfolder of the project workspace folder, if you enter any of the values in the following table, SQL Assurance searches for the AMI_DevOps.properties file name at the following path:

JENKINS_HOME/workspace/Project2/PropFolder/AMI_DevOps.properties

Field

Value

Plug-in Variables File Path

PropFolder/AMI_DevOps.properties

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*