2
100%
master: 100%

Ran 28 May 2013 10:58PM UTC

Files 4

Run time –

Badge

Embed ▾

Committed 28 May 2013 10:58PM UTC coverage: 100.0%. Remained the same

Job # 2.0.0

Build Type

push

travis-ci

Committed by

stefanozanella

Commit Message

Get rid of skeleton repository.

We now build the module from scratch. At this point, it seems to me that adding
the Git stuff makes the project less clear and more complicated in principle:
* what do you do in puppetry and what in the module?
* what if the inherited module (which should have been made customizable at
  some point, since it was the only thing making the design worth it) doesn't
  include folder/files referenced/used in puppetry itself? How to handle the
  possible mismatch?

By not having a half-baked source of data, it looks easier to separate
distinct features like rspec-puppet, rakefile, vagrant, etc. That said, the
design still SUCKS BAD. Needs refactoring + SRP enforcing.

NOTE that now we're a bit back on the features' list, since by cloning a
skeleton repo we had a Rakefile in place, which is not setup yet now.

Run Details

65 of 65 relevant lines covered (100.0%)

1.37 hits per line

stefanozanella / puppetry / 17 / 2
100%
master: 100%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 17.2 (2.0.0)

stefanozanella / puppetry / 17 / 2 100% master: 100%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 17.2 (2.0.0)

stefanozanella / puppetry / 17 / 2
100%
master: 100%

README BADGES
x