The fileExists step accepts neither wildcards, nor absolute paths.

However, if you install the optional Pipeline Utility Steps plugin, you can make use of the findFiles step, which does accept wildcards. For example:

def files = findFiles glob: '**/*.zip'
boolean exists = files.length > 0

As an alternative, without that plugin, you could use a shell step to run find:

def exitCode = sh script: 'find -name "*.zip" | egrep .', returnStatus: true
boolean exists = exitCode == 0

I found why it wasn't working. It is because fileExists does not support wildcards. I would need to use without wildcard or use something that supports wildcards, such as findFiles.

Jenkins pipeline to verify files existence in specific format inside when condition

2>/dev/null is putting your head in the sand. It doesn't make the danger go away, it just hides it. find still exits with the status 1 to signal the error. Jenkins sh scripts run with set -e enabled, so this stops the shell script immediately.

Test if the directory exists before running find.

In the snippet below I made a few other changes:

• Use Jenkins's dir instead of cd.
• Fix the regex passed to find -regex to look for a literal . (so as not to match e.g. wibble.not-a-zip).
• Simplify the double negative ! [ -z "$var" ] to [ -n "$var" ].

dir(WORKSPACE + '/' + BuildLocation) {
    sh '''
        if [ -d Build/ReleaseKit/Installable ]; then
            var=$(find Build/ReleaseKit/Installable/ -regex "$App.*\\.zip" 2>/dev/null)
            echo "var" ]
            then
                echo "App zip found"
                unzip -o Build/ReleaseKit/Installable/App-*.zip
            fi
    '''
}

Since the file apparently needs to be inside the Installable directory, and not somewhere deeper in a sub(*)directory, you don't need find.

dir(WORKSPACE + '/' + BuildLocation) {
    sh '''
        set Build/ReleaseKit/Installable/"1" ]; then
            echo "App zip found: $1"
            unzip -o "$1"
        fi
    '''
}

Instead of testing for the file's existence in sh, you can do it in Groovy, with the Pipeline utility steps plugin.

dir(WORKSPACE + '/' + BuildLocation) {
    def zips = findFiles glob: "Build/ReleaseKit/Installable/${App}*.zip"
    if (findFiles.length > 0) {
        env.app_zip = zips[0]
        sh 'unzip ${app_zip}'
    }
}

(All code snippets untested.)

Use findFiles which allows glob syntax:

stage('Check if file exists') {
        steps {
            script {
                def any_files = false
                def output_files = findFiles glob: './path/to/file/name_*.tar.gz'
                for (def one_file in output_files) { any_files = true; break }
                if (any_files) { // or maybe (!any_files) 
                    currentBuild.result = "ABORTED"
                    error('Could not find file!')
                }
            }
        }
    }

You probably need to use double quotes in your path instead of single quotes : if(fileExists("tmp/build/${variant}/bin/Test.xml")) so that the variable is substituted by its value.

Jenkins pipelines are written in groovy, so you can find more info about the difference between single quotes and double quotes in groovy in this question and in the official groovy documentation.

You need to use brackets when using the fileExists step in an if condition or assign the returned value to a variable

Using variable:

def exists = fileExists 'file'

if (exists) {
    echo 'Yes'
} else {
    echo 'No'
}

Using brackets:

if (fileExists('file')) {
    echo 'Yes'
} else {
    echo 'No'
}

Use the below:-

def exists = fileExists '/root/elp/test.php'

if (exists) {
    sh "LINUX SHELL COMMAND"
} else {
    println "File doesn't exist"
}

And you can follow check-if-a-file-exists-in-jenkins-pipeline

And you can also use below:-

def exitCode = sh script: 'find -name "*.zip" | egrep .', returnStatus: true
boolean exists = exitCode == 0

I have run into this issue before. I found that fileExists doesn't work on the SLES15 OS nodes and SLES containers I was using. Please note that this may have been fixed in later versions of Jenkins.

I ended up using a shell script to check for the file. You would have to modify it for Windows OS if you are using Windows.

Replaced failing

if (fileExists("/file/path")) {
    ...
}

with

if (sh(script: "#!/bin/sh \n test -e /file/path", returnStatus: true) == 0) {
    ...
}

If the build user doesn't have permission to the file or the directory in question, this acts same as if the file doesn't exist.

Shebang #!/bin/sh and the newline \n are to avoid xtrace to prevent printing of the commands in the Jenkins log.

The check is on the return status so the return status of zero means that the test is success and the directory/file exists.