It would be super helpful if I could create concurrency_groups that include environment variables or meta-data. We often have parameterized pipelines where the concurrency only matters for jobs using the same env var value. Currently all jobs in the pipeline have to wait even if a job using different (non-impacting) parameters has the lock.
Probably, but it would be nice to keep it simple and not need it. Especially since we can reference env vars in conditionals and elsewhere in a pipeline yaml. I’ll try the dynamic pipeline work around for now though, thanks!