Source Control Support
We currently store a lot of powershell assets (scripts modules etc) in our Source Control system. As we move our source to the cloud (GitHub, VS Online) we would like to have the ability to have a single source for this stuff rather than having to manually import into the Azure portal.
To me this is much the same as the early criticisms of Azure Mobile Services. This would be a major blocker for us in using Azure Automation
Source Control support for GitHub is now live! See http://azure.microsoft.com/en-us/blog/azure-automation-source-control-13/ for more detail.
If you need integration with a difference service or additional functionality, please file another request or add your votes to one of these existing suggestions:
VSO integration with TFS here: http://feedback.azure.com/forums/246290/suggestions/9771435
When you setup the sync for a runbook and devops you can only authenticate as yourself. Are there any plans to allow this syncronization process to take place with some other type of account? That way if an employee leaves we don't have to worry about the sync breaking.
Aaron Jones commented
@Beth It does not appear that you can create a private github repo as a user linked within a business account. This Source control integration appears to look for "user/repo" where as a business account will have the repo under "businessName/repo". No repo's are listed under "Choose Repository" after you authorize the user that has rights to that business account repos.
Cédric Blomart commented
Any ways to handle hosted git solutions (gitlab/gogs)?
Some companies are still using their own hosted git platform (for secutiry reason probably), being able to use any internet accessible git platform would be usefull.
Even if they do deliver a extraordinary service, please don't lock us on github!
JENOUVRIER Eric commented
quick question : when Source Control Support from Visual Studio Team Service will be available ?
Awesome! Great work.
Phani Tipparaju commented
Azure Automation currently does not integrate with any source control. Its totally challenging to manage scripts separately and then copy paste into the portal all the time for some serious project.
While the approach the blog post uses works, I would like to see a much tighter integration story here. Something closer to WebSites SCC integration. I connect an Azure Automation Runbook (at a runbook or account level) with some source control (Git, VSO, etc.). Then if I push to the related branch the SCC can ping the Azure Automation system with a notification and the new code is pulled and published. It would just cut out the need for the workaround.
Joe Levy (Azure Automation Team) commented
This blog post just came up which may alleviate the issue: "Azure Automation: Integrating Runbook Source Control using Visual Studio Online" (http://azure.microsoft.com/blog/2014/07/24/azure-automation-integrating-runbook-source-control-using-visual-studio-online/)
Does this unblock you?
There is a blog post around integrating Service Management Automation (Azure Automation's on-prem counterpart) and TFS: http://blogs.technet.com/b/privatecloud/archive/2014/05/08/automation-mvp-spotlight-series-tfs-and-service-management-automation-better-together.aspx
While this is not directly about Azure Automation, it provides some insight on how to integrate with a source control system.