xcodebuild_rake 2.2.5

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: df45156398ee3c6d3a50194def99c6716f7dfb11
+  data.tar.gz: bcd569f47991bcd12f8b50c19d86aeab4b0d2eb3
+SHA512:
+  metadata.gz: 3958fd0ca7031fe19bcaef150ae5b65580faca3d98a8e85e48dfeda6c58d908bf9f831b1ef8b5a5270c50cdd9880f8e9b5e4d65bc204eb7a6f4b52e11f41f23f
+  data.tar.gz: def5e8cbf38b9e3122fadad8de79b52b343b04566e93c8e9907bfbd501c8ad3d0739f8d3e3be4a6f997a4ff600474da69a9b82ee0a08f50c197260ad6ee3cb21

data/.gemrc

@@ -0,0 +1 @@
+gem: --no-ri --no-rdoc

data/.gitignore

@@ -0,0 +1 @@
+!/lib/

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at lprzytula@gmail.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

data/Gemfile

@@ -0,0 +1,3 @@
+source 'https://rubygems.org'
+
+gemspec

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2017 Applause inc. All rights reserved.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,25 @@
+# XcodebuildRake
+
+Simple Ruby Rake build script for Xcode projects. It uses `xcodebuild` and `xcpretty` tools.
+
+## Installation and usage
+
+- [**Prerequisites**](./docs/prerequisites.md)
+- [**Installation**](./docs/installation.md)
+- [**Configuration**](./docs/configuration.md)
+- [**Usage**](./docs/usage.md)
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies.
+
+To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/ApplauseAQI/xcodebuild-rake. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
+
+
+## License
+
+The gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).

data/Rakefile

@@ -0,0 +1,2 @@
+require "bundler/gem_tasks"
+task :default => :spec

data/bin/console

@@ -0,0 +1,14 @@
+#!/usr/bin/env ruby
+
+require "bundler/setup"
+require "xcodebuild_rake"
+
+# You can add fixtures and/or initialization code here to make experimenting
+# with your gem easier. You can also use a different console, if you like.
+
+# (If you use this, don't forget to add pry to your Gemfile!)
+# require "pry"
+# Pry.start
+
+require "irb"
+IRB.start

data/bin/setup

@@ -0,0 +1,8 @@
+#!/usr/bin/env bash
+set -euo pipefail
+IFS=$'\n\t'
+set -vx
+
+bundle install
+
+# Do any other automated setup that you need to do here

data/bin/xcodebuild_rake_init

@@ -0,0 +1,8 @@
+#!/usr/bin/env ruby
+
+templates_dir = File.join(File.dirname(__FILE__), '../templates')
+current_dir = Dir.pwd
+puts "Adding Rakefile"
+FileUtils.cp(File.join(templates_dir, "Rakefile"), File.join(current_dir, "Rakefile"))
+puts "Adding build.yaml"
+FileUtils.cp(File.join(templates_dir, "build.yaml"), File.join(current_dir, "build.yaml"))

data/docs/configuration.md

@@ -0,0 +1,43 @@
+# Configuration
+
+The main two files which must be placed next to `.xcodeproj` are `Rakefile` and `build.yaml`.
+
+To initialize those files with default values simply execute from the root of your project:
+
+```
+$ xcodebuild_rake_init
+```
+
+## Build.yaml
+
+This file contains `setups` which are used to invoke `xcodebuild`, parameters reflects the arguments you would provide manually to CLI tool.
+
+By default there are 2 setups:
+```
+setups:
+
+ - name: Default
+   sdk:	iphoneos
+   workspace:
+   scheme:
+   configuration: Release
+
+ - name: Specs
+   sdk:	iphonesimulator
+   xcpretty-flags: -c -t -r junit
+   destination:
+    platform: iOS Simulator
+    name: iPhone 6
+    os: 9.0
+```
+
+
+Setup `Default` is used for building and archiving and it's base setup for any other. Which means that you don't need to repeat setup for fields which can be take from default one. Setup `Specs` is used for `test` task.
+
+`scheme` property is left blank for you to fill in your default scheme.
+
+If you're using workspace fill in setting `workspace`, otherwise you can remove it.
+
+## Rakefile
+
+You must modify `PRODUCT_NAME` constant from the `Rakefile`, use the value of `PRODUCT_NAME` from your Xcode settings (most likely `.xcodeproj` or `.xcworkspace` name)

