Odin
  • Introduction
  • Why Odin?
  • Key Concepts
    • Environment
      • Environment Type
    • Provisioning
      • Provisioning Config for Component Types
    • Component
      • Available Component Types
      • Component Type reference
        • Optimus Components
          • Aerospike [6.3.0.7-1.0.0]
    • Service
      • Know Your Service Definition
    • Versioning
      • Clearing the Confusion: A Simplified Guide to Artifact, Component, and Service Versions
    • Service Sets
    • Labels
  • Reference
    • CLI reference
  • Onboard Your Service
    • Installation
    • Configure
    • Odin -h
    • Getting Started
    • Create Environment
      • Operations on Environment
    • Service Definition
    • Provisioning Config
    • Deploy Service
    • Release Service
    • Optimus Datastore Operations
      • How to use Optimus Datastore in my service?
      • RDS Operations
      • Aerospike Operations
      • Kafka Operations
    • Operating Service & Components
      • Redeploy
        • In Place Deployment
        • Blue Green Deployment
      • Rolling Restart
      • Adding & removing components
      • Revert a deployment for application component
      • Downscaling a Passive Stack
      • Updating the no. of stacks of application component
    • Dev <> QA iteration
    • Frequently Asked Questions
    • Deploy Concrete Service
    • Undeploy Service
    • Delete Environment
    • Appendix
  • How To
    • Define error threshold for canary deployment
    • Add or Remove a component in an already deployed service
    • Integrate mono-repo(cronjobs) with Odin
    • Deploy crontab with Odin
    • Integrate Data pipeline with Odin
    • Push logs to log central
    • Build artifacts for multi module applications
    • Load test with Odin
    • Track Deployments against Commit Ids
    • Deploy Service on Production - Dream11
    • How and when images are created
    • Check logs for deployed infrastructure - Dream11
    • Onboard Stepfunction as a component
    • Onboard Serverless as a component
    • Login to Kubernetes clusters
  • Release Notes
    • 1.2.0-beta.2 - 11 August, 2022
    • Odin October Release
    • Odin 1.2.0 - Nov 9th 2022
    • Odin February Release
Powered by GitBook
On this page
Export as PDF
  1. How To

Track Deployments against Commit Ids

This article details out the feature of tracking deployments against commit id

PreviousLoad test with OdinNextDeploy Service on Production - Dream11

Last updated 1 year ago

When a service is deployed in an environment, we can track the service version for the same. However, against that service's application component, there might be more than one commits in the code repository and it becomes challenging to track that the deployed version is against which commit id.

If you are using Jfrog as an artifactory, this feature will enable your users to track commit ids against the deployed application component and also monitor it post deployment.

If you are using any other artifactory than Jfrog, please reach out to us for getting the support for the same.

Feature Details

The underlying fundamental behind this feature is to tag the artefact created with property called "Commit Id". The following curl can be used to attach the commit id as a property manually against the artefact. Please note, use this curl only after you have uploaded the artefact. 

curl --location --request PUT 'YOUR_JFROG_URL?properties=commitId=YOUR_COMMIT_ID' \
--header 'Authorization: Basic <Token>'

Dream11 Use Case

In context of Dream11 who is already using Jfrog as an artefactory, this feature does not need any specific user intervention if the user is using jenkins job for creating the artifact. That means, if the artifact is being created by jenkins job, Odin will attach the property commit Id against the created artifact on its own.

Odin uses the above mentioned curl command in the backend to enable commit id capture via jenkins job.

Expected Behaviour

With this feature at place, now users can see the commit id during the deployment in the following format: