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

Pipeline status badge endpoints for server #158

Merged
merged 8 commits into from
Feb 3, 2019
Merged

Pipeline status badge endpoints for server #158

merged 8 commits into from
Feb 3, 2019

Commits on Jan 30, 2019

  1. Fix pipeline status badge

    Some previous status manager refactoring broke the badge end point. I've
    also changed it from redirecting to the shields.io image, to proxying
    it.
    brew committed Jan 30, 2019
    Configuration menu
    Copy the full SHA
    d61030d View commit details
    Browse the repository at this point in the history

Commits on Jan 31, 2019

  1. If no pipeline_id found, still return a badge

    If no pipeline_id is found, return a badge with 'not found' written in
    it, rather than returning a 404. Knowing that a pipeline is potentially
    missing is still useful status.
    brew committed Jan 31, 2019
    Configuration menu
    Copy the full SHA
    c3fd533 View commit details
    Browse the repository at this point in the history
  2. Pipeline collection status badge

    A status badge at the /badge/collection/<pipeline path> endpoint.
    
    This returns a pipeline collection summary badge, e.g.
    
    pipelines | 22 succeeded, 14 failed, 2 invalid, 1 running
    
    Pipeline path will filter the pipeline ids it is reporting on.
    brew committed Jan 31, 2019
    Configuration menu
    Copy the full SHA
    dd669b3 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    852162b View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    c9c4513 View commit details
    Browse the repository at this point in the history
  5. Use basic auth for dashboard view, but not badges

    This commit makes application of basic auth (if active) more selective.
    Instead of forcing basic auth on all endpoints, it is now applied as a
    decorator for the main dashboard views. This allows us to serve the
    status badges without basic auth while still being able to protect the
    dashboard pages.
    brew committed Jan 31, 2019
    Configuration menu
    Copy the full SHA
    1f2fb81 View commit details
    Browse the repository at this point in the history
  6. Configuration menu
    Copy the full SHA
    744509b View commit details
    Browse the repository at this point in the history
  7. Configuration menu
    Copy the full SHA
    f727cae View commit details
    Browse the repository at this point in the history