Run Coverity Scan only when specific variables are present
Submissions to Coverity Scan should be limited to those originated from release branches and only from a specific schedule which holds COVERITY_SCAN_PROJECT_NAME and COVERITY_SCAN_TOKEN variables.
The job would fail anyway as it requires project name and token, which likely were not added to the environment when started via web UI.
Edited by Michal Nowak