SFDX-Sam
commented
1 year ago For reference - my gitlab pipeline looks like this:
####################################################
# The docker image the jobs initialize with.
# We use nodejs, so a node image makes sense.
# https://docs.gitlab.com/ee/ci/yaml/README.html#image
####################################################
image: "node:latest"
####################################################
# The sequential stages of this pipeline.
# Jobs within a stage run in parallel.
# https://docs.gitlab.com/ee/ci/yaml/README.html#stages
####################################################
stages:
- metadata_scan
- apex_scan
####################################################
# Metadata Scanning Phase
####################################################
metadata_scan:
stage: metadata_scan
allow_failure: false
script:
- install_salesforce_cli
- install_lightning_flow_scanner
- scan_metadata
artifacts:
paths:
- metadata-scan-files/
when: always
####################################################
# Helper Methods
####################################################
.sf_helpers: &sf_helpers |
function install_salesforce_cli() {
# Salesforce CLI Environment Variables
# https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_cli_env_variables.htm
# By default, the CLI periodically checks for and installs updates.
# Disable (false) this auto-update check to improve performance of CLI commands.
export SF_AUTOUPDATE_DISABLE=false
# Set to true if you want to use the generic UNIX keychain instead of the Linux libsecret library or macOS keychain.
# Specify this variable when using the CLI with ssh or "headless" in a CI environment.
export SF_USE_GENERIC_UNIX_KEYCHAIN=true
# For force:package:version:create, disables automatic updates to the sfdx-project.json file.
export SF_PROJECT_AUTOUPDATE_DISABLE_FOR_PACKAGE_VERSION_CREATE=true
# Install Salesforce CLI
npm install @salesforce/cli --global
# Output CLI version and plug-in information
sf update
sf --version
sf plugins --core
}
#Install the flow scanner plugin - it is not digitally signed so we need to echo y to accept the prompt.
function install_lightning_flow_scanner() {
echo 'y' | sf plugins:install lightning-flow-scanner
}
# Function to run the metadata scan on the current branch
function scan_metadata() {
local OUTPUT_DIRECTORY=metadata-scan-files
mkdir -p $OUTPUT_DIRECTORY
sf flow:scan --failon error --config "scanner-config.json"
}
RubenHalman
nvuillam
jorgesolebur
Good evening! I've implemented flow scanner on both a gitlab pipeline and my local windows machine, and I cannot get the scanner to return a status code of 1 when using the --failon command.
I run the following command:
sf flow:scan --failon error --config "scanner-config.json"And it returns:
But does not seem to throw a status code of 1 - I have tried reducing the loglevel down to warning but still no luck.