data/docs/installation.md

@@ -0,0 +1,11 @@
+# Installation
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem 'xcodebuild_rake', :git => 'https://github.com/ApplauseAQI/xcodebuild-rake'
+```
+
+And then execute:
+
+    $ bundle

data/docs/prerequisites.md

@@ -0,0 +1,34 @@
+# Prerequisites
+
+The build script fetches it dependencies using `bundler` and configuration file `Gemfile`. In order to make sure that all ruby dependencies are sandboxed within the project it's recommended to use RVM ([rvm.io](https://rvm.io)).
+
+To install RVM on your machine invoke the following
+
+```
+$ curl -sSL https://get.rvm.io | bash -s stable --ruby
+```
+and then simply install desired version of Ruby:
+```
+$ rvm install 2.2.1
+$ rvm use 2.2.1
+```
+
+Create `gemset` for your project (e.g. MyProject):
+
+```
+$ rvm use 2.2.1@my-project --create
+
+```
+
+Lastly install `bundler`:
+```
+$ gem install bundler
+```
+
+## Uploading applications to Applause SDK / Beta
+
+In order to upload .ipa or .apk files to Applause SDK or Beta, install applause-tool cli using pip:
+
+```
+$ pip install applause-tool
+```

data/docs/usage.md

@@ -0,0 +1,71 @@
+# Usage
+
+Rakefile is based on our in-house build script (soon to be extract as submodule or ruby gem), which provides helpers functions for executing builds from command line.
+
+Build script setup is defined in the `build.yaml` file. There you can find a `Default` configuration which is a starting point for each task. Plus all additional configurations for specific tasks, e.g. "Specs" configuration defines destination of the test execution.
+
+Once the build-script is extracted into separate project the documentation of the `build.yaml` will be provided.
+
+###Clean
+
+To clean the project invoke the following:
+
+```
+$ rake clean
+```
+
+### Build
+
+To build the project invoke the following:
+
+```
+$ rake build
+```
+
+Result of the task can be found under `build` directory.
+
+### Archive
+
+To archive the project for distribution invoke the following:
+
+```
+$ rake archive
+```
+
+The result of this task are zipped .app and .dSYM files that are located `build` directory. 
+
+### Test
+
+To build the project invoke the following:
+
+```
+$ rake test
+```
+
+The JUnit formatted test output XML can be found under `build/reports/junit.xml`.
+
+
+### Watch
+
+To speed up the local development and receive quick feedback when something goes wrong you can use `watch` task. To use this task you first need to install two tools: `fswatch` (repo [here](https://github.com/emcrisostomo/fswatch)):
+
+```
+$ brew install fswatch
+```
+
+and `terminal-notifier` (repo [here](https://github.com/alloy/terminal-notifier)) which is added to `Gemfile`. This way, whenever something goes wrong you will get a Mac OS notification.
+
+Once you have it on your machine, simply invoke the `watch` task:
+
+```
+$ rake watch
+```
+
+From now on, every time you change something in your source code, it will be immediately incrementally complied. This feedback is extremely useful when one starts his journey with Swift lang.
+
+
+You can also execute tests for each change with the following task:
+
+```
+$ rake watch_test
+```

data/lib/ExportOptions.plist

@@ -0,0 +1,10 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+<plist version="1.0">
+<dict>
+	<key>method</key>
+	<string>enterprise</string>
+	<key>compileBitcode</key>
+	<true/>
+</dict>
+</plist>

data/lib/model/build_configuration.rb

@@ -0,0 +1,90 @@
+# Copyright (c) 2017 Applause Inc. All rights reserved.
+
+require 'yaml'
+
+BUILD_CONFIGURATION_YAML_PATH = 'build.yaml'
+
+YAML_SETUPS_KEY = 'setups'
+YAML_DEFAULT_SETUP_NAME = 'Default'
+YAML_SETUP_NAME_KEY = 'name'
+YAML_SETUP_WORKSPACE_KEY = 'workspace'
+YAML_SETUP_PROJECT_KEY = 'project'
+YAML_SETUP_SCHEME_KEY = 'scheme'
+YAML_SETUP_SDK_KEY = 'sdk'
+YAML_SETUP_CONF_KEY = 'configuration'
+YAML_SETUP_DESTINATION_KEY = 'destination'
+YAML_SETUP_RELEASE_CONFIGURATION_KEY = 'release_configuration'
+
+class BuildConfiguration
+	attr_accessor :project, :project_load, :scheme, :sdk, :configuration
+	attr_accessor :release_configuration
+	attr_accessor :test_destination
+	attr_accessor :use_xcpretty, :xcpretty_flags
+
+	def initialize()
+		@use_xcpretty = true
+		@xcpretty_flags = "-c"
+	end
+
+	def parse_setup(setup)
+		if setup.has_key?(YAML_SETUP_WORKSPACE_KEY)
+			@project = setup[YAML_SETUP_WORKSPACE_KEY]
+			@project_load = "-workspace"
+		end
+    if setup.has_key?(YAML_SETUP_PROJECT_KEY)
+      @project = setup[YAML_SETUP_PROJECT_KEY]
+			@project_load = "-project"
+    end
+		if setup.has_key?(YAML_SETUP_SCHEME_KEY)
+			@scheme = setup[YAML_SETUP_SCHEME_KEY]
+		end
+		if setup.has_key?(YAML_SETUP_SDK_KEY)
+			@sdk = setup[YAML_SETUP_SDK_KEY]
+		end
+		if setup.has_key?(YAML_SETUP_CONF_KEY)
+			@configuration = setup[YAML_SETUP_CONF_KEY]
+		end
+		if setup.has_key?(YAML_SETUP_XCPRETTY_KEY)
+			@use_xcpretty = setup[YAML_SETUP_XCPRETTY_KEY]
+		end
+		if setup.has_key?(YAML_SETUP_XCPRETTY_FLAGS_KEY)
+			@xcpretty_flags = setup[YAML_SETUP_XCPRETTY_FLAGS_KEY]
+		end
+		if setup.has_key?(YAML_SETUP_RELEASE_CONFIGURATION_KEY)
+			if self.release_configuration.nil?
+				@release_configuration = ReleaseConfiguration.new
+			end
+			@release_configuration.parse_setup(setup[YAML_SETUP_RELEASE_CONFIGURATION_KEY])
+		end
+		if setup.has_key?(YAML_SETUP_DESTINATION_KEY)
+			if self.test_destination.nil?
+				@test_destination = TestDestination.new
+			end
+			@test_destination.parse_setup(setup[YAML_SETUP_DESTINATION_KEY])
+		end
+	end
+
+	class << self
+			def load(setup_name)
+				build_config = BuildConfiguration.new
+				yaml = YAML.load_file(BUILD_CONFIGURATION_YAML_PATH)
+				if yaml.has_key?(YAML_SETUPS_KEY)
+					setups = yaml[YAML_SETUPS_KEY]
+					parse_named_setup setups, build_config, YAML_DEFAULT_SETUP_NAME
+					if setup_name != YAML_DEFAULT_SETUP_NAME
+						parse_named_setup setups, build_config, setup_name
+					end
+				end
+				return build_config
+			end
+
+			private
+			def parse_named_setup(setups, build_config, setup_name)
+				filtered_setups = setups.select { |s| s[YAML_SETUP_NAME_KEY] == setup_name}
+				setup = filtered_setups.first
+				if setup
+					build_config.parse_setup(setup)
+				end
+			end
+	end
+end