Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Travis Build Failure monitor(ing) #469

Closed
wants to merge 7 commits into from

Commits on May 18, 2020

  1. [Gemfile] Update travis

    NickLaMuro committed May 18, 2020
    Configuration menu
    Copy the full SHA
    dad56ec View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    23487ec View commit details
    Browse the repository at this point in the history
  3. Add TravisV3Client

    A small Travis API client library that is a compliment to the `travis`
    gem, but allows the use the v3 API endpoints for specific calls with the
    v2 based client library entities.
    
    Currently implements two methods:
    
    * `.repo_branch_builds`:  Fetch a collection of builds from a branch
    * `.repo_build`:          Fetch a singular build via ID
    
    For the second, the client actually still uses the v2 API, but doesn't
    use the default model's `.builds.first` approach (doesn't filter/fetch
    properly), and just fetches using the `find_one` interface.
    NickLaMuro committed May 18, 2020
    Configuration menu
    Copy the full SHA
    c4a7323 View commit details
    Browse the repository at this point in the history
  4. Add BuildFailureNotifier lib

    This class is a service class in charge of the logistics of sending a
    message to a configured gitter channel for a given repo, notifying there
    has been a failure.
    NickLaMuro committed May 18, 2020
    Configuration menu
    Copy the full SHA
    945c53b View commit details
    Browse the repository at this point in the history
  5. [Branch] Add build failure concept

    Use the Branch record to keep track of build failures that we find when
    polling the Travis API.  The main purpose is to avoid spamming gitter
    with extra notifications, but also can be used to identify that a branch
    has previously been broken and now has been fixed.
    
    Makes sense to also notify on the passing cases so others aren't taking
    the time to investigate a failure when this has already been
    investigated/fixed by another.
    NickLaMuro committed May 18, 2020
    Configuration menu
    Copy the full SHA
    c550b0a View commit details
    Browse the repository at this point in the history
  6. Add TravisBranchMonitor

    Worker that is in charge of monitoring Travis for build_failures, and
    will create BuildFailure records and send messages to gitter as needed.
    NickLaMuro committed May 18, 2020
    Configuration menu
    Copy the full SHA
    b7440e6 View commit details
    Browse the repository at this point in the history
  7. [rake] Add travis_branch_monitor:poll_single

    A task for triggering a single run of the TravisBranchMonitor without
    needing sidekiq running.
    NickLaMuro committed May 18, 2020
    Configuration menu
    Copy the full SHA
    d68b6a4 View commit details
    Browse the repository at this point in the history