-
Why are you starting this discussion?Question What GitHub Actions topic or product is this about?General Discussion DetailsHello guys this is my first time learning and buulding CICD pipelines, im using github actions and having a weird thing happing to me right now : I made a workflow that has 2 jobs : `on: jobs: backend-tests: docker-builds: everytime after I push the commit to github it starts the flow but get stuck on what seems to be infinite queuing on the second job, the docker building one what funny is I have a second workflow that also uses docker build but it gets assigned workers instantly *note im not paying for actions , using free tier |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Hey! The issue is a simple typo in your second job. You wrote runs-on: ubunto-latest instead of ubuntu-latest (with a 'u' at the end). GitHub is stuck in a loop looking for a runner named 'ubunto' that doesn't exist. Fix that 'o' and it will start instantly! Also, make sure your indentation is correct (YAML is very picky about spaces). Here is the fixed workflow: |
Beta Was this translation helpful? Give feedback.
Hey! The issue is a simple typo in your second job. You wrote runs-on: ubunto-latest instead of ubuntu-latest (with a 'u' at the end).
GitHub is stuck in a loop looking for a runner named 'ubunto' that doesn't exist. Fix that 'o' and it will start instantly! Also, make sure your indentation is correct (YAML is very picky about spaces).
Here is the fixed workflow: