> For the complete documentation index, see [llms.txt](https://docs.connect.jfrog.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.connect.jfrog.io/features-new-ui/deployments/update-deployment/set-application-and-version.md).
# Set Deployment Tag & Version
In JFrog Connect, deployment tags and their versions serve as a user-defined version control of the software updates deployed to your devices.
## Deployment Tagging Concept
Version control of software updates on thousands of devices in your fleet can be very difficult. The tagging concept in JFrog Connect provides a simple yet powerful way to keep track of your deployments.
In Connect, you can create a deployment tag. When you create a software deployment, you will use the tag name along with a version number as a way to associate software in the update with the devices the update is deployed to. This enables you to always know exactly which code (i.e., deployment tag and version) is running on a specific device. You can also filter devices by deployment tag and execute commands based on the filter used.
### Example
An example would be a product that includes four different services running on the device simultaneously. To utilize the tagging concept, mark each service of your product with a deployment tag. When you update one of the services, simply define the new version of that service as the version of your deployment tag. This will enable you to know which version of the software exists on each device.
## Set Deployment Tag and Version
You set your deployment tag and version when you [configure a new deployment](/features-new-ui/deployments/update-deployment.md). To set the deployment tag, do the following:
1. In the New Deployment wizard, select the devices for the software update.
2. Mark **Set Deployment Tag and Version** and choose a tag from the dropdown list. If your deployment tag does not appear in the list, you can choose **Add New Deployment Tag**. Once you have created the new deployment tag, it will appear in the list.
3. Enter a version for the deployment tag that you chose.
4. (Optional) Schedule the deployment, set an alert upon failure, and add a comment to help you identify the deployment.
5. Run the deployment.
When you create the new deployment, the deployment tag and version will be associated with the devices that you chose.
## What’s Next?
Learn how to [View Deployment Progress](/features-new-ui/deployments/update-deployment/view-deployment-progress.md).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.connect.jfrog.io/features-new-ui/deployments/update-deployment/set-application-and-version.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
