Expose the current source control revision to deployment scripts

[jrusbatch]

It would be convenient for Kudu to expose the checksum that represents the revision being deployed to deployment scripts. In my particular circumstance, I would like to inject the checksum into my application's config file during the deployment.

[mwtian-zz]

Have you tried SCM_COMMIT_ID in your deployment script?

[davidebbo]

Oh, great, I didn't know we had done that! Can you add it to https://github.com/projectkudu/kudu/wiki/Configurable-settings?

[davidebbo]

Actually, it doesn't quite belong on that page as it's not a setting. We should find the right place to doc it.

[jrusbatch]

Perfect, thanks!

On Wednesday, June 18, 2014, David Ebbo notifications@github.com wrote:

Actually, it doesn't quite belong on that page as it's not a setting. We
should find the right place to doc it.

—
Reply to this email directly or view it on GitHub
#1212 (comment).

[mwtian-zz]

Maybe create a new wiki entry called "Deployment Environment" or "Writing Custom Deployment Script", and document all the environement variables we provide including SCM_COMMIT_ID?

[davidebbo]

Agreed, that's the way to go. Current page are the settings you can set from the outside, and we need the things that you can use inside the script.

[mwtian-zz]

@jrusbatch No problem! @davidebbo I will start a "Deployment Environment" page.