cartage 1.2 → 2.0.rc1

data/test/test_cartage_plugin.rb

@@ -0,0 +1,85 @@
+# frozen_string_literal: true
+
+require 'minitest_config'
+
+describe Cartage::Plugin do
+  let(:config) { Cartage::Config.load(:default) }
+  let(:cartage) { Cartage.new(config) }
+  let(:plugin) { Cartage::Plugin::Test }
+  let(:instance) { plugin.new(cartage) }
+
+  it 'cannot be instantiated without being subclassed' do
+    assert_raises_with_message NotImplementedError, 'not a subclass' do
+      Cartage::Plugin.new(cartage)
+    end
+  end
+
+  class Cartage::Plugin::Test < ::Cartage::Plugin
+    def test
+      'test'
+    end
+  end
+
+  describe Cartage::Plugin::Test do
+    it 'is enabled by default' do
+      assert_true instance.enabled?
+      assert_false instance.disabled?
+    end
+
+    it 'can be disabled by configuration' do
+      contents = {
+        plugins: {
+          test: {
+            disabled: true
+          }
+        }
+      }.to_yaml
+
+      config = instance_stub Pathname, :read, -> { contents } do
+        instance_stub Pathname, :exist?, -> { true } do
+          Cartage::Config.load('foo')
+        end
+      end
+
+      cartage = Cartage.new(config)
+      assert_false cartage.test.enabled?
+      assert_true cartage.test.disabled?
+    end
+
+    it 'has its configured feature offers' do
+      assert_true instance.offer?(:test)
+      assert_false instance.offer?(:other)
+    end
+
+    it 'is named based on the class' do
+      assert_equal 'test', instance.plugin_name
+      assert_equal 'test', plugin.plugin_name
+    end
+  end
+
+  describe Cartage::Plugins do
+    let(:manifest) { Cartage::Manifest.new(cartage) }
+    let(:subject) { Cartage::Plugins.new.tap { |c| c.add(instance, manifest) } }
+
+    it '#enabled returns all enabled plugins' do
+      instance.define_singleton_method(:disabled?, -> { true })
+      assert_equal 1, subject.enabled.count
+    end
+
+    it '#request executes the named feature on found plug-ins' do
+      instance_stub Cartage::Plugin::Test, :test, -> {} do
+        subject.request(:test)
+      end
+
+      assert_instance_called Cartage::Plugin::Test, :test, 1
+    end
+
+    it '#request_map maps the named feature on found plug-ins' do
+      instance_stub Cartage::Plugin::Test, :test, -> { 'TEST' } do
+        assert_equal %w(TEST), subject.request_map(:test)
+      end
+
+      assert_instance_called Cartage::Plugin::Test, :test, 1
+    end
+  end
+end

metadata

@@ -1,43 +1,43 @@
 --- !ruby/object:Gem::Specification
 name: cartage
 version: !ruby/object:Gem::Version
-  version: '1.2'
+  version: 2.0.rc1
 platform: ruby
 authors:
 - Austin Ziegler
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-05-27 00:00:00.000000000 Z
+date: 2016-05-25 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
-  name: cmdparse
+  name: gli
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '3.0'
+        version: '2.13'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '3.0'
+        version: '2.13'
 - !ruby/object:Gem::Dependency
   name: minitest
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '5.6'
+        version: '5.9'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '5.6'
+        version: '5.9'
 - !ruby/object:Gem::Dependency
   name: rdoc
   requirement: !ruby/object:Gem::Requirement
@@ -56,14 +56,14 @@ dependencies:
   name: rake
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
       - !ruby/object:Gem::Version
         version: '10.0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
       - !ruby/object:Gem::Version
         version: '10.0'
 - !ruby/object:Gem::Dependency
@@ -150,6 +150,20 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: '1.2'
+- !ruby/object:Gem::Dependency
+  name: minitest-bonus-assertions
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '2.0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '2.0'
 - !ruby/object:Gem::Dependency
   name: minitest-focus
   requirement: !ruby/object:Gem::Requirement
@@ -212,60 +226,21 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '3.13'
+        version: '3.15'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '3.13'
+        version: '3.15'
 description: |-
