Hi all, I’m currently working at Unit21 on the security team. I’ve had previous experience with Bazel at other gigs and wanted to bring some of that here but pants looked easier to adopt. Currently working on adding it to a greenfield project and one existing one that my team owns in order to prove the value, then planning on presenting my findings to the rest of engineering to hopefully get it adopted elsewhere. We have a weird monolith application that’s actually split across half a dozen repos and I’d love to bring them all together under one to make cross-cutting changes and testing easier.

Nice! Yeah, Pants should be a solid choice for that. What languages are used by the codebases you'll be bringing together?

It’s all Python, we have a JS repo for the frontend as well that I’ll be leaving out of the pants monorepo.

The post might be slightly out of date by now, but may still be useful for your colleagues familiar with Bazel's strengths and weanesses. https://blog.pantsbuild.org/pants-vs-bazel/

Yeah, I’ve been ironing out some kinks with Benjy over in #general. Need a couple more things to land before it’s ready to share with my team, had a bugfix around the Go backend that got merged yesterday and I need CGO support. I think

2.15.0rc1

should be what I’m targeting if my understanding of the release process is right. I just tried porting my bugfix to the

2.15.0rc0

branch and can successfully build both projects.

You've already been contributing to the project! Thank you 🙂

I’m using the codegen feature as well in one of the projects, that was part of what motivated actually setting up pants. We have a Go server + Python client lib with gRPC as the interface between them, it’s a pretty slick setup with pants.