GIT tags are a simple and effective way to keep track of your code's different versions and the important quality of Git's version control. GIT Tag operation allows giving meaningful names to a specific version in the repository. Suppose Timon and Rumba decide to tag their project code so that they can later access it easily.
Creating a new Git Tag
A. Create GIT Tag in your Version Control Branch
- Log in to your AutoRABIT account.
- From the AutoRABIT home page, click and go to the VC Repo's tab.
- Select your Version Control Repository under Repository List.
- Go to the Tags tab and click on the Create button.
- In the Create Tag screen, select the VC branch from the drop-down. The branch that was registered with AutoRABIT for your Version Control repository will be populated here.
- Use the Search () button next to the Revision field to pull a list of revisions from which you can choose which revision to use in the deployment.Get Latest HEAD points out the last commit in the current checkout branch.
- Give a name for the tag and any additional info in the Message section. Click Create.
- A newly created tag will be displayed under the Tags section.
B. Create GIT Tag during Merge
Once the merge process is completed and pushed to the remote branch, AutoRABIT will create the GIT tag based on your configuration. To do so,
- From the top navigation pane, navigate to Create New > New EZ-Merge.
- On the New Merge screen, select your GIT Version Control Repository, Base Branch, and the Target Branch.
- Scroll a bit below and you can see the option: Create Git Tag. Select this checkbox.
- Give a name for the tag and any additional info in the message box.
- Fill in the remaining fields as per your convenience and click on Merge/ Validate & Merge. Once the merge process is completed, the GIT tag gets auto-created.
C. Create GIT Tag via CI Job
AutoRABIT will create the GIT tag while CI Job is triggered and is successfully build.
- Go to the New CI Job screen.
- The new CI Job screen gives the job a descriptive name in the CI Job Name field.
- Under Build, select your Version Control Systems, your Repository, and the Branch.
- Go to the Deploy section.
- Under the Deploy section, select your Destination org.
- Select the checkbox: On Successful Deployment.
- Now, select the checkbox: Run Merge Process. This allows running the merge operation automatically once the build is triggered successfully in CI Job. For merge to run, you need to select the Version Control type, source and destination branch, merge type, and how you like to resolve the merge conflicts that may arise during the merge process.
- Next, select the 'Create GIT Tag' checkbox and enter any tag message for your reference.
- Fill in other details as per your wish and click Save. When the build is triggered successfully and the merge process is run, a tag will be created based on the Project_Buildnumber.
Deployment via GIT Tag
- In the New Deployment screen, choose Tag as a dropdown in the Deployment From field.
- Select the Version Control Repository and the Tag from the drop-down.
- Choose the Destination org for your deployment.
- The Deployment Type is auto-selected to Full Deployment by default. Full Deployment transfers all objects in the source org to the destination org.
- Once you are done with the selection, click on Deploy.
- The remaining steps are similar to other deployments methods, do refer to the article: Create and Deploy Changes