The naming convention needed for deploys to be picked up can vary depending on the deployment tool or system you are using. However, there are some common naming conventions that are often used to ensure deploys are picked up correctly:
1. **Semantic Versioning**: Using semantic versioning for your deploy names can help organize and track different versions of your application. Semantic versioning typically follows the format `major.minor.patch`, where each part represents a different level of change in the software. For example, `v1.2.3` indicates major version 1, minor version 2, and patch version 3.
2. **Timestamps**: Including timestamps in deploy names can provide a clear indication of when each deploy occurred. Timestamps are often formatted in a way that is sortable and easily readable, such as `YYYYMMDDHHMMSS` (year, month, day, hour, minute, second).
3. **Environment Indicator**: Adding an environment indicator to deploy names can help distinguish between different environments, such as development, staging, and production. For example, you might use prefixes like `dev-`, `stage-`, or `prod-` to indicate the environment.
4. **Branch Name**: Including the name of the branch being deployed can be useful for tracking changes and debugging issues related to specific branches. This is especially relevant in continuous integration/continuous deployment (CI/CD) workflows.
5. **Release Name or Tag**: If your deployment process involves creating releases or tags in your version control system (e.g., Git), you can use the release or tag name as part of the deploy name. This helps link the deploy to a specific release or version of your application.
6. **Descriptive Labels**: Including descriptive labels or identifiers in deploy names can provide additional context about the changes included in the deploy. This might include features, bug fixes, or other relevant information.
Here's an example of a deploy name incorporating some of these elements:
```
v1.2.3-prod-20220501-143000
```
This deploy name indicates that it is version 1.2.3 deployed to the production environment on May 1, 2022, at 2:30:00 PM.
It's important to establish a consistent naming convention that works well for your team and aligns with your deployment process and tooling. Additionally, ensure that your deployment tool or system is configured to recognize and process deploy names according to your chosen convention.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.