Releases: BuildPulseLLC/buildpulse-action
v0.9.1
The BuildPulse action has moved to a new home at buildpulse/buildpulse-action.
Developers are encouraged to update their workflows to point to buildpulse/buildpulse-action
instead of Workshop64/buildpulse-action
.
If you have any questions or want a hand making this change, you can reach us any time at hello@buildpulse.io.
v0.9.0
-
Gracefully handle failure downloading test-reporter binary (63f43af)
Prior to this change, a failure when downloading the BuildPulse test-reporter would cause the whole build to fail, which is a rotten experience.
In theory, the download should always succeed. But networks are messy, and we never want BuildPulse to make anyone's builds unstable. So in the (hopefully rare) scenario where we're unable to download the BuildPulse test-reporter, the action will skip the BuildPulse analysis for the build and emit a warning in the build logs and via an annotation.
Also, in the (again hopefully rare) scenario where we're unable to download the binary from
get.buildpulse.io
, the action will usegithub.com
as a backup source for the binary. -
If we can't connect within 5 seconds when downloading the test-reporter binary, give up so that we don't delay completion of the build (0051afa)
v0.8.0
v0.8.0-pre
Add preliminary support for running on macOS and Windows (in addition to the existing support for running on Linux) (#3)
v0.7.0
- Download test-reporter binary via https://get.buildpulse.io/test-reporter-linux-amd64
- Retry download if transient network error encountered
v0.6.0
Update URL for downloading test-reporter binary to work around 403 forbidden
issue
v0.5.0
Add support for using glob patterns to specify location of XML report files
v0.4.0
Gracefully handle missing secrets in @dependabot pull requests (#1)
v0.3.0
Add support for optional repository-path
input (for workflows that use a custom path when cloning their repository)
v0.2.0
Adopts the newly-released BuildPulse Test Reporter for faster setup 🐎