ArmorCode Release Gate ensures that code changes meet security standards before they are deployed.

When this build step runs, it will:

1. Connect to ArmorCode and request validation of your build against security policies
2. Wait for validation to complete (polling with the specified retry interval)
3. Either block the build or issue a warning based on the validation results and configured mode

For this to work properly, you need to:

1. Configure the ArmorCode API token in Jenkins credentials with ID "ARMORCODE_TOKEN"
2. Set the correct product and sub-product IDs from your ArmorCode account
3. Configure global settings under "Manage Jenkins" > "System" > "ArmorCode Configuration"