appdome/Appdome build-2secure

Appdome Build-2secure in GitHub

Trust Signals

workflow.ymlSHA-pinned

uses: appdome/github_build-2secure@01a741e335256e03ffd22228d4543a97d070c5fa # 1.9.3

tags can be moved; commit SHAs can't. why a SHA?

name	description	required	default
APPDOME_API_TOKEN	Appdome API key	yes	None
APP_FILE	APK file	yes	None
FUSION_SET_ID	Appdome FusionSetId iOS/Android	yes	None
SIGN_OPTIONS	iOS/Android Signin option	yes	—
KEYSTORE_FILE	Keystore sign file	no	None
MOBILE_PROVISION_PROFILE_FILE	iOS sign file	no	None
ENTITLEMENTS_FILE	iOS sign file	no	None
KEYSTORE_PASSWORD	Keystore password sign file	no	None
KEYSTORE_ALIAS	keystore alias	no	None
KEYSTORE_KEY_PASSWORD	keystore key password	no	None
SIGN_FINGERPRINT	signing sha1 fingerprint	no	None
GOOGLE-PLAY-SIGNING	Google Play App Signing program	no	false
GOOGLE_PLAY_SIGNING	Google Play App Signing program	no	false
CERTIFICATE_FILE	Certificate sign file	no	None
CERTIFICATE_PASSWORD	Certificate password sign file	no	None
TEAM-ID	your team-id	no	None
TEAM_ID	your team-id	no	None
BUILD_WITH_LOGS	whether build with logs or not	no	false
SECOND_OUTPUT	Should there be a second universal apk output (for aab apps)?	no	false
OUTPUT_APP_NAME	Specify a name for the output app (without the extension)	no	None
BUILD_TO_TEST	Build to test option (e.g., bitbar, browserstack, lambdatest, saucelabs, aws_device_farm, perfecto, tosca, firebase, kobiton katalon)	no	None
FIREBASE_APP_ID	App ID in Firebase project (required for Crashlytics)	no	None
DATADOG_API_KEY	Data Dog API_KEY (required for DataDog Deobfuscation)	no	None
DYNAMIC_CERTIFICATES	Dynamic certificates zip file for cert pinning	no	None
UPLOAD_ARTIFACTS	Choose if Action Upload Generated Artifacts	no	true
ARTIFACT_APP_SUFFIX	Append OUTPUT_APP_NAME to artifact name	no	false

no outputs