cide 0.5.0 → 0.6.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: f7abefe36a37940197b6aadd1fcb7df51562fde0
-  data.tar.gz: 5a4c14225d5fa5a7a3331c2c4eede54f0a1ad661
+  metadata.gz: 75c61ed91d6c0393c10dfe65926187de5aa3f8d4
+  data.tar.gz: a96c7379797f3708a8bfa56d5c40d189812d6870
 SHA512:
-  metadata.gz: 6610a43e9ed60f4f8e2addfdf7ae204b82ef082971b1555e333d69e88afb51ebcb8a04b576b080cbb3172dc7215613a48d8e2bb17e2f62fc7e0e47b544984bd6
-  data.tar.gz: 4f294c94689281c3195997dd036c0f1ca66a63b5f05e489e3d99cef09539d035d6197391d23975ace077cde710f7558a7ea5ca0be3d9ce4398508f7f4521863e
+  metadata.gz: fb4182ea7c26cdff0fc2e3811fbd6145af1396307e714a5d6298db7ed825e0b9c5c08edcbe03d728d7e8dad80c8f95c9dacec684f82b60cd5585e395007ae90c
+  data.tar.gz: 2816622e32e6fb799467f808d3ce2cf44f7a27603ae86729081f8a3d3f2c4339494234ba87f7a2741e94a007a78d7f2dd6f163ea271dd8c751df1f8ff0936e50

data/CHANGELOG.md

@@ -1,4 +1,10 @@
 
+0.6.0 / 2015-07-03
+==================
+
+  * CHANGE: Remove the runtime options. --force, --skip, ... are not available anymore
+  * FIX: Doc fixes and updates
+
 0.5.0 / 2015-06-19
 ==================
 

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    cide (0.5.0)
+    cide (0.6.0)
       thor (~> 0.19)
       virtus (~> 1.0)
 
@@ -85,4 +85,4 @@ DEPENDENCIES
   rubocop
 
 BUNDLED WITH
-   1.10.3
+   1.10.5

data/README.md

@@ -4,8 +4,8 @@
 *cide* is a command-line tool that runs tests in an isolated (docker)
 environment. It solves a problem where Jenkins workers need all the project's
 dependencies (possibly conflicting) to be installed on the boxes. With *cide*
-each run gets it's own set of temporary docker containers which are scratched
-at the end. Incidentally it's also possible to run the same `cide` command on
+each run gets its own set of temporary docker containers which are scratched
+at the end. Incidentally it is also possible to run the same `cide` command on
 the developer machine and get the same build environment as on the CI. This
 makes configuration iterations much shorter and allows to converge on a
 working configuration faster.
@@ -17,7 +17,7 @@ Go to the target project's root and run `cide init` to populate a default
 `cide.yml`. This file contains all the instruction to build your project with
 cide and is [documented here](docs/cide.yml.md).
 
-Once the file is configure run `cide` to execute the build. All the output
+Once the file is configured run `cide` to execute the build. All the output
 will appear in the console.
 
 Example

data/cide.gemspec

@@ -2,7 +2,7 @@
 
 Gem::Specification.new do |s|
   s.name          = 'cide'
-  s.version       = '0.5.0'
+  s.version       = '0.6.0'
   s.authors       = ['zimbatm']
   s.email         = ['zimbatm@zimbatm.com']
   s.summary       = 'Isolated test runner with Docker'
@@ -11,7 +11,7 @@ cide is a command-line tool that runs tests in an isolated (docker)
 environment. It allows to run the same command on the developer and CI
 machines.
 DESC
-  s.homepage      = 'https://github.com/zimbatm/cide'
+  s.homepage      = 'https://zimbatm.github.io/cide'
   s.license       = 'MIT'
 
   s.executables   = ['cide']

data/docs/cide.yml.md

