Home → Support →

Deploying a pre-built package

• Edit

Lavinski

05 Dec, 2016 01:31 AM

I'd like to use a build server separate from appveyor. Ideally I'll have one package that I can push to multiple environments.

How can I do this with appharbor?

I also saw this, but there was no real direction I could gather from it.
https://support.appharbor.com/discussions/problems/1232-pushing-a-pre-built-deployment-package

1. Support Staff 1 Posted by rune on 06 Dec, 2016 08:35 AM

   

   Hi,

   I'm not aware of any integration options for prebuilt appveyor packages, but if you can make your build process work with AppHarbor it seems like you could just use their git workflow described here. That should also allow you to deploy the same source code to multiple AppHarbor applications -- similar to how you can connect a GitHub repository with multiple AppHarbor apps.

   It wouldn't leverage the already built appveyor package, but perhaps that's not an issue? Have you experienced any issues building the application through AppHarbor? Integrating appveyor's with AppHarbor using their git integration would likely still give you some of the CI benefits of appveyor.

   There are a few other options that might be worth a look, but probably requires a bit of code to fully automate:

   • AppHarbor's command line interface has a deploy command that can create a tarball and upload it to AppHarbor. This is particularly useful for prebuilt binaries, so if you can execute a script after completing the CI workflow at appveyor this seems pretty straightforward.
   • The CLI uses AppHarbor's build API, which essentially just takes a payload describing the build and location of the source code. The source code should be packaged in a tarball and you can find more information about this integration option here.

   Best,
   Rune

   • Edit