Hello! I am Slava, Lead SWE at <loka.com>. I was e...
# welcome
b
Hello! I am Slava, Lead SWE at loka.com. I was experimenting with Pants last week, and was impressed! Well done, and thanks for your contributions to OSS! I am trying to optimize development process for projects we do for our clients, and currently investigating trunk-based development style with monorepos and believe it can be a huge productivity booster for my teams. As for tech stack most of the time we use Python, NodeJS (TypeScript), AWS CDK/Terraform, Golang. Before we had multi-repo setups for our projects with language-native build tools, and if monorepo was configured - it was just Makefiles and custom bash/python scripts. I have created a monorepo powered by pants, GitHub Actions, and S3 remote cache. After I tried Bazel last time, it was a huge relief using pants! Unfortunately, I haven't tried it yet at a large codebase, because bumped into CD integration issues. Could community share some opinions on Continuous Deployment Delivery patterns with pants-monorepo (or monorepos in general)? Multiple IaC tools, multiple projects, deploy changes only. Thanks in advance!
👋 3
👋🏻 1
Some context of what I thought about: depend on build docker tags at terraform as
--var
with custom scripts (not found the other way yet nor a way to run terraform/cdk commands as init/plan/apply within pants's terraform backend environment) release do shared sandbox/dev environment on each PR (use GitHub environments) and update
sandbox
tag after successful deployment Deploy to staging and production using GitHub releases, use the same tagging mechanism
f
I don't have a huge experience with continuous delivery patterns with Pants specifically, so I'm not deeply experienced there. Maybe it would be good to put this in #general so more eyes could see the question (I believe many people may mute #welcome)