@@ -19,7 +19,7 @@ Root document
 
 ```yaml
 ---
-# Image to base the build on
+# Image to base the build on. Find images at http://index.docker.io/
 #
 # required
 # type: string
@@ -108,7 +108,7 @@ ENV definition
 
 An array or hash of environment variables to load
 
-In the hash for, the left-hand side is the key and the right-hand side the
+In the hash form, the left-hand side is the key and the right-hand side the
 value.
 
 If a hash value is nil or the array form is used, the environment variables
@@ -142,7 +142,7 @@ name: 'mysql'
 # Name of the image to pull and base the container on.
 #
 # type: string
-name: 'redis:2.6'
+from: 'redis:2.6'
 
 # Environment variables for that container. See the ENV definition.
 env: {}

data/lib/cide/cli.rb

@@ -13,7 +13,6 @@ module CIDE
   class CLI < Thor
     include CIDE::Docker
     include Thor::Actions
-    add_runtime_options!
 
     default_command 'build'
 
@@ -270,7 +269,7 @@ module CIDE
       docker('rmi', '--force', *old_cide_images)
     end
 
-    desc 'init', "Creates a blank #{CONFIG_FILES.first} into the project"
+    desc 'init', "Creates a blank #{CONFIG_FILES.first} in the project"
     def init
       puts "Creating #{CONFIG_FILES.first} with default values"
       create_file CONFIG_FILES.first, File.read(DEFAULT_CIDEFILE)

data/lib/cide/default_cide.yml

@@ -1,9 +1,33 @@
 ---
-# See https://github.com/zimbatm/cide
+# See http://zimbatm.github.io/cide/#man/cide.yml.1 for more documentation
+
+# Docker image to base the build on. Find images at http://index.docker.io/
 from: ubuntu
-as_root: []
-forward_env: []
-before:
+
+# Commands run as root
+as_root:
+#  add: []
+#  env: {}
+#  run: []
+
+# Whenever to inject ssh keys into the project
 use_ssh: false
+
+# Commands run as "cide", used for caching build depedencies
+before:
+#  add: []
+#  env: {}
+#  run: []
+
+# Folder path who contains artifacts to export
 export_dir:
+
+# Linked-containers to run along the tests
+links:
+# - { from: 'redis:2.6', run: 'redis-server' }
+
+# Sets additional environment variables
+env: {}
+
+# Main script to run
 run: script/ci

data/man/cide-build.1.md

@@ -16,8 +16,8 @@ SYNOPSIS
 DESCRIPTION
 -----------
 
-This is the default command that does most of the work and is invoked 99% of
-the command.
+This is the default command that does most of the work and is invoked most of
+the time.
 
 When invoked it will read the `cide.yml` file, generate a temporary
 `Dockerfile.cide` file, build it with *docker build*, start all the linked
@@ -40,7 +40,7 @@ OPTIONS
 
 `-o`, `--export-dir`=<*path*>
   By default the export directory is the same as the one given in the
-  `export:` directive in the `cide.yml` file. It's possible to change that
+  `export:` directive in the `cide.yml` file. It is possible to change that
   target folder outside of the container.
 
 `-r`, `--run`=<*command*>

data/man/cide-debug.1.md

@@ -14,7 +14,7 @@ SYNOPSIS
 DESCRIPTION
 -----------
 
-Sometimes it's useful to run commands inside of the same environment where the
+Sometimes it is useful to run commands inside of the same environment where the
 CI tests are run from. For example if an error doesn't reproduce on the
 developer's machine.
 
@@ -33,7 +33,7 @@ OPTIONS
 
 `--user`=<*username*>
   Selects the user to run the container under. By default the `cide` user is
-  selected. In some situations it's useful to run the container as `root`
+  selected. In some situations it is useful to run the container as `root`
   (when poking at system dependencies)
 
 SEE ALSO

data/man/cide-init.1.md

@@ -4,7 +4,7 @@ CIDE-INIT 1 "JUNE 2015" cide-init "Cide Manual"
 NAME
 ----
 
-cide-init - Creates a blank `cide.yml` into the project
+cide-init - Creates a blank `cide.yml` in the project
 
 SYNOPSIS
 --------
@@ -14,7 +14,7 @@ SYNOPSIS
 DESCRIPTION
 -----------
 
-It's useful to get a basic skeleton when adding *cide* to a new project.  If
+It is useful to get a basic skeleton when adding *cide* to a new project.  If
 the file already exists a confirmation is asked.
 
 FILES

data/man/cide.1.md

@@ -20,7 +20,7 @@ DESCRIPTION
 container (through Docker).
 
 The default *cide build* command reads a `.cide.yml` file in the current
-folder and takes it's content to build a temporary Dockerfile that imports all
+folder and takes its content to build a temporary Dockerfile that imports all
 of the current directory's structure, builds an image with it and then runs a
 container from it that executes the specified tests. See the cide.yml(1) man
 page for the structure of that file.
@@ -65,7 +65,7 @@ COMMANDS
   Shows the general help or the one for the given *command*
 
 *cide init*
-  Creates a blank `cide.yml` file into the project.
+  Creates a blank `cide.yml` file in the project.
 
   See cide-init(1)
 

data/man/cide.yml.1.md

@@ -19,7 +19,7 @@ Root document
 
 ```yaml
 ---
-# Image to base the build on
+# Image to base the build on. Find images at http://index.docker.io/
 #
 # required
 # type: string
@@ -108,7 +108,7 @@ ENV definition
 
 An array or hash of environment variables to load
 
-In the hash for, the left-hand side is the key and the right-hand side the
+In the hash form, the left-hand side is the key and the right-hand side the
 value.
 
 If a hash value is nil or the array form is used, the environment variables
@@ -142,7 +142,7 @@ name: 'mysql'
 # Name of the image to pull and base the container on.
 #
 # type: string
-name: 'redis:2.6'
+from: 'redis:2.6'
 
 # Environment variables for that container. See the ENV definition.
 env: {}

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: cide
 version: !ruby/object:Gem::Version
-  version: 0.5.0
+  version: 0.6.0
 platform: ruby
 authors:
 - zimbatm
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-06-19 00:00:00.000000000 Z
+date: 2015-07-03 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: thor
@@ -154,7 +154,7 @@ files:
 - man/cide.yml.1.md
 - spec/build_config_loader_spec.rb
 - spec/spec_helper.rb
-homepage: https://github.com/zimbatm/cide
+homepage: https://zimbatm.github.io/cide
 licenses:
 - MIT
 metadata: {}
@@ -174,7 +174,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.4.7
+rubygems_version: 2.4.8
 signing_key: 
 specification_version: 4
 summary: Isolated test runner with Docker