BuildPulse
7.9#3 in ci failure analysis and flaky test toolsFree planFree planWebAPILinuxmacOS
VisitBuildPulse vs Jenkins
What both publish
| Fact | BuildPulse | Jenkins |
|---|---|---|
| Compliance | BuildPulse says SOC 2 Type I attestation is in progress and Type II is planned; Enterprise pricing lists a DPA available on request. | The Jenkins security page says the project will not provide compliance documents, certifications, or questionnaire responses. |
| Integrations | Official integrations include GitHub and Bitbucket source control, Jira issue tracking and Slack notifications. | Jenkins uses plugins to integrate with tools across the CI/CD toolchain, including source control systems such as Git, Subversion, and Perforce. |
| Security | BuildPulse says it runs on AWS in the United States and encrypts data in transit; its page describes encryption at rest for object storage and DynamoDB while saying native DocumentDB storage encryption is still being evaluated. | Jenkins documents access controls and security settings; some protections are enabled by default when the interactive setup wizard is used. |
| Support | Team includes email support, Growth includes priority email support and a dedicated onboarding session, and Enterprise includes dedicated onboarding and priority support. | Jenkins is supported by a community, and the project directs users with questions about contributing to its Newcomer and Advocacy and Outreach channels. |
BuildPulse plans
- BuildPulse RunnersFree
- Runner 2xFree
- Runner 4x$0.01, paid once
- Runner 8x$0.02, paid once
- Runner 16x$0.03, paid once
- Runner 32x$0.06, paid once
Jenkins plans
No prices published.
Pick BuildPulse if…
BuildPulse suits engineering teams tracking flaky tests, coverage, and CI activity across repositories. It may be useful to teams that want to quarantine disruptive tests without adding an SDK or test annotations.
Pick Jenkins if…
Jenkins suits software delivery teams looking for anything from a basic CI server to a configurable delivery hub. It is aimed at teams working with continuous integration, continuous delivery, and modern software delivery practices.