No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

but not Gitlab with kubernetes executors :disappointed:

Really? I don’t recall seeing that limitation

There was some caching with help of S3 where some paths are copied to object storage at the end of the job, but that is slow so we dont run it :slightly_smiling_face:

<https://gitlab.com/gitlab-org/gitlab-runner/issues/1906> - strange they didn’t add it given how much they talk about k8s

they dont use k8s internally *at all*, with no dogfooding using gitlab on k8s is a pain

If you can, look into <http://CodeFresh.io|CodeFresh.io> as a CI/CD solution. It’s obviously not a real recommendation as a fix for your issue, just saying we’re trialing it out ourselves right now, works nicely. As far as solving your issue, do you have many different repos with pulumi code in it?

Nah, doesn't worth a change. Yet another YAML code, they are all the same. I'll switch CI/CD once somebody introduces pipeline description as a code, I need DAG, not just YAML with implicit schema. Microsoft's Brigade is a step in the right direction