"Execute in place" support for cirrus-cli about cirrus-cli HOT 2 OPEN

Hey @anarazel,

It will be a bit hacky but you can specify a persistent_worker instance instead whatever you use right now:

task:
  persistent_worker:
  script: touch test.txt

In this case cirrus run --dirty will just shell out things.

In general, I think we can add an option to override instance types from command lines.

from cirrus-cli.

It will be a bit hacky but you can specify a persistent_worker instance instead whatever you use right now:

Nice, that mostly does work.

One thing I noticed while playing with that is that cirrus run doesn't seem to deal with env: CIRRUS_WORKING_DIR: ... in the task? Is that expected? I'd have expected that cirrus run would copy the working directory there...

In general, I think we can add an option to override instance types from command lines.

That'd be very useful. An alternative could be a flag to indicate that cirrus-cli is already in the target environment.

from cirrus-cli.