Uploading builds from your Pipelines in Azure DevOps to Buildstash is easy.<h2>Create your application API token</h2><ol class="steps-list"><li>Create API token In your application settings, navigate to the “Connections” tab, and select “New Token”.<img src="https://uploads.productlane.com/afdce0f579b7c876c74a5fd3cc04ada6.png">Call the token anything you like - ideally something that helps you remember where it’s being used (like "Azure DevOps").</li><li>Safely store for use Your new API token will be shown.<img src="https://uploads.productlane.com/e556971579da43ff15f9f8f8b3d166eb.png">Note this is the only time the token will be shown, so be careful to record it securely (like in a password manager).</li></ol><h2>Install Buildstash extension to your organization</h2><ol class="steps-list"><li>Find Buildstash extension in marketplace<img src="https://uploads.productlane.com/89840168d61e245fc13407f2c4c368d8.png"> Go to the <a href="https://marketplace.visualstudio.com/items?itemName=Buildstash.buildstash-tasks" target="_blank" rel="noopener noreferrer nofollow" class="cursor-pointer box-border font-semibold border-b hover:border-b-[2px] transition-all duration-75 " style="text-decoration: none; color: inherit; border-color: var(--portal-accent-color);">Buildstash extension in the Visual Studio Marketplace for Azure Pipelines</a>.Select "Get it free" to install.</li><li>Install on your organization<img src="https://uploads.productlane.com/f2f163a9e693b36d1ca51acd49a40fdf.png">Select the organization you'd like to install the extension on from the dropdown. Alternatively, if you're using Azure DevOps Server, select "Download".</li><li>Extension will be installed<img src="https://uploads.productlane.com/3ebe45d033ed02585ca49ecd98bf909b.png">Once the extension is installed you'll be able to proceed to using it in your pipelines.</li></ol><h2>Add Buildstash action to your pipeline</h2><ol class="steps-list"><li>Add BuildstashUpload task to your .yml You can copy and paste the provided code into your pipeline yaml script. Set your file paths, platform, stream, and version fields as applicable.See further down for a full list of inputs with descriptions.<pre class="relative language-yaml"><code class="language-yaml relative">-<text> </text>task:<text> </text>BuildstashUpload@1<text>
 </text>displayName:<text> </text>Upload<text> </text>to<text> </text>Buildstash<text>
 </text>inputs:<text>
 </text>apiKey:<text> </text>$(BUILDSTASH_API_KEY)<text>
 </text>structure:<text> </text>'file'<text>
 </text>primaryFilePath:<text> </text>'example.exe'<text>
 </text>versionComponent1Major:<text> </text>'1'<text>
 </text>versionComponent2Minor:<text> </text>'0'<text>
 </text>versionComponent3Patch:<text> </text>'1'<text>
 </text>versionComponentExtra:<text> </text>'beta'<text>
 </text>versionComponentMeta:<text> </text>'2024.12.02'<text>
 </text>customBuildNumber:<text> </text>'12345'<text>
 </text>platform:<text> </text>'windows'<text>
 </text>stream:<text> </text>'default'<text>

 </text># Optional CI info<text>
 </text>ciBuildDuration:<text> </text>'15m30s'<text>

 </text># Optional VC info<text>
 </text>vcHostType:<text> </text>'git'<text>
 </text>vcHost:<text> </text>'github'<text>
 </text>vcRepoName:<text> </text>$(Build.Repository.Name)<text>
 </text>vcRepoUrl:<text> </text>$(Build.Repository.Uri)<text>
 </text>vcBranch:<text> </text>$(Build.SourceBranchName)<text>
 </text>vcCommitSha:<text> </text>$(Build.SourceVersion)<text>
 </text>vcCommitUrl:<text> </text>$(Build.Repository.Uri)/commit/$(Build.SourceVersion)</code></pre></li><li>Add API key as a secret variable<img src="https://uploads.productlane.com/bd10450dc458c2118a6a268ac0baa7ef.png">When editing your Pipeline, go to "Variables" and add a new variable. To match the sample code above, call the API key BUILDSTASH_API_KEY, paste in your previously generated key, and ensure you select "Keep this value secret".Note, the API key is application-specific, i.e. matched to one application in Buildstash. So you'll want to generate a unique API key for each pipeline and application.</li><li>Tweak timeout value if needed By default Azure DevOps will timeout jobs after 60 minutes.This is probably fine, but if you are uploading a particularly massive build, or have a slow connection, you may wish to tweak this.This is done on the job as below:<pre class="relative language-yaml"><code class="language-yaml relative">jobs:- job: TesttimeoutInMinutes:<text> </text>60<text> </text># how long to run the job before automatically cancelling in minutes - increase if needed for large uploads</code></pre>Refer to <a href="https://learn.microsoft.com/en-us/azure/devops/pipelines/process/phases?view=azure-devops&amp;tabs=yaml#timeouts" target="_blank" rel="noopener noreferrer nofollow" class="cursor-pointer box-border font-semibold border-b hover:border-b-[2px] transition-all duration-75 " style="text-decoration: none; color: inherit; border-color: var(--portal-accent-color);">Azure docs for more detail</a>.</li><li>Use outputs if needed Once the build is successfully uploaded, some useful information is provided by the task as outputs. For example, the URL to download the build directly. See below for a full list of outputs.</li><li>Run pipeline, and start seeing builds in Buildstash!<img src="https://uploads.productlane.com/fdb72674f9683521b79329d66b246af3.png">Successful Pipeline runs will now be sending your builds into Buildstash, giving you seamless management, organization, and distribution of your builds.</li></ol><h1></h1><h2><a href="https://docs.buildstash.com/integrations/ci/github#inputs" target="_blank" rel="noopener noreferrer nofollow" class="cursor-pointer box-border font-semibold border-b hover:border-b-[2px] transition-all duration-75 " style="text-decoration: none; color: inherit; border-color: var(--portal-accent-color);">​</a>Inputs</h2>A breakdown of all required and optional inputs for the Buildstash upload task.<table style="min-width: 278px"><colgroup><col style="width: 175px"><col style="width: 78px"><col style="min-width: 25px"></colgroup><tbody><tr><th colspan="1" rowspan="1" colwidth="175">Input Name</th><th colspan="1" rowspan="1" colwidth="78">Required?</th><th colspan="1" rowspan="1">Description</th></tr><tr><td colspan="1" rowspan="1" colwidth="175">apiKey</td><td colspan="1" rowspan="1" colwidth="78">Yes</td><td colspan="1" rowspan="1">Application specific API Key, should be stored and pass in as a secret</td></tr><tr><td colspan="1" rowspan="1" colwidth="175">structure</td><td colspan="1" rowspan="1" colwidth="78">Yes</td><td colspan="1" rowspan="1">Structure type. Either <code class="inline-code-shadow bg-gray-100 border border-gray-200/60 dark:border-gray-800 font-medium dark:bg-gray-700/60 text-gray-700 dark:text-gray-200 font-mono text-md px-1 py-0.5 rounded-[0.2rem] [&amp;::before]:content-none [&amp;::after]:content-none">file</code> (for single file build) or <code class="inline-code-shadow bg-gray-100 border border-gray-200/60 dark:border-gray-800 font-medium dark:bg-gray-700/60 text-gray-700 dark:text-gray-200 font-mono text-md px-1 py-0.5 rounded-[0.2rem] [&amp;::before]:content-none [&amp;::after]:content-none">file+expansion</code> (for a primary build file with a single expansion file, i.e. apk + obb)</td></tr><tr><td colspan="1" rowspan="1" colwidth="175">primaryFilePath</td><td colspan="1" rowspan="1" colwidth="78">Yes</td><td colspan="1" rowspan="1">Path to the primary file to upload</td></tr><tr><td colspan="1" rowspan="1" colwidth="175">expansionFilePath</td><td colspan="1" rowspan="1" colwidth="78">No</td><td colspan="1" rowspan="1">Path to an expansion file to be paired with primary (optional)</td></tr><tr><td colspan="1" rowspan="1" colwidth="175">versionComponent1Major</td><td colspan="1" rowspan="1" colwidth="78">Yes</td><td colspan="1" rowspan="1">Major version component</td></tr><tr><td colspan="1" rowspan="1" colwidth="175">versionComponent2Minor</td><td colspan="1" rowspan="1" colwidth="78">Yes</td><td colspan="1" rowspan="1">Minor version component</td></tr><tr><td colspan="1" rowspan="1" colwidth="175">versionComponent3Patch</td><td colspan="1" rowspan="1" colwidth="78">Yes</td><td colspan="1" rowspan="1">Patch version component</td></tr><tr><td colspan="1" rowspan="1" colwidth="175">versionComponentExtra</td><td colspan="1" rowspan="1" colwidth="78">No</td><td colspan="1" rowspan="1">Extra version component (optional). Pre-release label like ‘beta’ or ‘alpha’</td></tr><tr><td colspan="1" rowspan="1" colwidth="175">versionComponentMeta</td><td colspan="1" rowspan="1" colwidth="78">No</td><td colspan="1" rowspan="1">Meta version component (optional). Can be used to add additional metadata to your version, such as data <code class="inline-code-shadow bg-gray-100 border border-gray-200/60 dark:border-gray-800 font-medium dark:bg-gray-700/60 text-gray-700 dark:text-gray-200 font-mono text-md px-1 py-0.5 rounded-[0.2rem] [&amp;::before]:content-none [&amp;::after]:content-none">2025.01.01</code>)</td></tr><tr><td colspan="1" rowspan="1" colwidth="175">customBuildNumber</td><td colspan="1" rowspan="1" colwidth="78">No</td><td colspan="1" rowspan="1">Allows a flexible format custom build number if you have one. (Optional)</td></tr><tr><td colspan="1" rowspan="1" colwidth="175">labels</td><td colspan="1" rowspan="1" colwidth="78">No</td><td colspan="1" rowspan="1">Array of labels to attach to build (will be created if they do not already exist)</td></tr><tr><td colspan="1" rowspan="1" colwidth="175">architectures</td><td colspan="1" rowspan="1" colwidth="78">No</td><td colspan="1" rowspan="1">Array of architectures this build supports (must be supported by platform)</td></tr><tr><td colspan="1" rowspan="1" colwidth="175">ciBuildDuration</td><td colspan="1" rowspan="1" colwidth="78">No</td><td colspan="1" rowspan="1">CI build duration</td></tr><tr><td colspan="1" rowspan="1" colwidth="175">vcHostType</td><td colspan="1" rowspan="1" colwidth="78">No</td><td colspan="1" rowspan="1">Version control host type</td></tr><tr><td colspan="1" rowspan="1" colwidth="175">vcHost</td><td colspan="1" rowspan="1" colwidth="78">No</td><td colspan="1" rowspan="1">Version control host</td></tr><tr><td colspan="1" rowspan="1" colwidth="175">vcRepoName</td><td colspan="1" rowspan="1" colwidth="78">No</td><td colspan="1" rowspan="1">Repository name</td></tr><tr><td colspan="1" rowspan="1" colwidth="175">vcRepoUrl</td><td colspan="1" rowspan="1" colwidth="78">No</td><td colspan="1" rowspan="1">Repository URL</td></tr><tr><td colspan="1" rowspan="1" colwidth="175">vcBranch</td><td colspan="1" rowspan="1" colwidth="78">No</td><td colspan="1" rowspan="1">Branch name</td></tr><tr><td colspan="1" rowspan="1" colwidth="175">vcCommitSha</td><td colspan="1" rowspan="1" colwidth="78">No</td><td colspan="1" rowspan="1">Commit SHA</td></tr><tr><td colspan="1" rowspan="1" colwidth="175">vcCommitUrl</td><td colspan="1" rowspan="1" colwidth="78">No</td><td colspan="1" rowspan="1">Commit URL</td></tr><tr><td colspan="1" rowspan="1" colwidth="175">platform</td><td colspan="1" rowspan="1" colwidth="78">Yes</td><td colspan="1" rowspan="1">Platform slug (<a href="https://docs.buildstash.com/integrations/platforms" target="_blank" rel="noreferrer" class="cursor-pointer box-border font-semibold border-b hover:border-b-[2px] transition-all duration-75 " style="text-decoration: none; color: inherit; border-color: var(--portal-accent-color);">see list here for reference</a>)</td></tr><tr><td colspan="1" rowspan="1" colwidth="175">stream</td><td colspan="1" rowspan="1" colwidth="78">Yes</td><td colspan="1" rowspan="1">Stream - the exact name of the stream on your app this build will be sent to</td></tr><tr><td colspan="1" rowspan="1" colwidth="175">notes</td><td colspan="1" rowspan="1" colwidth="78">No</td><td colspan="1" rowspan="1">Build notes (optional)</td></tr></tbody></table><h2>Outputs</h2>A breakdown of outputs the task provides.<table style="min-width: 50px"><colgroup><col style="min-width: 25px"><col style="min-width: 25px"></colgroup><tbody><tr><th colspan="1" rowspan="1">Output Name</th><th colspan="1" rowspan="1">Description</th></tr><tr><td colspan="1" rowspan="1">buildId</td><td colspan="1" rowspan="1">Buildstash ID associated with the newly created build</td></tr><tr><td colspan="1" rowspan="1">pendingProcessing</td><td colspan="1" rowspan="1">Whether the build is pending additional processing on server (typically iOS or Android builds)</td></tr><tr><td colspan="1" rowspan="1">buildInfoUrl</td><td colspan="1" rowspan="1">URL to view the build information on Buildstash</td></tr><tr><td colspan="1" rowspan="1">downloadUrl</td><td colspan="1" rowspan="1">URL to download the build on Buildstash (requires authentication in workspace and permission to access build)</td></tr></tbody></table>Links<a href="https://marketplace.visualstudio.com/items?itemName=Buildstash.buildstash-tasks" target="_blank" rel="noopener noreferrer nofollow" class="cursor-pointer box-border font-semibold border-b hover:border-b-[2px] transition-all duration-75 " style="text-decoration: none; color: inherit; border-color: var(--portal-accent-color);">Buildstash on Azure DevOps Marketplace</a>

Integrations

Azure DevOps Pipelines

Guide

Get started

GitHub Actions

fastlane

AWS S3

JumpCloud

Microsoft Entra

Okta

Auth0

Docs

Buildstash