trollolo 0.0.5 → 0.0.6

data/spec/unit/support/update_webmock_data

@@ -1,17 +1,35 @@
 #!/usr/bin/env ruby
 
+require "json"
+
 require_relative "webmocks"
 
-trollolo_bin = File.expand_path("../../../bin/trollolo", __FILE__)
-spec_data_dir = File.expand_path("../../data", __FILE__)
+trollolo_bin = File.expand_path("../../../../bin/trollolo", __FILE__)
+spec_data_dir = File.expand_path("../../../data", __FILE__)
 
 STDERR.puts "Updating web mock data"
 
+def scrub_file(file)
+  json = JSON.parse(File.read(file))
+  if json.is_a?(Hash) and json.has_key?("cards")
+    json["cards"].each do |card|
+      card["email"] = "trello@example.com"
+    end
+  end
+  File.open(file, "w") do |f|
+    f.write(JSON.pretty_generate(json))
+  end
+end
+
 webmock_mapping.each do |mapping|
   url = mapping[:path] + parameters_as_string(mapping)
-  file = mapping[:file]
+  filename = mapping[:file]
 
-  cmd = "#{trollolo_bin} get-raw '#{url}' >#{spec_data_dir}/#{file}"
+  file = File.join(spec_data_dir, filename)
+
+  cmd = "#{trollolo_bin} get-raw '#{url}' >#{file}"
   puts cmd
   system cmd
+
+  scrub_file(file)
 end

data/spec/unit/trello_wrapper_spec.rb

@@ -1,5 +1,7 @@
 require_relative 'spec_helper'
 
+include GivenFilesystemSpecHelpers
+
 describe TrelloWrapper do
 
   let!(:settings){ double('settings', developer_public_key: "mykey", member_token: "mytoken") }
@@ -44,4 +46,32 @@ describe TrelloWrapper do
       expect(subject.board("myboard")).to be subject.board("myboard")
     end
   end
+
+  describe '#add_attachment' do
+    use_given_filesystem
+
+    it "uploads attachment" do
+      srand(1) # Make sure multipart boundary is always the same
+
+      card_body = <<EOT
+{
+  "name": "mycard",
+  "id": "123"
+}
+EOT
+
+      stub_request(:get, "https://api.trello.com/1/cards/123?key=mykey&token=mytoken").
+        with(:headers => {'Accept'=>'*/*; q=0.5, application/xml', 'Accept-Encoding'=>'gzip, deflate', 'User-Agent'=>'Ruby'}).
+          to_return(:status => 200, :body => card_body, :headers => {})
+
+      stub_request(:post, "https://api.trello.com/1/cards/123/attachments?key=mykey&token=mytoken").
+          with(:body => "--470924\r\nContent-Disposition: form-data; name=\"file\"; filename=\"attachment-data\"\r\nContent-Type: text/plain\r\n\r\nabc\n\r\n--470924\r\nContent-Disposition: form-data; name=\"name\"\r\n\r\n\r\n--470924--\r\n",
+               :headers => {'Accept'=>'*/*; q=0.5, application/xml', 'Accept-Encoding'=>'gzip, deflate', 'Content-Length'=>'188', 'Content-Type'=>'multipart/form-data; boundary=470924', 'User-Agent'=>'Ruby'}).
+            to_return(:status => 200, :body => "", :headers => {})
+
+      path = given_file("attachment-data")
+
+      subject.add_attachment("123", path)
+    end
+  end
 end

data/trollolo.gemspec

@@ -15,8 +15,8 @@ Gem::Specification.new do |s|
   s.required_rubygems_version = '>= 1.3.6'
   s.rubyforge_project         = 'trollolo'
 
-  s.add_dependency 'thor', '>= 0.19.1'
-  s.add_dependency 'ruby-trello', '>=1.1.2'
+  s.add_dependency 'thor', '~> 0.19'
+  s.add_dependency 'ruby-trello', '~> 1.1'
 
   s.files        = `git ls-files`.split("\n")
   s.executables  = `git ls-files`.split("\n").map{|f| f =~ /^bin\/(.*)/ ? $1 : nil}.compact

