Allow Deploy Scripts as a provider, rather than hijacking the whole deploy process
Here's my scenario:
I'm trying to deploy an Azure Functions / ARM template project to Azure. Currently the best way that I've been able to do this is to
1. Push my code to a github branch just for deployment
1. Provision the Azure resources by executing the powershell script ARM template. Part of the functions deployment requires a Git URL and branch. I have not been able to get the standard web deploy packages to deploy successfully with Azure Functions as of yet. The tooling feels rather immature
I'd love to be able to do this with a script provider, rather than having to put conditional if logic in the `deploy_script` section which totally makes all the awesome deployment options that you have already not able to be used (like being able to deploy on tags!)
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
1 Posted by Ilya Finkelshte... on 05 Sep, 2017 07:47 PM
Hi Ken,
We plan to implement script-based Deployment Environment. For now if you need to decouple script-based deployment from the build, you can use deployment project.
If you need to run your deployment script only on tags, you can simple add something like this in the beginning of the script:
IF (!$env:APPVEYOR_REPO_TAG) {return}
Ilya.
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:19 AM.