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.

Sign up for GitHub

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

Jump to bottom

Improve init scripts and add test coverage #304

Merged
merged 10 commits into from Jun 5, 2022
Merged

Improve init scripts and add test coverage #304

merged 10 commits into from Jun 5, 2022

Commits on Jun 5, 2022

  1. Save project-root-list in RUNNER_TEMP dir 

    This feels better than saving in Gradle User Home and is consistent
with where the build results are written.
    @bigdaz
    bigdaz committed Jun 5, 2022
    Configuration menu
    Copy the full SHA
    ece69c5 View commit details
    Browse the repository at this point in the history

  2. Add test for project-root-capture.init.gradle

    @bigdaz
    bigdaz committed Jun 5, 2022
    Configuration menu
    Copy the full SHA
    e4ed35b View commit details
    Browse the repository at this point in the history

  3. Support and test Gradle 3.5.1 

    Fix build-scan-capture.init.gradle so that it applies to versions 3.+,
and include this version in test coverage.
    @bigdaz
    bigdaz committed Jun 5, 2022
    Configuration menu
    Copy the full SHA
    748dc30 View commit details
    Browse the repository at this point in the history

  4. Add test coverage for build-result-capture init script

    @bigdaz
    bigdaz committed Jun 5, 2022
    Configuration menu
    Copy the full SHA
    ea24a0a View commit details
    Browse the repository at this point in the history

  5. Add workflow to run init-script tests

    @bigdaz
    bigdaz committed Jun 5, 2022
    Configuration menu
    Copy the full SHA
    754892d View commit details
    Browse the repository at this point in the history

  6. Capture build-results without build-scan publication 

    The `buildScanPublished` is only called when a build scan is published by the build.
Support other invocations by adding a `buildFinished` listener.
    @bigdaz
    bigdaz committed Jun 5, 2022
    Configuration menu
    Copy the full SHA
    500607b View commit details
    Browse the repository at this point in the history

  7. Capture build results when config-cache is enabled 

    When enabled, the configuration-cache will cause the build to fail when a
`buildFinished` listener is added. Instead, use a BuildService to listen for task
failures and to write the results on build completion.
    @bigdaz
    bigdaz committed Jun 5, 2022
    Configuration menu
    Copy the full SHA
    5203a0b View commit details
    Browse the repository at this point in the history

  8. Improve build badgee for builds without scan links

    @bigdaz
    bigdaz committed Jun 5, 2022
    Configuration menu
    Copy the full SHA
    6001bc9 View commit details
    Browse the repository at this point in the history

  9. Capture build results when GE plugin is applied but no build-scan is … 

    …published
    @bigdaz
    bigdaz committed Jun 5, 2022
    Configuration menu
    Copy the full SHA
    3f2d9cd View commit details
    Browse the repository at this point in the history

  10. Build outputs

    @bigdaz
    bigdaz committed Jun 5, 2022
    Configuration menu
    Copy the full SHA
    b400dc5 View commit details
    Browse the repository at this point in the history