showcase.html

---
title: Showcase
id: showcase
layout: default
sectionid: showcase
---
{% include header-banner.html %}

<div class="container">
    <div class="row">
        <div class="col-sm-12">

            <h2 class="no-top-margin">Showcase</h2>
            <p>
            Need a peek of what Swingletree looks like? Find a collection of screenshots below.
            </p>


            <h3 class="underline">Build reports</h3>
            <p>
                Swingletree can persist build reports to ElasticSearch, making it possible to generate custom build reports using Kibana or Grafana (see below).
                Build reports can also be viewed and searched using the Swingletree web-interface.
            </p>
            <p>
                <img class="showcase img-thumbnail" style="max-width:75%" src="assets/images/build-overview.png" alt="Swingletree build overview" />
            </p>

            <div class="separator"></div>

            <h3 class="underline">Grafana Dashboards</h3>
            <p>
                Configure your Dashboards to your liking using Grafana
            </p>
            <p>
                <img class="showcase img-thumbnail" style="max-width:75%" src="assets/images/grafana-dashboard.png" alt="Swingletree build overview" />
            </p>

            <div class="separator"></div>

            <h3 class="underline">Check Pull Requests</h3>
            <p>
                SonarQube findings are annotated and updated inside your Pull Requests.
                If the built-in SonarQube Branch Analysis quality gates are not fulfilled,
                the Pull Request can be blocked from merging.
            </p>

            <p>
                <img class="showcase img-thumbnail" style="max-width:75%" src="assets/images/pr-merge-block.png" alt="" />
            </p>

            <div class="separator"></div>

            <h3 class="underline">Code Annotations</h3>
            <p>
                Swingletree annotates the code inside the Pull Request with the SonarQube findings. Developers do not
                have to leave GitHub.
            </p>

            <p>
                <img class="showcase img-thumbnail" style="max-width:75%" src="assets/images/pull-request-files.png" alt="" />
            </p>

            <div class="separator"></div>

            <h3 class="underline">Check Runs</h3>
            <p>
                Posting and deleting analysis results as comments into the Pull Request conversation clutters
                the discussion and may lead to misunderstandings due to automated deletions.
                Swingletree uses GitHub Checks to inform users about the status of their Pull Request,
                which is a more fitting way of pointing out issues.
            </p>
            <p>
                <img class="showcase img-thumbnail" style="max-width:75%" src="assets/images/swingletree-check-run.png" alt="" />
            </p>
        </div>
    </div>
</div>