data/yes_ship_it.conf

@@ -1,6 +1,6 @@
-# Experimental release automation. See https://github.com/cornelius/yes_ship_it.
-
 assertions:
+  - release_branch
+  - working_directory
   - version
   - change_log
   - built_gem

metadata

@@ -1,43 +1,43 @@
 --- !ruby/object:Gem::Specification
 name: trollolo
 version: !ruby/object:Gem::Version
-  version: 0.0.5
+  version: 0.0.6
 platform: ruby
 authors:
 - Cornelius Schumacher
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-07-22 00:00:00.000000000 Z
+date: 2015-11-12 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: thor
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.19.1
+        version: '0.19'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.19.1
+        version: '0.19'
 - !ruby/object:Gem::Dependency
   name: ruby-trello
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: 1.1.2
+        version: '1.1'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: 1.1.2
+        version: '1.1'
 description: Trollolo is a command line tool to access Trello and support tasks like
   generation of burndown charts.
 email:
@@ -47,9 +47,9 @@ executables:
 extensions: []
 extra_rdoc_files: []
 files:
-- .gitignore
-- .rspec
-- .travis.yml
+- ".gitignore"
+- ".rspec"
+- ".travis.yml"
 - CHANGELOG.md
 - CONTRIBUTING.md
 - COPYING
@@ -63,6 +63,7 @@ files:
 - lib/burndown_chart.rb
 - lib/burndown_data.rb
 - lib/card.rb
+- lib/checklist.rb
 - lib/cli.rb
 - lib/column.rb
 - lib/result.rb
@@ -78,6 +79,7 @@ files:
 - scripts/create_burndown.py
 - scripts/graph.py
 - scripts/plot.py
+- spec/data/attachment-data
 - spec/data/board-list.yaml
 - spec/data/board.json
 - spec/data/burndown-data-10.yaml
@@ -121,8 +123,6 @@ files:
 - spec/unit/trello_wrapper_spec.rb
 - trollolo.gemspec
 - yes_ship_it.conf
-- man/trollolo.1
-- man/trollolo.1.html
 homepage: https://github.com/openSUSE/trollolo
 licenses:
 - GPL-3
@@ -133,19 +133,18 @@ require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
-  - - '>='
+  - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - '>='
+  - - ">="
     - !ruby/object:Gem::Version
       version: 1.3.6
 requirements: []
 rubyforge_project: trollolo
-rubygems_version: 2.0.3
+rubygems_version: 2.4.5.1
 signing_key: 
 specification_version: 4
 summary: Trello command line client
 test_files: []
-has_rdoc: 

data/man/trollolo.1

