Specify path to task definitions about cirrus-cli HOT 4 CLOSED

We have a cirrus run "Task Name" to run a given task from .cirrus.yml.

Does that work for you?

from cirrus-cli.

I was about to say no, but honestly, it might. Instead of creating a yaml file for each instance, I can create a task for each instance in a single yaml file.

It's not nice, though, IMO, to be forced to use a hidden file for this. I would still like to have the ability to use a different file name, so that others can easily see what is going on in the GitHub self-hosted runner I'm building on top of cirrus.

But at least multiple tasks gets me to a single file.

from cirrus-cli.

It's not nice, though, IMO, to be forced to use a hidden file for this. I would still like to have the ability to use a different file name, so that others can easily see what is going on in the GitHub self-hosted runner I'm building on top of cirrus.

But there are lots of software out there that uses hidden files (e.g. the aforementioned GitHub uses .github/ directory for it's Actions and Git uses .gitignore) and most modern IDEs nowadays display them nicely in their file tree.

Technically it would be trivial to add support for non-standard file names in the Cirrus CLI, but please understand that it would introduce additional confusion for people migrating to the Cirrus CI from Cirrus CLI (and vice versa), because Cirrus CI only supports .cirrus.yml and .cirrus.star at the moment.

from cirrus-cli.

Okay, I understand. Thanks for your time and consideration.

from cirrus-cli.