Using Danger in iOS Development

August iOS Meetup:
https://www.meetup.com/TokyoiOSMeetup/events/238915908/

Danger (Ruby):
http://danger.systems/ruby/

Danger JS:
http://danger.systems/js/

Dangerfile Examples:
- https://github.com/danger/danger/blob/master/Dangerfile
- https://github.com/fastlane/fastlane/blob/master/Dangerfile
- https://github.com/ReactiveX/RxSwift/blob/master/Dangerfile
- http://techlife.cookpad.com/entry/2017/06/28/190000
- https://github.com/operando/AndroidDangerSample/blob/master/Dangerfile

Reference:
- English
- http://techlife.cookpad.com/entry/2015/06/04/dokumi-en
- Japanese
- http://techlife.cookpad.com/entry/2016/08/17/111500
- http://techlife.cookpad.com/entry/2017/06/28/190000
- https://speakerdeck.com/operando/merukari-kaurufalsekai-fa-qi-ninaru-narahua-sou

Transcript

1. Using Danger in iOS Development Tokyo iOS Meetup - August 12th, 2017 Satoshi Hachiya / @jpmartha_jp
2. Satoshi Hachiya @jpmartha_jp
3. Satoshi Hachiya • Japanese iOS developer at ookami, Inc. • Making an iOS application, Player!
4. Satoshi Hachiya • Japanese iOS developer at ookami, Inc. • Making an iOS application, Player! • Organizer of try! Swift Tokyo, try! Swift NYC • Speaker of try! Swift India
5. Satoshi Hachiya • Founder of Pancake Meetup (Tokyo, San Jose...)
6. Agenda • What is Danger?
7. Agenda • What is Danger? • Including Danger
8. Agenda • What is Danger? • Including Danger • Using Danger on our Terminal
9. Agenda • What is Danger? • Including Danger • Using Danger on our Terminal • Using Danger on our CI
10. Agenda • What is Danger? • Including Danger • Using Danger on our Terminal • Using Danger on our CI • Practical Uses
12. What is Danger? • Danger (Ruby) • http:/ /danger.systems/ruby/ • Danger JS • http:/ /danger.systems/js/
13. Danger (Ruby)
14. Can run on: Circle, Travis, Jenkins, Buildkite, BuddyBuild, Semaphore, TeamCity, Xcode Bots, Drone, Surf and Bitrise Can chat back on: GitHub, GitLab and Bitbucket Can handle diffs from: Git
15. Including Danger
16. Creating a Gemfile • Run $ gem install bundler • Run $ bundle init
17. Creating a Dangerfile • Add gem 'danger' to Gemfile • Run $ bundle install • Run $ bundle exec danger init
18. Starter Dangerfile # Sometimes it's a README fix, or something like that - which isn't relevant for # including in a project's CHANGELOG for example declared_trivial = github.pr_title.include? "#trivial" # Make it more obvious that a PR is a work in progress and shouldn't be merged yet warn("PR is classed as Work in Progress") if github.pr_title.include? "[WIP]" # Warn when there is a big PR warn("Big PR") if git.lines_of_code > 500 # Don't let testing shortcuts get into master by accident fail("fdescribe left in tests") if `grep -r fdescribe specs/ `.length > 1 fail("fit left in tests") if `grep -r fit specs/ `.length > 1
19. Using Danger on our Terminal
20. Dangerfile # Test warn("By the way, did you have ! these days? @#{github.pr_author}")
21. Run (OSS Projects) $ bundle exec danger pr https://github.com/jpmartha/LicensePlist/pull/1 Result Warnings: - [ ] By the way, did you have ! these days? @jpmartha
22. Using Danger on our CI
23. GitHub (OSS Projects) • Create an account for Danger • Set personal access tokens
24. Travis CI • Set DANGER_GITHUB_API_TOKEN as Environment Variables
25. Travis CI • Create .travis.yml ... include: - os: osx language: swift osx_image: xcode8.3 script: - bundle exec danger ...
26. bundle exec danger (OSS Projects) # Test warn("By the way, did you have ! these days? @#{github.pr_author}")
27. Practical Uses
28. Danger 1/4 # Sometimes its a README fix, or something like that - which isn't relevant for # including in a CHANGELOG for example has_app_changes = !git.modified_files.grep(/lib/).empty? has_test_changes = !git.modified_files.grep(/spec/).empty? is_version_bump = git.modified_files.sort == ["CHANGELOG.md", "lib/danger/version.rb"].sort if has_app_changes && !has_test_changes && !is_version_bump warn("Tests were not updated", sticky: false) end # Thanks other people! message(":tada:") if is_version_bump && github.pr_author != "orta"
29. Danger 2/4 # Make a note about contributors not in the organization unless github.api.organization_member?("danger", github.pr_author) message "@#{github.pr_author} is not a contributor yet, would you like to join the Danger org?" # Pay extra attention if they modify the gemspec if git.modified_files.include?("*.gemspec") warn "External contributor has edited the Gemspec" end end # Mainly to encourage writing up some reasoning about the PR, rather than # just leaving a title if github.pr_body.length < 5 fail "Please provide a summary in the Pull Request description" end
30. Danger 3/4 # Let people say that this isn't worth a CHANGELOG entry in the PR if they choose declared_trivial = (github.pr_title + github.pr_body).include?("#trivial") || !has_app_changes if !git.modified_files.include?("CHANGELOG.md") && !declared_trivial fail("Please include a CHANGELOG entry. \nYou can find it at [CHANGELOG.md](https://github.com/danger/danger/blob/master/CHANGELOG.md).", sticky: false) end # Docs are critical, so let's re-run the docs part of the specs and show any issues: core_plugins_docs = `bundle exec danger plugins lint lib/danger/danger_core/plugins/*.rb --warnings-as-errors` # If it failed, fail the build, and include markdown with the output error. unless $?.success? # We want to strip ANSI colors for our markdown, and make paths relative colourless_error = core_plugins_docs.gsub(/\e\[(\d+)(;\d+)*m/, "") markdown("### Core Docs Errors \n\n#{colourless_error}") fail("Failing due to documentation issues, see below.", sticky: false) end
31. Danger 4/4 # Oddly enough, it's quite possible to do some testing of Danger, inside Danger # So, you can ignore these, if you're looking at the Dangerfile to get ideas. # # If these are all empty something has gone wrong, better to raise it in a comment if git.modified_files.empty? && git.added_files.empty? && git.deleted_files.empty? fail "This PR has no changes at all, this is likely an issue during development." end # This comes from `./danger_plugins/protect_files.rb` which is automatically parsed by Danger files.protect_files(path: "danger.gemspec", message: ".gemspec modified", fail_build: false) # Ensure that our core plugins all have 100% documentation core_plugins = Dir.glob("lib/danger/danger_core/plugins/*.rb") core_lint_output = `bundle exec yard stats #{core_plugins.join " "} --list-undoc --tag tags` if !core_lint_output.include?("100.00%") fail "The core plugins are not at 100% doc'd - see below:", sticky: false elsif core_lint_output.include? "warning" warn "The core plugins are have yard warnings - see below", sticky: false markdown "```\n#{core_lint_output}```" end junit.parse "junit-results.xml" junit.headers = %i(file name) junit.report
32. fastlane 1/2 # We generally try to avoid big PRs warn("Big PR") if git.lines_of_code > 500 # Show a warning for PRs that are Work In Progress if (github.pr_body + github.pr_title).include?("WIP") warn("Pull Request is Work in Progress") end # Contributors should always provide a changelog when submitting a PR if github.pr_body.length < 5 warn("Please provide a changelog summary in the Pull Request description @#{github.pr_author}") end if git.modified_files.include?("snapshot/lib/assets/SnapshotHelper.swift") warn("You modified `SnapshotHelper.swift`, make sure to update the version number at the bottom of the file to notify users about the new helper file.") end
33. fastlane 2/2 # To avoid "PR & Runs" for which tests don't pass, we want to make spec errors more visible # The code below will run on Circle, parses the results in JSON and posts them to the PR as comment containing_dir = ENV["CIRCLE_TEST_REPORTS"] || "." # for local testing file_path = File.join(containing_dir, "rspec", "fastlane-junit-results.xml") if File.exist?(file_path) junit.parse(file_path) junit.headers = [:name, :file] junit.report else puts "Couldn't find any test artifacts in path #{file_path}" end
34. RxSwift 1/2 # Warn about develop branch warn("Please target PRs to `develop` branch") if github.branch_for_base != "develop" && github.branch_for_base != "swift-3.0" # Sometimes it's a README fix, or something like that - which isn't relevant for # including in a project's CHANGELOG for example declared_trivial = github.pr_title.include? "#trivial" # Make it more obvious that a PR is a work in progress and shouldn't be merged yet warn("PR is classed as Work in Progress") if github.pr_title.include? "[WIP]" # Warn no CHANGELOG warn("No CHANGELOG changes made") if git.lines_of_code > 50 && !git.modified_files.include?("CHANGELOG.md") && !declared_trivial # Warn pod spec changes warn("RxCocoa.podspec changed") if git.modified_files.include?("RxCocoa.podspec") warn("RxSwift.podspec changed") if git.modified_files.include?("RxSwift.podspec") warn("RxTests.podspec changed") if git.modified_files.include?("RxTests.podspec") warn("RxBlocking.podspec changed") if git.modified_files.include?("RxBlocking.podspec")
35. RxSwift 2/2 # Warn summary on pull request if github.pr_body.length < 5 warn "Please provide a summary in the Pull Request description" end # If these are all empty something has gone wrong, better to raise it in a comment if git.modified_files.empty? && git.added_files.empty? && git.deleted_files.empty? fail "This PR has no changes at all, this is likely a developer issue." end # Warn when there is a big PR warn("Big PR") if git.lines_of_code > 500
36. Cookpad (Android) ... # for PR # #### if github.pr_title.include? "[WIP]" || github.pr_labels.include?("WIP") warn("PR is classed as Work in Progress") end # Warn when there is a big PR warn("a large PR") if git.lines_of_code > 300 # Warn when PR has no milestone warn("A pull request must have a milestone set") if github.pr_json["milestone"].nil? # Warn when PR has no assignees warn("A pull request must have some assignees") if github.pr_json["assignee"].nil? ...
37. AndroidDangerSample (Mercari) has_milestone = github.pr_json["milestone"] != nil warn "͋ΕΕʁϚΠϧετʔϯ͕ઃఆ͞Εͯͳ͍Αʁ" unless has_milestone warn "WIPͳͷʁ͸΍͘ऴΘΔͱ͍͍Ͷʔʂ" if github.pr_title.include? "[WIP]" or github.pr_labels.include?("WIP") ...
38. Can handle the follows from GitHub • github.pr_author • github.pr_title • github.pr_body • github.pr_labels • github.pr_json["milestone"] • github.pr_json["assignee"] • etc.
39. Other Examples • Warn if an important file is changed • Fail a pull request if required file is removed • Warn "Add screenshot" if Including storyboard file
40. Conclusion ! Stop saying "you forgot to ..." in code review by (quoted from https:/ /github.com/danger/danger/)
41. Reference • English • http:/ /techlife.cookpad.com/entry/2015/06/04/dokumi-en • Japanese • http:/ /techlife.cookpad.com/entry/2016/08/17/111500 • http:/ /techlife.cookpad.com/entry/2017/06/28/190000 • https:/ /speakerdeck.com/operando/merukari-kaurufalsekai-fa- qi-ninaru-narahua-sou
42. Q&A
43. Thanks!