Problems with artifact folder structure in vanilla FTP deployment

sebastian's Avatar


02 Dec, 2014 04:53 PM

Hi guys,

I'm trying to set up a build for a vanilla HTML site via FTP, for some simple UX staging.
I've disabled build, so that the process just checks out the files and moves straight to the artifacts step.
In the repo, I keep the site source in a 'src' folder, which is the root of the site.
I add src\**\* as an artifact to capture all files in the 'src' folder.
When I try to deploy via FTP, it's attempting to deploy (for example) to ROOT\src\index.html, instead of ROOT\index.html.
Is there a way to tell the FTP deployment to upload files from a certain artifact subpath? Or map the artifacts into another path?
In TeamCity you can do something like src\**\* => **\*.

  1. Support Staff 1 Posted by Feodor Fitsner on 02 Dec, 2014 07:40 PM

    Feodor Fitsner's Avatar

    First, you should have a single .zip artifact. To upload entire folder as a single zip remove \**\* from artifact path.

    Then use Application field to specify zip artifact name to make AppVeyor "expanding" it before publishing to FTP.

    Let me know how it goes.

  2. sebastian closed this discussion on 11 Jun, 2015 07:34 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? 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