Closed valeriomazzeo closed 8 years ago
This might take a little bit, I need to integrate danger and to have her show the results of bundle exec danger plugins readme
on your repo in here first
There are two more coming :)
I still need to do some work on the CI so we can talk about how well documentented these are, but I definitely don't want to have two junit plugins - I wrote one two weeks ago https://github.com/orta/danger-junit/ - is there anything unique to your implementation that I should merge?
The junit plugin I wrote it few months ago, then I just ported it to be a plugin.
I think the main difference is in the report, as yours report as a table mine reports as failures
.
Interesting, do you have any PRs with it showing still?
I'll try to post a screenshot as soon as I can
Alright, sorry for the delay, any chance you can rebase this? I've made some Danger changes which should mean that we get a preview of what this looks like on the site in this PR
done
Any chance you could give this another rebase? Sorry, think the Dangerfile should be correct now
Prints markdown containing a random post from thecodinglove.com
Prints markdown containing a random postthe_coding_love.random
random
- Prints markdown containing a random post from thecodinglove.com
Exposes warnings, errors and test results. It requires a JSON generated using xcpretty-json-formatter, to be passed as an argument for it to work.
Ensure the project compiles without warnings, errors and all tests are executed correctlyxcodebuild.parse_warnings xcodebuild.parse_errors xcodebuild.parse_tests xcodebuild.perfect_build
json_file
- Allows you to specify an xcodebuild JSON file location to parse.
parse_warnings
- Parses and exposes eventual warnings.
parse_errors
- Parses and expose eventual errors.
parse_tests
- Parses and exposes eventual test failures.
perfect_build
- Prints "Perfect build 👍🏻" if everything is ok after parsing.
A Danger plugin for Pod lib lint.
If a log file is specified lint
will parse it,
otherwise it will execute pod lib lint
and parse the output.
# Optionally specify a log file:
podliblint.log_file = "/tmp/podliblint.log"
# Lint
podliblint.lint
If pod lib lint
is executed as part of Fastlane
is possible to parse the JUnit
report instead:
# Specify a Fastlane report file:
podliblint.log_file = "/fastlane/report.xml"
podliblint.is_fastlane_report = true
# Lint
podliblint.lint
Additional pod lib lint
options can be specified through the options
variable:
# Specify custom options
podliblint.options = "--allow-warnings --private"
# Lint
podliblint.lint
Ensure pod lib lint executes correctly
Ensure pod lib lint executes correctly as part of Fastlane
Ensure pod lib lint executes correctly with custom options
log_file
- Allows you to specify a pod lib lint log file location to parse.
is_fastlane_report
- Allows you to specify if the pod lib lint log has been generated from fastlane.
options
- Allows you to specify the pod lib lint options.
see pod lib lint --help for more information.
lint
- Parses and exposes eventual warnings, errors.
Generated by :no_entry_sign: danger
Awesome, looks good
👍
Plugins