Config was parsed correctly but no tasks were found!

[AlexWayfer]

AlexWayfer/flame-cli#57

Probably because of cirruslabs/cirrus-ci-docs#689

[edigaryev]

Please take a look at the CLI's version 0.19.0 that was just released, it should support .cirrus.yaml now.

[AlexWayfer]

Sorry, but I can't confirm:

> sudo cirrus --version
cirrus version 0.20.1-unknown

> sudo cirrus run
2020/12/03 01:31:01 Config was parsed correctly but no tasks were found!
Error: run failed
2020/12/03 01:31:01 run failed

> ls -lah .cirrus.yaml
-rw-r--r-- 1 alex alex 3.1K Dec  3 01:28 .cirrus.yaml

[edigaryev]

Sorry, but I can't confirm:

> sudo cirrus --version
cirrus version 0.20.1-unknown

> sudo cirrus run
2020/12/03 01:31:01 Config was parsed correctly but no tasks were found!
Error: run failed
2020/12/03 01:31:01 run failed

> ls -lah .cirrus.yaml
-rw-r--r-- 1 alex alex 3.1K Dec  3 01:28 .cirrus.yaml

Looks like you have some only_if conditions in your .cirrus.yaml that don't get evaluated to true. This results in parser skipping those tasks.

You can try supplying the missing environment variables to make this work:

cirrus run -e CIRRUS_BRANCH=master

[AlexWayfer]

Sorry, but I can't confirm:

> sudo cirrus --version
cirrus version 0.20.1-unknown

> sudo cirrus run
2020/12/03 01:31:01 Config was parsed correctly but no tasks were found!
Error: run failed
2020/12/03 01:31:01 run failed

> ls -lah .cirrus.yaml
-rw-r--r-- 1 alex alex 3.1K Dec  3 01:28 .cirrus.yaml

Looks like you have some only_if conditions in your .cirrus.yaml that don't get evaluated to true. This results in parser skipping those tasks.

You can try supplying the missing environment variables to make this work:

cirrus run -e CIRRUS_BRANCH=master

OK, thank you! Sorry, forgot about this.