so im interested in ways people deal with circlici trying to double up on jobs. is there a handy pulumi command I can run in a job to check if pulumi is busy and if so just abort the job?

You mean Pulumi instance

2

should fail fast if another instance

1

currently applies on the same stack? If so, also if it’s just a preview? I’m also interested in both options.

im interested in checking if something is applying before I my job applys. Can then decide if I want to cancel the old, wait till read, then go. or just cancel the new update

If you’re using the Pulumi Service backend, Pulumi will automatically exit with a message when another update is in progress on the same stack.