|
Sorry, I'm just coming up to speed on BuildBot in response to your question. There are a lot of tools out there, so apologies if I am misinformed. Okay. From my quick reading, BuildBot is a nice way to run your tests in parallel. It also has Jenkins-like dependencies, where a successful build can trigger another build. In Conducto, these parallel and serial steps aren't broken apart, they are combined into a single tree. The tree lets you compose these steps to do bigger and more sophisticated tasks, all within a single build. Check out https://medium.com/conducto/cant-teach-an-old-dag-new-tricks... for more details. This makes it easy to chain together steps like "Build my artifacts", then "Test them", then "Deploy my app", where each of the steps has more detail. Also, Conducto has a big focus on debugging that I don't see in BuildBot. In my experience, debugging new features is a major productivity bottleneck for developers, and we built Conducto to make it easy to reproduce errors and solve them quickly, even in long-running pipelines. I'll keep reading, these are my first thoughts. |