or Create a profile
07 May, 2017 10:04 PM
I am trying to deploy to s3 with a yaml definition attached. When I do I get the results in the other attachement. I encrypted the aws access key and secret via the UI and then set them directly (removed just for the screenshots).
When I go to s3, there is no artifact there. I changed the secret key to a wrong value ('v') and I received the same results from the build.
Is there anyway to see what exactly is happening during the deploy process? logs or debug output? Now I am not sure what is wrong, maybe my secrets, or something else all together?
on 07 May, 2017 10:35 PM
To add to this, I tried defining the file as an artifact in the yaml file with:
and the output in the build looks more promising (attached) but I still cant see a file in s3.
on 07 May, 2017 10:57 PM
Define artifact as:
then in S3 deployment provider settings use msi deployment name instead of path:
- provider: S3
- provider: S3
on 08 May, 2017 04:30 PM
Oh got it. That works! Thanks.
on 08 May, 2017 09:28 PM
If I want multiple artifacts in the deploy section. Is this possible in any way?
on 08 May, 2017 09:32 PM
Sure you can have multiple artifacts and multiple deployments each for specific artifact. Easiest way to get YAML for this is to set this in UI and then use Export YAML menu.
on 09 May, 2017 12:27 AM
Ok thanks. Is there a reference or doc that shows how? I'd rather not go and fill out the UI with all the info twice.
on 09 May, 2017 12:42 AM
Here are few links you can get this information from:
But using UI to create initial template is really the fastest way.
on 09 May, 2017 01:07 AM
Ok great thanks. I did it via the UI and exported it and it created a line:
I looked through those links and others and I couldn't find this syntax anywhere. It is also not so obvious as the key is singular but the value is a comma separated list.
I created a pull request here to help clarify for people in the future.
Formatting help /
(switch to plain text)
(switch to Markdown)
You can attach files up to 10MB
If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.
A conversation has been started with the AppVeyor staff to resolve this discussion.
This discussion is private.
Only you and AppVeyor support staff can see and reply to it.
This discussion is public. Everyone can see and reply to it.
You can use Command ⌘ instead of Control ^ on Mac
Powered by Tender™.