Start deployment in AppVeyor
A documented AppVeyor operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Start deployment
- POSTChanges data · Deployment
ci.appveyor.com/deployments
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which AppVeyor operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other AppVeyor operations
- Add environmentPOST · changes data
- Cancel user invitationDELETE · changes data
- Join AccountPUT · changes data
- Start build of branch most recent commitPOST · changes data
- Re-run buildPUT · changes data
- Update projectPUT · changes data
- Update environmentPUT · changes data
- Update collaboratorPUT · changes data
Questions
- Can HumDay start deployment in AppVeyor?
- Yes. This operation is published in AppVeyor's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my AppVeyor data?
- Yes — this is a POST operation, so it changes something in AppVeyor. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your AppVeyor account.
Where this came from
Read from a published API description for AppVeyor at raw.githubusercontent.com/kevinoid/appveyor-swagger/master/swagger.yaml. The description above is the provider’s own wording, not ours. Last published 2023-03-06.