@@ -1,128 +0,0 @@
-.\" generated with Ronn/v0.7.3
-.\" http://github.com/rtomayko/ronn/tree/0.7.3
-.
-.TH "TROLLOLO" "1" "June 2014" "" ""
-.
-.SH "NAME"
-\fBTrollolo\fR \- Trello command line client
-.
-.SH "SYNOPSIS"
-\fBtrollolo\fR [command] [options]
-.
-.P
-\fBtrollolo\fR help [command]
-.
-.SH "DESCRIPTION"
-\fBTrollolo\fR is a command line client for Trello\. It supports fetching lists and cards and has functionality for extracting data for burndown charts\.
-.
-.SH "GENERAL OPTIONS"
-.
-.TP
-\fB\-\-version\fR
-Give out version of trollolo tool\. Exit when done\.
-.
-.TP
-\fB\-\-verbose\fR
-Run in verbose mode\.
-.
-.TP
-\fB\-\-board\-id\fR
-Most commands take a \fBboard\-id\fR parameter\. This is the id of the Trello board\. It is the cryptic part of the URL of the Trello board\.
-.
-.TP
-\fB\-\-raw\fR
-Some of the commands take a \fBraw\fR option\. If this is provided the commands put out the raw JSON returned by the server instead of processing it to a more human\-readable version\.
-.
-.SH "COMMANDS"
-.
-.SS "burndown\-init \-\- Initialize burndown chart"
-\fBtrollolo burndown\-init \-\-board\-id=<board id> \-\-output=<directory>\fR
-.
-.P
-Initialize the given directory for the generation of burndown charts\. It stores the given board id in the directory in a YAML file together with other configuration data\. The YAML file also is used to store the data for the burndown charts\. The \fBburndown\fR command can be used to update the file with data from the specified Trello board\.
-.
-.P
-The directory also gets a script to do the actual generation of the burndown chart\. Just run this script after each update of the data to get the latest burndown chart\.
-.
-.SS "burndown \-\- Process data for burndown chart"
-\fBtrollolo burndown \-\-output=<directory>\fR
-.
-.P
-Update the burndown data in the given directory from the Trello board specified in the YAML file in the directory\. The given directory has to be initialized before running the \fBburndown\fR command by running the \fBburndown\-init\fR command\.
-.
-.P
-The actual generation of the burndown chart is done by running the script which is put into the directory by the \fBburndown\-init\fR command\.
-.
-.P
-For correct generation of the burndown chart, the Trello board has to follow a few convention\. They are described in the section \fBCONVENTIONS for SCRUM BOARDS\fR\.
-.
-.SS "fetch\-burndown\-data \-\- Read data for burndown chart"
-\fBtrollolo fetch\-burndown\-data \-\-board\-id=<board id>\fR
-.
-.P
-Reads data from the specified Trello board, extracts it according to the conventions for Scrum boards, and reports burndown data\.
-.
-.SS "get\-cards \-\- Get card data for a board"
-Read all card data for a given board\.
-.
-.SS "get\-checklists \-\- Get checklist data for a board"
-Read all checklist data for a given board
-.
-.SS "get\-lists \-\- Get list data for a board"
-Read all list data for a given board\.
-.
-.SH "EXAMPLES"
-Fetch burndown data of a Trello board configured in the configuration file:
-.
-.P
-\fBtrollolo fetch\-burndown\-data \-\-board\-id=CRdddpdy\fR
-.
-.P
-Fetch raw data of all cards of a Trello board:
-.
-.P
-\fBtrollolo get\-cards \-\-raw \-\-board\-id=CRdddpdy\fR
-.
-.SH "CONFIGURATION"
-Trollolo reads a configuration file \fB\.trollolorc\fR in the home directory of the user running the command line tool\. It reads the data required to authenticate with the Trello server from it\. It\'s two values (the example shows random data):
-.
-.IP "" 4
-.
-.nf
-
-developer_public_key: 87349873487ef8732487234
-member_token: 87345897238957a29835789b2374580927f3589072398579820345
-.
-.fi
-.
-.IP "" 0
-.
-.P
-These values have to be set with the personal access data for the Trello API and the id of the board, which is processed\.
-.
-.P
-For creating a developer key go to the Developer API Keys \fIhttps://trello\.com/1/appKey/generate\fR page on Trello\. It\'s the key in the first box\.
-.
-.P
-For creating a member token go follow the instructions \fIhttps://trello\.com/docs/gettingstarted/index\.html#getting\-a\-token\-from\-a\-user\fR in the Trello API documentation\.
-.
-.P
-The board id is the cryptic string in the URL of your board\.
-.
-.SH "CONVENTIONS FOR SCRUM BOARDS"
-The burndown functionality expects the board to follow a certain naming scheme, so that Trollolo can process it as a Scrum board\.
-.
-.P
-It expects a list \fBSprint Backlog\fR with open items, a list \fBDoing\fR with items in progress, and a list \fBDone Sprint X\fR with done items, where \fBX\fR is the number of the sprint\. For burndown data calculation the list with the highest number is taken\.
-.
-.P
-On work item cards the tool takes a bracketed number as suffix as size of the item in story points\. E\.g\. a card with the title \fB(3) Build magic tool\fR would have three story points\.
-.
-.P
-Cards under the waterline not part of the actual sprint commitment are expected to have a label with the name "Under waterline"\.
-.
-.P
-An example for a board which follow this conventions is the Trollolo Testing Board \fIhttps://trello\.com/b/CRdddpdy/trollolo\-testing\-board\fR\.
-.
-.SH "COPYRIGHT"
-Trollolo is Copyright (C) 2013\-2014 SUSE LLC

