Using Gitlab CI/CD + Fastlane for iOS Project — Part 2

In previous tutorial, we installed Runner, Fastlane tool to run CI/CD on Gitlab. We are also configuring for swiftlint to check code style convention and a lot errors happened.

Now, we continue with this step to fix all errors in code.

We need to create .swiftlint.yml in the root directory of the project to do that. This file tell with swiftlint library what we need to check in our project.

$ touch .swiftlint.yml

Then, open this file with vim, it is the text editor tool:

$ vim .swiftlint.yml

And paste content to your .swiftlint.yml file:

disabled_rules: # rule identifiers to exclude from running
- colon
- comma
- control_statement
opt_in_rules: # some rules are only opt-in
- empty_count
# Find all the available rules by running:
# swiftlint rules
excluded: # paths to ignore during linting. Takes precedence over `included`.
- Pods
- vendor
analyzer_rules: # Rules run by `swiftlint analyze` (experimental)
- explicit_self
# configurable rules can be customized from this configuration file
# binary rules can set their severity level
force_cast: warning # implicitly
force_try:
severity: warning # explicitly
# rules that have both warning and error levels, can set just the warning level
# implicitly
line_length: 110
# they can set both implicitly with an array
type_body_length:
- 300 # warning
- 400 # error
# or they can set both explicitly
file_length:
warning: 500
error: 1200
# naming rules can set warnings/errors for min_length and max_length
# additionally they can set excluded names
type_name:
min_length: 4 # only warning
max_length: # warning and error
warning: 40
error: 50
excluded: iPhone # excluded via string
identifier_name:
min_length: # only min_length
error: 1 # only error
excluded: # excluded via string array
- id
- URL
- GlobalAPIKey
reporter: “xcode” # reporter type (xcode, json, csv, checkstyle, junit, html, emoji, sonarqube, markdown)

Now, build again! All errors are resolved. But there are many warnings, you will try to fix by yourself later. 🤩

Come back to Fastlane. We will configure for Fastlane also can run Swiftlint and export the report. Open Fastfile in fastlane directory in the root project and paste this script in your file:

desc "Does a static analysis of the project. Configure the options in .swiftlint.yml"
lane :lint do
swiftlint(
mode: :lint,
executable: "Pods/SwiftLint/swiftlint",
reporter: "html",
output_file: "fastlane/swiftlint-results.html",
config_file: '.swiftlint.yml',
ignore_exit_status: true
)
end

Okay, type this command in terminal:

$ fastlane lint

Let see the result:

Then, you can see the report as .html format in your fastlane directory:

Awesome!

Next, we will integrate with code coverage to measure how many percent code is covered.

Open Fastfile, paste the following content:

desc "Test an measure code coverage"
lane :test do
run_tests(devices: ["iPhone XS"])
xcov(
workspace: "CoinMarket.xcworkspace",
scheme: "CoinMarket",
output_directory: "fastlane/xcov_output"
)
end

To can get coverage, we must allow Xcode export coverage file when run testing.

Open workspace -> Edit Schema -> Test -> Options -> check on Code coverage.

Open Gemfile, add xcov gem to the project: gem ‘xcov’, ‘~> 1.5’

Then, run bundle install to install new gem.

bundle install --path vendor

After new gem is installed, we are going to run lane test to execute code coverage action on Fastfile.

fastlane test

If everything is so far so good now, let open fastlane folder, you will see new reported in this directory. Let see the results:

This is good project! 😂

Okay! We will continue with Fastlane to complete the configuration in next tutorial.

Preferences:

nakiostudio/xcov

realm/SwiftLint