Home → Questions →

Writing build version in Azure Websites (equivalent to Deployment Label?)

• Edit

todd

09 Jan, 2015 03:39 PM

Hi,
I have a few Azure Cloud Services and Websites. My deployment scripts are able to read the build version for the Cloud Services, thanks to your slick feature that writes them to the Deployment Label. Curious if there is some equivalent to this for Websites? Some property I could read via PowerShell or the management API that contains (or could contain) the build version?

I've enabled AssemblyInfo.cs patching and I'm going down the path of exposing an HTTP endpoint on the sites themselves (/version) that I can read from the script. Should work, feels like sort of a hack.

Thanks in advance!

1. Support Staff 1 Posted by Feodor Fitsner on 09 Jan, 2015 07:54 PM

   

   Azure Websites are being published with Web Deploy which AFAIK doesn't have a proper way of attaching some meta info. Maybe be having /version endpoint is not a bad idea (or injecting version number into HTML meta of home page?).

   • Edit

2. 2 Posted by todd on 09 Jan, 2015 10:53 PM

   

   Thanks! Thought that was the case wanted to make sure I wasn't missing anything obvious. I went with `/version` endpoints and it's working well.

   • Edit

3. 3 Posted by Adam Webb on 28 Oct, 2015 10:17 PM

   

   I came across the same limitation when we moved our solution from Azure cloud services to web apps, plus still have not found any further verification if there is an OOTB solution.

   One solution that I have implemented is to create a "version" tag, which can then be assigned to the relevant Azure resource and deployment slot. These tags can then be easily read via scripts or whatever automation services you implement. From testing, the tags do not get swapped with deployment slots, but that is easy enough to automate, if desired.

   • Edit

4. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:01 AM.