Feature request: script deploy environment
Hi Appveyor,
Our team is running into some issues bringing some of our more legacy projects over. Currently, those projects are built using a rake script, which determines the build targets (one of which can be a deploy target). What we want to do, is move the deploy to a separate process altogether. The issue with this approach and appveyor is that our deployment is done using that same rake script doing a POST request with multipart/form-data, with the artifact in the boundary together with some additional content disposition.
Would it be possible to add an environment where the deployment happens via a custom script? Ideally, I would love to be able to run the deployment like a build script - but for starters, I think being able to just create a deployment environment as a plain script (at least powershell) would be amazing.
Thanks!
Nero
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 20 Oct, 2016 10:25 AM
Hi Nero,
Please take a look at this https://www.appveyor.com/blog/2015/11/04/deployment-projects/ approach, maybe it will work for you.
Ilya.
2 Posted by Ted on 24 Nov, 2016 10:37 AM
It would be great to make this a high priority! :)
We're deploying to Azure Web Apps, and the value of AppVeyor would be tenfold if we could run a PS script before deploying to an Environment, to make a database copy.
Since the "runCommand" provider isn't available in Azure (I think?) we can't run it remotely. And we might also want to do some checks with the PS script, and cancel the deploy if some prerequisites aren't met.
3 Posted by nero.sule on 24 Nov, 2016 10:46 AM
I'm afraid this approach does not work for us. That process involves too much ceremony when all we need is just a deployment environment that is capable of receiving the packages, and then doing with them whatever it needs to. We don't deploy to Azure with that script, and in general we could use that single environment as a deployment point for all the projects that use the same method, because really - there's nothing stopping us from doing that. Pretty please with a cherry on top for a script deployment environment?
4 Posted by Ilya Finkelshte... on 24 Nov, 2016 07:39 PM
GitHub issue
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:09 AM.