From 04d9ee40c8e73d4b7d5f49a803b66c2ca9c6deb3 Mon Sep 17 00:00:00 2001
From: Maurice Parker <mo@vincode.io>
Date: Tue, 8 Oct 2019 17:15:43 -0500
Subject: [PATCH] Remove CircleCI build config

---
 .circleci/config.yml | 58 --------------------------------------------
 1 file changed, 58 deletions(-)
 delete mode 100644 .circleci/config.yml

diff --git a/.circleci/config.yml b/.circleci/config.yml
deleted file mode 100644
index 1f32a4fa1..000000000
--- a/.circleci/config.yml
+++ /dev/null
@@ -1,58 +0,0 @@
-# iOS CircleCI 2.0 configuration file
-#
-version: 2
-jobs:
-  build:
-
-    # Specify the Xcode version to use
-    macos:
-      xcode: "10.2.1"
-    # https://circleci.com/docs/2.0/configuration-reference/
-
-    # Mac/IOS specific examples and docs under the following links:
-    # https://circleci.com/docs/2.0/hello-world-macos/
-
-    steps:
-      - checkout
-      - run: git submodule sync
-      - run: git submodule update --init
-      # Commands will execute in macOS container
-      # with Xcode 10.2.1 installed
-      - run: xcodebuild -version
-      #- run:
-      #    name: get xcodebuild build options
-      #    command: xcodebuild -help
-      - run:
-          name: get xcodebuild build settings
-          command: xcodebuild -showBuildSettings
-
-      - run:
-          name: force wipe of any pre-existing derived data in CI
-          command: rm -rf /Users/distiller/Library/Developer/Xcode/DerivedData/NetNewsWire-*
-
-      # Build the app and run tests
-      - run:
-          name: Build Mac
-          command: xcodebuild -workspace NetNewsWire.xcworkspace -scheme NetNewsWire -configuration Debug -showBuildTimingSummary
-      # NOTE(heckj):
-      # the -configuration Release build invokes a shell script specifically
-      # codesigning the Sparkle pieces with the developer 'Brent Simmons',
-      # so we don't try and invoke that in CI
-      #
-
-      # the stuff below is from example that was using fastlane
-      # (and we're not using that...) so it's placeholder tidbits
-      # to clue me in to where I can get things for test log output
-      # for the CircleCI UI exposure...
-
-      # Collect XML test results data to show in the UI,
-      # and save the same XML files under test-results folder
-      # in the Artifacts tab
-      #- store_test_results:
-      #    path: test_output/report.xml
-      #- store_artifacts:
-      #    path: /tmp/test-results
-      #    destination: scan-test-results
-      #- store_artifacts:
-      #    path: ~/Library/Logs/scan
-      #    destination: scan-logs