Permalink
Branch: master
Commits on Jan 22, 2019
  1. Release 0.6.4 (#384)

    ale7714 committed Jan 22, 2019
Commits on Jan 18, 2019
  1. Skip unknown files and warn (#382)

    ale7714 committed Jan 18, 2019
Commits on Oct 30, 2018
  1. Update README.md (#372)

    davehenton committed Oct 30, 2018
    * Update README.md
    
    removes duplicate/confusing installation instructions
    
    * Update README.md
    
    * Update README.md
    
    * Update README.md
Commits on Sep 20, 2018
  1. Remove cobertura.ser from Cobertura searchPaths (#365)

    ale7714 committed Sep 20, 2018
    Our current Cobertura parser supports XML format only.
Commits on Sep 5, 2018
  1. Update release strategy and migrate to circle 2 (#355)

    ale7714 committed Sep 5, 2018
    * Update building strategies
    
    * We will build natively OS X binaries so it uses
      the system  DNS resolver
    * For Linux, we will compile 2 binaries:
      * One with CGO disabled (which is how our current binary
        behaves)
      * One with CGO enabled and that forces the use of CGO for
        DNS resolution
    
    * wip: circle 2.0
    
    * update circle
    
    * bump version to 0.6.3
    
    * Add comment on make release
Commits on Jul 31, 2018
  1. Release 0.6.2 (#351)

    ale7714 committed Jul 31, 2018
    * Update docs
  2. Support multiple jacoco source paths. (#348)

    atoulme authored and ale7714 committed Jul 31, 2018
  3. Release v0.6.1

    dblandin committed Jul 31, 2018
    * [FIX] Support clover `path` attribute on file nodes in XML report [#349][]
    
    [#349]: #349
  4. Support clover `path` attribute on file nodes in XML report

    dblandin committed Jul 30, 2018
    The XML report generated by more recent versions of clover include the
    full path to the file within a `path` attribute. The `name` attribute in
    these reports contains just the filename without any directory
    structure.
    
    To support reading the source file, we'll need to reference this new
    attribute.
Commits on May 21, 2018
  1. Release v0.6.0 (#339)

    ale7714 committed May 21, 2018
    * [FIX] Update `Gcov` formatter to report the correct source file paths [#338][]
    
    [#338]: #338
  2. Fix gcov formatter (#338)

    ale7714 committed May 21, 2018
    * Fix gcov formatter
    
    * Adds getSourFileName. Formatter will parse from coverage file
      the source file name, use it to create the SourceFile and
      then, add it to the Report.
    
    * Updates specs and fixtures so we ensure that we're returning
      actual source file names and not coverage file names.
    
    Addresses #328
    
    * Add test-gcov to Makefile
Commits on May 16, 2018
  1. Release v0.5.2

    chrishulton committed May 15, 2018
    * [FIX] Update `Cobertura` formatter to ignore invalid line numbers in a
      `cobertura.xml` file #335
Commits on May 15, 2018
  1. Ignore invalid lines in cobertuna formatter

    ale7714 authored and chrishulton committed May 14, 2018
    This prevents the test reporter from crashing when an invalid line
    number is detected in the cobertuna.xml coverage file.
    
    While this does not address the actual issue causing invalid line
    numbers, it does allow the test reporter to ignore the invalid lines.
    
    Related: SlatherOrg/slather#387
    Addresses: #320
Commits on Apr 17, 2018
  1. Update schema.json

    ale7714 committed Apr 17, 2018
    Follow up on #329
Commits on Apr 11, 2018
  1. Create javascript_examples.md (#327)

    amadeu01 authored and ale7714 committed Apr 11, 2018
    * Create javascript_examples.md
    
    * Update javascript_examples.md
Commits on Mar 30, 2018
  1. Add documentation for JACOCO_SOURCE_PATH variable

    toddmazierski committed Mar 30, 2018
    Related issue: #259.
Commits on Mar 19, 2018
  1. Release v0.5.1

    toddmazierski committed Mar 19, 2018
  2. Add optional JACOCO_SOURCE_PATH env variable

    toddmazierski committed Mar 16, 2018
    Add an optional `JACOCO_SOURCE_PATH` environment variable to fix
    bug where sometimes the path to source code can't be inferred.
    
    Example usage:
    
        JACOCO_SOURCE_PATH=src/main/java ./cc-test-reporter \
          format-coverage target/site/jacoco/jacoco.xml     \
          --input-type jacoco
    
    Addresses #259.
Commits on Mar 8, 2018
  1. Update php_examples.md (#315)

    davehenton committed Mar 8, 2018
Commits on Feb 26, 2018
  1. Release v0.5.0

    toddmazierski committed Feb 26, 2018
  2. Add flag to upload coverage insecurely

    toddmazierski committed Feb 22, 2018
    Add an `--insecure` flag to both the `after-build` and `upload-coverage`
    sub-commands to upload test coverage insecurely (without HTTPS).
    
    This is *not* recommended for general use. This is intended for use in
    private environments where the benefits of secure transfer outweigh the
    operational costs.
Commits on Feb 19, 2018
  1. Release v0.4.5

    dblandin committed Feb 19, 2018
    * [FIX] Add partial automated support for Heroku CI builds #305
  2. Backfill pull request links in CHANGELOG.md

    dblandin committed Feb 19, 2018
    This commit fills in a few missing footnote links.
  3. Add partial automated support for Heroku CI builds

    dblandin committed Feb 19, 2018
    Heroku CI currently exposes the following environment variables during
    CI builds:
    
    - `HEROKU_TEST_RUN_BRANCH`: A string representing the branch of the commit under test
    - `HEROKU_TEST_RUN_COMMIT_VERSION`: A string representing the commit version under test (This is the SHA in most cases)
    - `HEROKU_TEST_RUN_ID`: A string uuid representing the unique ID of the test run
    
    source: https://devcenter.heroku.com/articles/heroku-ci#configuration-using-app-json
    
    The Code Climate test reporter relies on a git committed at timestamp to
    reliably render accurate test coverage annotations on codeclimate.com
    and on github.com via the browser extension.
    
    For now, we can automatically apply the environment variables supported
    by Heroku CI, but a couple others will have to be manually supplied by
    the user:
    
    ```
    export CI_NAME="heroku"
    export GIT_COMMITTED_AT="$(date +%s)"
    ```
    
    Related to: #226
Commits on Feb 16, 2018
  1. Release 0 4 4 (#303)

    larkinscott committed Feb 16, 2018
    * Bump to version 0.4.4
    
    * Update developer instructions to include AWS CLI and GPG ref
Commits on Feb 15, 2018
  1. Add support for CI_TIMESTAMP env var (#300)

    markphelps authored and larkinscott committed Feb 15, 2018
  2. Update go_examples.md (#302)

    ale7714 committed Feb 15, 2018
Commits on Feb 9, 2018
  1. Update go_examples.md (#298)

    davehenton authored and ale7714 committed Feb 9, 2018
    * Update go_examples.md
    
    change `gocov` to `go tool cover (go test -coverprofile)`
    
    * Update go_examples.md
Commits on Feb 7, 2018
  1. Update cc-test-reporter-format-coverage.1.md (#296)

    davehenton authored and ale7714 committed Feb 7, 2018
    * Update cc-test-reporter-format-coverage.1.md
    
    * Update cc-test-reporter-format-coverage.1.md
    
    * Remove typo
Commits on Feb 6, 2018
  1. add Example 3 (#293)

    davehenton authored and ale7714 committed Feb 6, 2018
Commits on Jan 25, 2018
  1. add a 2nd go example (#289)

    nzin authored and ale7714 committed Jan 25, 2018
Commits on Jan 24, 2018
  1. Update README.md (#291)

    maestromac authored and gdiggs committed Jan 24, 2018
Commits on Jan 18, 2018
  1. prep release 0.4.3 (#290)

    wfleming committed Jan 18, 2018
  2. Clean up some logging around prefix usage (#288)

    wfleming committed Jan 18, 2018
    * Typo: trimming has two 'm's
    
    * Don't include newline in logrus format string
    
    It's not necessary: with the default  TTY formatter it just prints an
    *extra* newline, and with the logfmt formatter it prints the actual
    escape sequence "\n", which can be confusing.