# Uploading a file via dynamic URL

Similar to [uploading a file via URL](https://cicd-docs.gitbook.io/docs/how-to/uploading-a-file-via-a-url), you can also upload your files by passing the URL of the build and release definition files all via the address bar.

![](https://534879326-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LMlY6_3lslz22cVc3_a%2F-LMqZil4q__-4WB2nqKX%2F-LMq_3zFhmuB5aDLT86A%2Fupload-via-dynamicurl-v1.png?alt=media\&token=e49d1201-bd68-4ce7-94db-9bf936f2017d)

As highlighted in the picture above, you would notice, the URL of the build definition is mentioned after the key "buildjson" followed by an ampersand (&) and then the key "releasejson" followed by the URL of the release definition file.

Therefore, the format would be:

> ### Format:
>
> <https://clydedz.github.io/cicd-docs/?**buildjson**=(URL> of the build definition file)&**releasejson**=(URL of the release definition file)

And the example pictured above, uses the following URL. Feel free to give it a go!

> ### Example:
>
> <https://clydedz.github.io/cicd-docs/?buildjson=https://raw.githubusercontent.com/ClydeDz/cicd-docs/master/samples/build/sample-build.json&releasejson=https://raw.githubusercontent.com/ClydeDz/cicd-docs/master/samples/release/sample-release.json>

{% hint style="info" %}
**Note:** You don't have to have URLs of both - the build and release definition - files. You may supply any one if you'd like.
{% endhint %}

As with the other ways to upload a file, after a successful upload, you would be able to visualize your Azure DevOps pipeline.

![](https://534879326-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LMlY6_3lslz22cVc3_a%2F-LMqXIJhozECV_g5VHUI%2F-LMqXOca2e6XhxM8wrrK%2Fbuild-view-v1.png?alt=media\&token=b558b169-3b3b-4f8f-bb7a-7785548f6009)