-  Cartage provides a plug-in based tool to reliably create a package for a
-  Bundler-based Ruby application that can be used in deployment with a
-  configuration tool like Ansible, Chef, Puppet, or Salt. The package is created
-  with its dependencies bundled in +vendor/bundle+, so it can be deployed in
-  environments with strict access control rules and without requiring development
-  tool access.
-
-  Cartage has learned its tricks from Heroku, Capistrano, and Hoe. From Hoe, it
-  learned to keep a manifest to control what is packaged (as well as its plug-in
-  system). From Heroku, it learned to keep a simple ignore file. From Capistrano,
-  it learned to mark the Git hashref as a file in its built package, and to
-  timestamp the packages.
-
-  Cartage follows a relatively simple set of steps when creating a package:
-
-  1.  Copy the application files to the work area. The application’s files are
-      specified in +Manifest.txt+ and filtered against the exclusion list
-      (+.cartignore+). If there is no +.cartignore+, try to use +.slugignore+. If
-      there is no +.slugignore+, Cartage will use a sensible default exclusion
-      list. To override the use of this exclusion list, an empty +.cartignore+
-      file must be present.
-
-  2.  The Git hashref is written to the work area (as +release_hashref+) and to
-      the package staging area.
-
-  3.  Files that have been modified are restored to pristine condition in the
-      work area. The source files are not touched. (This ensures that
-      +config/database.yml+, for example, will not be the version used by a
-      continuous integration system.)
-
-  4.  Bundler is fetched into the work area, and the bundle is installed into the
-      work area’s +vendor/bundle+ without the +development+ and +test+
-      environments. If a bundle cache is kept (by default, one is), the resulting
-      +vendor/bundle+ will be put into a bundle cache so that future bundle
-      installs are faster.
-
-  5.  A timestamped tarball is created from the contents of the work area. It can
-      then be copied to a more permanent or accessible location.
-
-  Cartage is extremely opinionated about its tools and environment:
-
-  * The packages are created with +tar+ and +bzip2+ using <tt>tar cfj</tt>.
-  * Cartage only understands +git+, which is used for creating
-    <tt>release_hashref</tt>s, +Manifest.txt+ creation and comparison, and even
-    default application name detection (from the name of the origin remote).
+  Cartage provides a repeatable means to create a package for a server-side
+  application that can be used in deployment with a configuration tool like
+  Ansible, Chef, Puppet, or Salt. The package is created with vendored
+  dependencies so that it can be deployed in environments with strict access
+  control rules and without requiring development tool presence on the target
+  server(s).
 email:
 - aziegler@kineticcafe.com
 executables:
@@ -273,37 +248,46 @@ executables:
 extensions: []
 extra_rdoc_files:
 - Cartage.yml.rdoc
-- Contributing.rdoc
-- History.rdoc
-- Licence.rdoc
+- Contributing.md
+- Extending.md
+- History.md
+- Licence.md
 - Manifest.txt
 - README.rdoc
+- cartage-cli.md
 files:
-- ".autotest"
-- ".gemtest"
-- ".minitest.rb"
-- ".travis.yml"
 - Cartage.yml.rdoc
-- Contributing.rdoc
-- Gemfile
-- History.rdoc
-- Licence.rdoc
+- Contributing.md
+- Extending.md
+- History.md
+- Licence.md
 - Manifest.txt
 - README.rdoc
 - Rakefile
 - bin/cartage
+- cartage-cli.md
 - cartage.yml.sample
 - lib/cartage.rb
-- lib/cartage/command.rb
+- lib/cartage/backport.rb
+- lib/cartage/cli.rb
+- lib/cartage/commands/echo.rb
+- lib/cartage/commands/info.rb
+- lib/cartage/commands/manifest.rb
+- lib/cartage/commands/pack.rb
 - lib/cartage/config.rb
-- lib/cartage/manifest.rb
-- lib/cartage/manifest/commands.rb
-- lib/cartage/pack_command.rb
+- lib/cartage/core.rb
+- lib/cartage/gli_ext.rb
+- lib/cartage/minitest.rb
 - lib/cartage/plugin.rb
+- lib/cartage/plugins/build_tarball.rb
+- lib/cartage/plugins/manifest.rb
 - test/minitest_config.rb
 - test/test_cartage.rb
+- test/test_cartage_build_tarball.rb
 - test/test_cartage_config.rb
+- test/test_cartage_core.rb
 - test/test_cartage_manifest.rb
+- test/test_cartage_plugin.rb
 homepage: https://github.com/KineticCafe/cartage/
 licenses:
 - MIT
@@ -316,20 +300,20 @@ require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ">="
+  - - "~>"
     - !ruby/object:Gem::Version
