Comments (6)
Binaries can be downloaded from the Releases page: https://github.com/jstemmer/go-junit-report/releases
from go-junit-report.
@kishaningithub that's pretty slick. I might just switch!
from go-junit-report.
Thanks, that's a good suggestion. I'll look into setting this up and providing release binaries when I get some time.
from go-junit-report.
For automated generation of go binaries and publishing in github
https://goreleaser.com/introduction/
For creating an automagical install script that uses binaries from github releases
https://github.com/goreleaser/godownloader
from go-junit-report.
For inspiration you can look into golangci-lint project which uses both goreleaser as well as godownloader
@ahammond IMHO you should shift to this as well as you can generate brew taps, rpm and dep packages etc as well and all that has to be done is put in a yaml file and a CI integration
from go-junit-report.
In the mean time if anyone are interested we are providing pre-built binaries of go-junit-report for linux and macos here: https://github.com/bulderbank/go-junit-report/releases
from go-junit-report.
Related Issues (20)
- Build failure in tests are not reported HOT 1
- TestSuite Timestamps Report All Constant HOT 6
- Trimming module name from classname HOT 4
- unable to install go-unit-report HOT 3
- after I use "go test xxx 2>&1 | go-junit-report > result.xml", then the console doesn't print any more information HOT 4
- go-junit-report is failing with command not found...
- `-version` info is "not as useful" as it may should've been
- have an option to exclude succeeded tests
- zsh: command not found: go-junit-report HOT 3
- [no test files] Not handled well by set-exit-code
- New release HOT 2
- False error report in case of json parsing HOT 1
- Include arm64 builds in release assets
- gotest output from 1.20+ is not properly parsed
- `flag provided but not defined: -in`
- go-junit-report reports success after failing to compile code HOT 1
- benchmark tests marked as error when no unit test found HOT 1
- `system-out` is never placed under the correct `testcase` HOT 2
- Consider adding an option to prevent parsing lines starting with `#` as build output
- Better support of multiple test runs (`-count`)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from go-junit-report.