DOCSEARCHbyAlgolia
Submit Docs

Buildnote CI/CD Pipeline Observability

website·Indexed 32 days ago

https://buildnote.io/docs

Buildnote provides CI/CD pipeline observability and monitoring software to help engineering teams identify flaky tests and improve pipeline performance. It plugs into existing CI systems to turn raw build data into insights, featuring a CLI tool for collecting and uploading events during the build process.

Tokens
6.3K
Snippets
10
Records
57
Agent score
47%

What's inside Buildnote

  1. Overview of Buildnote CI/CD Observability Platform

    Buildnote provides CI/CD pipeline observability and monitoring software designed to bridge the gap between basic monitoring tools and expensive enterprise solutions. It specializes in pre-production environment visibility and supports test results in most available formats. Key features include seamless integration with GitHub, Slack, and Grafana, AI-powered test failure summarization, and the ability to handle file attachments alongside event data.

  2. Overview of Buildnote CI visibility features

    Buildnote integrates with existing CI environments to provide visibility into build data. Key capabilities include:

    • Pipeline Performance: Tracks execution time and failure rates across environments and branches, linking degradations to specific commits and logs.
    • Flaky Test Detection: Ranks the slowest and most failure-prone tests to identify unstable tests versus real regressions.
    • Build Timelines: Provides an end-to-end view of pipelines, jobs, and steps with durations and parallelization data to identify bottlenecks.
    • AI Insights: Automatically explains build/test failures, distinguishes between infrastructure blips and regressions, and allows plain-English querying of build data.
    • BNQL: A read-only query language used to analyze events (builds, tests, commits, deployments) for dashboards or API scripting.

  3. Overview of Buildnote CI Visibility Features

    Buildnote integrates with existing CI pipelines to provide visibility into build data. Key capabilities include:

    • Pipeline Performance: Tracks execution time and failure rates across environments and branches, linking degradations to specific commits and logs.
    • Flaky Test Detection: Ranks the slowest and most failure-prone tests to identify unstable tests versus real regressions.
    • Build Timelines: Provides an end-to-end view of pipelines, jobs, and steps with durations and parallelization data to identify bottlenecks.
    • AI Insights: Automatically explains build/test failures, distinguishes between infrastructure blips and regressions, and allows plain-English querying of build data.
    • BNQL: A read-only query language used to analyze events (builds, tests, commits, deployments) for dashboards or API scripting.

  4. Overview of Buildnote CI Visibility Platform

    Buildnote plugs into existing CI pipelines to turn raw build data into actionable insights. It tracks execution time, failure rates, and identifies flaky tests across environments and branches. Key capabilities include a build timeline for bottleneck identification, AI-powered failure analysis, and a read-only query language (BNQL) for custom data extraction.

  5. Overview of Buildnote CI Visibility Platform

    Buildnote is a tool that integrates with existing CI environments to turn raw build data into actionable insights. It tracks pipeline performance (execution time and failure rates), identifies flaky tests, provides a detailed timeline of builds (jobs, steps, and parallelization), and offers AI-powered failure analysis to distinguish between infrastructure blips and real regressions.

  6. Understand Active Submitters and Resource Allocation

    Buildnote uses the concept of an 'Active Submitter' to determine billing and resource pools.

    • Active Submitter: Any entity (e.g., a developer committing code or a process like GitHub's dependabot) that sends at least one event to Buildnote during the billing period.
    • Billing Cycle: The number of active submitters is counted monthly, ending on the last day of each month.

    Resource Pool Calculations:

    • Total Allotted Events: Active Submitters × 400k (Resets monthly).
    • Total Allotted Storage: Active Submitters × 1GB (Cumulative; only decreases when events expire after the retention period).

  7. Buildnote Pricing Plans Overview

    Buildnote offers three pricing tiers based on feature requirements and usage volume:

    • Free: Basic features for getting started. Includes event collection via integrations, build stage collection, 14-day data retention, and a limit of 25K events per day.
    • Pro: Comprehensive plan for advanced features. Includes API & CLI event collection, AI-powered features, 400-day data retention, and a limit of 1M events per day.
    • Enterprise: Custom plan for larger organizations. Offers SSO/SAML, dedicated instances, custom identity system integration, priority 24-hour support, and custom SLA commitments.

  8. Integrate Buildnote with CI Tools and Test Frameworks

    Buildnote supports a wide range of integrations to collect build and test data:

    • CI Platforms: GitHub (including a ready-made GitHub Action for the CLI) and GitLab.
    • Test Result Formats: The CLI and Gradle plugin support JUnit, xUnit, NUnit, TRX, TestNG, Cucumber, Robot Framework, CTRF, and Dart.
    • Notifications: Failure alerts can be sent to Slack or Discord.
    • AI Models: AI Insights can be powered by Anthropic, OpenAI, or Gemini.
    • Authentication: Enterprise teams support SAML SSO.

  9. Provide feedback and report errors

    Feedback, error reports, and suggestions for improvement can be sent directly to info@buildnote.io. By providing feedback, users agree that they retain no intellectual property rights to the feedback and that Buildnote may use, modify, and commercialize the feedback without obligation of confidentiality.
    Email: info@buildnote.io

  10. Get started with Buildnote free tier

    Buildnote offers a free tier for new users, providing free processing for up to 25K events per day. Users can upgrade to paid plans as their requirements for insights and volume increase.

  11. Manage personal data and exercise privacy rights

    Users can request to access, update, rectify, delete, or limit the use of their personal data. Buildnote may require identity verification before responding to these requests. For GDPR, CCPA, and CalOPPA compliance, requests should be sent via email.
    Email: privacy@buildnote.io

  12. Understand Buildnote monthly pricing and cost components

    Buildnote pricing is calculated based on four primary metrics: active submitters, volume of events, storage requirements, and AI request usage.

    Key pricing components include:

    • Submitters: Charged at a rate of £15 per submitter.
    • Events: A base volume of 2M events is included with the submitter subscription. Additional events are charged beyond this limit.
    • Storage: 5GB of storage is included with the submitter subscription. Additional storage is charged beyond this limit.
    • AI Requests: Charged based on the number of requests used.

    Note: Prices do not include taxes, levies, or duties unless otherwise stated.