-      version: '0'
+      version: '2.0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ">="
+  - - ">"
     - !ruby/object:Gem::Version
-      version: '0'
+      version: 1.3.1
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.4.5
+rubygems_version: 2.6.4
 signing_key: 
 specification_version: 4
-summary: Cartage provides a plug-in based tool to reliably create a package for a
-  Bundler-based Ruby application that can be used in deployment with a configuration
-  tool like Ansible, Chef, Puppet, or Salt
+summary: Cartage provides a repeatable means to create a package for a server-side
+  application that can be used in deployment with a configuration tool like Ansible,
+  Chef, Puppet, or Salt
 test_files: []

data/.autotest

@@ -1,8 +0,0 @@
-# -*- ruby -*-
-
-require "autotest/restart"
-
-Autotest.add_hook :initialize do |at|
-  # .minitest.rb ensures that the gem version of minitest is used.
-  at.testlib = ".minitest.rb"
-end

data/.gemtest

@@ -1 +0,0 @@
-

data/.minitest.rb

@@ -1,2 +0,0 @@
-gem "minitest"
-require "minitest/autorun"

data/.travis.yml

@@ -1,36 +0,0 @@
----
-sudo: false
-language: ruby
-rvm:
-  - "2.2"
-  - "2.1"
-  - 2.0.0
-  - ruby-head
-  - jruby-head
-  - jruby-9.0.0.0.pre1
-  - rbx-2
-matrix:
-  allow_failures:
-    - rvm: rbx-2
-    - rvm: jruby-head
-    - rvm: jruby-9.0.0.0.pre1
-    - rvm: ruby-head
-gemfile:
-  - Gemfile
-before_script:
-  - |
-    case "${TRAVIS_RUBY_VERSION}" in
-      rbx*)
-        gem install psych
-        ;;
-    esac
-  - rake travis:before -t
-script: rake travis
-after_script:
-  - rake travis:after -t
-notifications:
-  email:
-    recipients:
-      - aziegler@kineticcafe.com
-    on_success: change
-    on_failure: always

data/Contributing.rdoc

@@ -1,66 +0,0 @@
-== Contributing
-
-We value any contribution to cartage you can provide: a bug report, a feature
-request, or code contributions.
-
-Cartage is reasonably complex code, so there are a few guidelines:
-
-* Changes *will* *not* be accepted without tests. The test suite is written
-  with {Minitest}[https://github.com/seattlerb/minitest].
-* Match our coding style.
-* Use a thoughtfully-named topic branch that contains your change. Rebase your
-  commits into logical chunks as necessary.
-* Use {quality commit messages}[http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html].
-* Do not change the version number; when your patch is accepted and a release
-  is made, the version will be updated at that point.
-* Submit a GitHub pull request with your changes.
-* New behaviours and features are probably better created as cartage plugins.
-  If they are best suited for the core Cartage features, they require new or
-  updated documentation.
-
-=== Test Dependencies
-
-Cartage uses Ryan Davis’s {Hoe}[https://github.com/seattlerb/hoe] to manage the
-release process, and it adds a number of rake tasks. You will mostly be
-interested in:
-
-    $ rake
-
-which runs the tests the same way that:
-
-    $ rake test
-    $ rake travis
-
-will do.
-
-To assist with the installation of the development dependencies for
-cartage, I have provided the simplest possible Gemfile pointing to
-the (generated) +cartage.gemspec+ file. This will permit you to do:
-
-    $ bundle install
-
-to get the development dependencies. If you aleady have +hoe+ installed, you
-can accomplish the same thing with:
-
-    $ rake newb
-
-This task will install any missing dependencies, run the tests/specs, and
-generate the RDoc.
-
-=== Workflow
-
-Here's the most direct way to get your work merged into the project:
-
-* Fork the project.
-* Clone down your fork (<tt>git clone git://github.com/KineticCafe/cartage.git</tt>).
-* Create a topic branch to contain your change (<tt>git checkout -b my\_awesome\_feature</tt>).
-* Hack away, add tests. Not necessarily in that order.
-* Make sure everything still passes by running +rake+.
-* If necessary, rebase your commits into logical chunks, without errors.
-* Push the branch up (<tt>git push origin my\_awesome\_feature</tt>).
-* Create a pull request against KineticCafe/cartage and describe
-  what your change does and the why you think it should be merged.
-
-=== Contributors
-
-* Austin Ziegler created Cartage.