Question

Digitalocean github app action error deployment

Posted on August 29, 2023
Deployment DigitalOcean App Platform GitHub Actions
Asked by Quenoz Alvareoe

followed the steps [from https://github.com/digitalocean/app_action](https://from https://github.com/digitalocean/app_action) but github action failed and getting this error triggering deploy: unable to create-deployment for app: exit status 1

any idea?

my app spec at .do/app.yaml

name: testapp
region: sgp
services:
- git:
    branch: main
    repo_clone_url: https://github.com/Web-Fuel-Agency-LTD/test-deploy-do.git
  http_port: 8080
  instance_count: 1
  instance_size_slug: basic-xxs
  name: web
  routes:
  - path: /

and I tested it through app platform set up and I can create the app successfully.

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Bobby Iliev

Site Moderator

• August 29, 2023

Hi there,

There are a few things that I could suggest here:

Ensure that you have set the required GitHub secrets (like DIGITALOCEAN_ACCESS_TOKEN) and they are correct. Tokens should have appropriate permissions.
Check the logs of the GitHub Action run. They might contain more details about what exactly failed. Feel free to share thos errors here in case that there are any.
Ensure there are no syntax errors in your .do/app.yaml file. Ensure that the repository and branch in the app spec match exactly with the repository and branch you are pushing to.
Try to deploy manually using the doctl command line, replicating what the GitHub Action does:
```
doctl apps create --spec .do/app.yaml
```
- If this fails, you’ll have a clearer error message directly from doctl and the context of your local machine. If it succeeds, the problem lies somewhere in the GitHub Action or its environment.