Azure Pipelines
Store QUOLLVAULT_TOKEN as a secret pipeline variable and run the CLI after producing the artifact.
yaml
- script: |
npm install --global quollvault-cli
quollvault config set api https://api.quollvault.com
quollvault config set app "$(QUOLLVAULT_APP_ID)"
quollvault config set environment "$(QUOLLVAULT_ENVIRONMENT_ID)"
quollvault upload ./build/app.apk --app-identifier "$(QUOLLVAULT_APP_IDENTIFIER)" --version "$(QUOLLVAULT_VERSION)" --build-number "$(QUOLLVAULT_BUILD_NUMBER)"
displayName: Upload to QuollVault
env:
QUOLLVAULT_TOKEN: $(QUOLLVAULT_TOKEN)QuollVault detects Azure Pipelines provenance from standard environment variables.
Prompt an agent to add Azure Pipelines upload
text
Add a QuollVault upload step to this repository's Azure Pipelines mobile-build pipeline.
Inspect the existing pipeline YAML and build output before editing. Run the upload only after the selected mobile artifact is available in the agent workspace. Install `quollvault-cli`, configure the API origin plus the App and Environment UUIDs, and upload the resolved IPA, APK or AAB path. Pass `QUOLLVAULT_TOKEN` to the step only as a secret pipeline variable. Keep App/Environment IDs and required Android application identity, version and build-number values as non-secret variables. Do not manually provide provenance metadata or print secrets.
Before editing, ask me to choose the pipeline/job and artifact when several options exist. Ask which variable group or pipeline-variable scope to use if that is not already defined, and ask for the target App/Environment and identity source whenever they are ambiguous. If the secret is not configured, tell me its required name and ask me to add it without sharing the value.
Validate the YAML and summarize the required variables and final artifact path.Common failures
Mark the token secret, verify the artifact path in the agent workspace and keep the Automation Token scoped to only the required Project/App.