data/man/trollolo.1.html

@@ -1,219 +0,0 @@
-<!DOCTYPE html>
-<html>
-<head>
-  <meta http-equiv='content-type' value='text/html;charset=utf8'>
-  <meta name='generator' value='Ronn/v0.7.3 (http://github.com/rtomayko/ronn/tree/0.7.3)'>
-  <title>Trollolo(1) - Trello command line client</title>
-  <style type='text/css' media='all'>
-  /* style: man */
-  body#manpage {margin:0}
-  .mp {max-width:100ex;padding:0 9ex 1ex 4ex}
-  .mp p,.mp pre,.mp ul,.mp ol,.mp dl {margin:0 0 20px 0}
-  .mp h2 {margin:10px 0 0 0}
-  .mp > p,.mp > pre,.mp > ul,.mp > ol,.mp > dl {margin-left:8ex}
-  .mp h3 {margin:0 0 0 4ex}
-  .mp dt {margin:0;clear:left}
-  .mp dt.flush {float:left;width:8ex}
-  .mp dd {margin:0 0 0 9ex}
-  .mp h1,.mp h2,.mp h3,.mp h4 {clear:left}
-  .mp pre {margin-bottom:20px}
-  .mp pre+h2,.mp pre+h3 {margin-top:22px}
-  .mp h2+pre,.mp h3+pre {margin-top:5px}
-  .mp img {display:block;margin:auto}
-  .mp h1.man-title {display:none}
-  .mp,.mp code,.mp pre,.mp tt,.mp kbd,.mp samp,.mp h3,.mp h4 {font-family:monospace;font-size:14px;line-height:1.42857142857143}
-  .mp h2 {font-size:16px;line-height:1.25}
-  .mp h1 {font-size:20px;line-height:2}
-  .mp {text-align:justify;background:#fff}
-  .mp,.mp code,.mp pre,.mp pre code,.mp tt,.mp kbd,.mp samp {color:#131211}
-  .mp h1,.mp h2,.mp h3,.mp h4 {color:#030201}
-  .mp u {text-decoration:underline}
-  .mp code,.mp strong,.mp b {font-weight:bold;color:#131211}
-  .mp em,.mp var {font-style:italic;color:#232221;text-decoration:none}
-  .mp a,.mp a:link,.mp a:hover,.mp a code,.mp a pre,.mp a tt,.mp a kbd,.mp a samp {color:#0000ff}
-  .mp b.man-ref {font-weight:normal;color:#434241}
-  .mp pre {padding:0 4ex}
-  .mp pre code {font-weight:normal;color:#434241}
-  .mp h2+pre,h3+pre {padding-left:0}
-  ol.man-decor,ol.man-decor li {margin:3px 0 10px 0;padding:0;float:left;width:33%;list-style-type:none;text-transform:uppercase;color:#999;letter-spacing:1px}
-  ol.man-decor {width:100%}
-  ol.man-decor li.tl {text-align:left}
-  ol.man-decor li.tc {text-align:center;letter-spacing:4px}
-  ol.man-decor li.tr {text-align:right;float:right}
-  </style>
-</head>
-<!--
-  The following styles are deprecated and will be removed at some point:
-  div#man, div#man ol.man, div#man ol.head, div#man ol.man.
-
-  The .man-page, .man-decor, .man-head, .man-foot, .man-title, and
-  .man-navigation should be used instead.
--->
-<body id='manpage'>
-  <div class='mp' id='man'>
-
-  <div class='man-navigation' style='display:none'>
-    <a href="#NAME">NAME</a>
-    <a href="#SYNOPSIS">SYNOPSIS</a>
-    <a href="#DESCRIPTION">DESCRIPTION</a>
-    <a href="#GENERAL-OPTIONS">GENERAL OPTIONS</a>
-    <a href="#COMMANDS">COMMANDS</a>
-    <a href="#EXAMPLES">EXAMPLES</a>
-    <a href="#CONFIGURATION">CONFIGURATION</a>
-    <a href="#CONVENTIONS-FOR-SCRUM-BOARDS">CONVENTIONS FOR SCRUM BOARDS</a>
-    <a href="#COPYRIGHT">COPYRIGHT</a>
-  </div>
-
-  <ol class='man-decor man-head man head'>
-    <li class='tl'>Trollolo(1)</li>
-    <li class='tc'></li>
-    <li class='tr'>Trollolo(1)</li>
-  </ol>
-
-  <h2 id="NAME">NAME</h2>
-<p class="man-name">
-  <code>Trollolo</code> - <span class="man-whatis">Trello command line client</span>
-</p>
-
-<h2 id="SYNOPSIS">SYNOPSIS</h2>
-
-<p><code>trollolo</code> [command] [options]</p>
-
-<p><code>trollolo</code> help [command]</p>
-
-<h2 id="DESCRIPTION">DESCRIPTION</h2>
-
-<p><strong>Trollolo</strong> is a command line client for Trello. It supports fetching lists
-and cards and has functionality for extracting data for burndown charts.</p>
-
-<h2 id="GENERAL-OPTIONS">GENERAL OPTIONS</h2>
-
-<dl>
-<dt><code>--version</code></dt><dd><p>Give out version of trollolo tool. Exit when done.</p></dd>
-<dt><code>--verbose</code></dt><dd><p>Run in verbose mode.</p></dd>
-<dt><code>--board-id</code></dt><dd><p>Most commands take a <code>board-id</code> parameter. This is the id of the Trello
-board. It is the cryptic part of the URL of the Trello board.</p></dd>
-<dt class="flush"><code>--raw</code></dt><dd><p>Some of the commands take a <code>raw</code> option. If this is provided the commands
-put out the raw JSON returned by the server instead of processing it to
-a more human-readable version.</p></dd>
-</dl>
-
-
-<h2 id="COMMANDS">COMMANDS</h2>
-
-<h3 id="burndown-init-Initialize-burndown-chart">burndown-init -- Initialize burndown chart</h3>
-
-<p><code>trollolo burndown-init --board-id=&lt;board id> --output=&lt;directory></code></p>
-
-<p>Initialize the given directory for the generation of burndown charts. It stores
-the given board id in the directory in a YAML file together with other
-configuration data. The YAML file also is used to store the data for the
-burndown charts. The <code>burndown</code> command can be used to update the file with
-data from the specified Trello board.</p>
-
-<p>The directory also gets a script to do the actual generation of the burndown
-chart. Just run this script after each update of the data to get the latest
-burndown chart.</p>
-
-<h3 id="burndown-Process-data-for-burndown-chart">burndown -- Process data for burndown chart</h3>
-
-<p><code>trollolo burndown --output=&lt;directory></code></p>
-
-<p>Update the burndown data in the given directory from the Trello board
-specified in the YAML file in the directory. The given directory has to be
-initialized before running the <code>burndown</code> command by running the
-<code>burndown-init</code> command.</p>
-
-<p>The actual generation of the burndown chart is done by running the script
-which is put into the directory by the <code>burndown-init</code> command.</p>
-
-<p>For correct generation of the burndown chart, the Trello board has to follow
-a few convention. They are described in the section <code>CONVENTIONS for SCRUM
-BOARDS</code>.</p>
-
-<h3 id="fetch-burndown-data-Read-data-for-burndown-chart">fetch-burndown-data -- Read data for burndown chart</h3>
-
-<p><code>trollolo fetch-burndown-data --board-id=&lt;board id></code></p>
-
-<p>Reads data from the specified Trello board, extracts it according to the
-conventions for Scrum boards, and reports burndown data.</p>
-
-<h3 id="get-cards-Get-card-data-for-a-board">get-cards -- Get card data for a board</h3>
-
-<p>Read all card data for a given board.</p>
-
-<h3 id="get-checklists-Get-checklist-data-for-a-board">get-checklists -- Get checklist data for a board</h3>
-
-<p>Read all checklist data for a given board</p>
-
-<h3 id="get-lists-Get-list-data-for-a-board">get-lists -- Get list data for a board</h3>
-
-<p>Read all list data for a given board.</p>
-
-<h2 id="EXAMPLES">EXAMPLES</h2>
-
-<p>Fetch burndown data of a Trello board configured in the configuration file:</p>
-
-<p><code>trollolo fetch-burndown-data --board-id=CRdddpdy</code></p>
-
-<p>Fetch raw data of all cards of a Trello board:</p>
-
-<p><code>trollolo get-cards --raw --board-id=CRdddpdy</code></p>
-
-<h2 id="CONFIGURATION">CONFIGURATION</h2>
-
-<p>Trollolo reads a configuration file <code>.trollolorc</code> in the home directory of the
-user running the command line tool. It reads the data required to authenticate
-with the Trello server from it. It's two values (the example shows random data):</p>
-
-<pre><code class="yaml">developer_public_key: 87349873487ef8732487234
-member_token: 87345897238957a29835789b2374580927f3589072398579820345
-</code></pre>
-
-<p>These values have to be set with the personal access data for the Trello API
-and the id of the board, which is processed.</p>
-
-<p>For creating a developer key go to the
-<a href="https://trello.com/1/appKey/generate">Developer API Keys</a> page on Trello. It's
-the key in the first box.</p>
-
-<p>For creating a member token go follow the
-<a href="https://trello.com/docs/gettingstarted/index.html#getting-a-token-from-a-user">instructions</a>
-in the Trello API documentation.</p>
-
-<p>The board id is the cryptic string in the URL of your board.</p>
-
-<h2 id="CONVENTIONS-FOR-SCRUM-BOARDS">CONVENTIONS FOR SCRUM BOARDS</h2>
-
-<p>The burndown functionality expects the board to follow a certain naming scheme,
-so that Trollolo can process it as a Scrum board.</p>
-
-<p>It expects a list <code>Sprint Backlog</code> with open items, a list <code>Doing</code> with items in
-progress, and a list <code>Done Sprint X</code> with done items, where <code>X</code> is the number
-of the sprint. For burndown data calculation the list with the highest number
-is taken.</p>
-
-<p>On work item cards the tool takes a bracketed number as suffix as size of the
-item in story points. E.g. a card with the title <code>(3) Build magic tool</code> would
-have three story points.</p>
-
-<p>Cards under the waterline not part of the actual sprint commitment are expected
-to have a label with the name "Under waterline".</p>
-
-<p>An example for a board which follow this conventions is the <a href="https://trello.com/b/CRdddpdy/trollolo-testing-board">Trollolo Testing
-Board</a>.</p>
-
-<h2 id="COPYRIGHT">COPYRIGHT</h2>
-
-<p>Trollolo is Copyright (C) 2013-2014 SUSE LLC</p>
-
-
-  <ol class='man-decor man-foot man foot'>
-    <li class='tl'></li>
-    <li class='tc'>June 2014</li>
-    <li class='tr'>Trollolo(1)</li>
-  </ol>
-
-  </div>
-</body>
-</html>