-
Notifications
You must be signed in to change notification settings - Fork 52
Conversation
Consistently use 'bundle exec' in examples of executing tests.
Puppet 4 shipped with ruby 2.1.6 in puppet-agent 1.0.1, so we should test with that. Also test strict variables. Not a failing test yet.
Add puppet 4
Add the ability to allow failures
…pdate_docs (MODULES-1885) update docs
Add puppet install helper
Add tagmail to the managed modules
Gemfile: recognize ssh urls for git
* run rake once with all the targets instead of spawning it thrice * enforce unit test on puppet 4 * add the metadata-json-lint gem to enable this validation
(maint) several fixes to the default config
These can still be overridden by setting SPEC_OPTS or on the commandline, if required.
(maint) reactivate default rspec options
git should ignore the log folder
…_motd (FM-3923) Add puppetlabs-motd module to modulesync
(maint) Use blacksmith for promotions
…en-possible (maint) use newer rspec when possible
Add spec helper local and travisci caching
This uses travis to run a preliminary evaluation of PRs using the spec/acceptance test suites running in a docker container on a VM-based travis runner. This allows us to evaluate the effects of a change before merging it.
Docker acceptance on travis
@puppetlabs/windows and @glennsarti especially - feast your eyes on this awesome sauce. Please review. Thanks @DavidS ! |
*.rb eol=lf | ||
*.erb eol=lf | ||
*.pp eol=lf | ||
*.sh eol=lf |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Noooo..... haha
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👼
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like this is causing issues with one of our modules. Looks like we'll need to fix that one up.
* master: (30 commits) (FM-5091) Implement docker-based full-system tests Refresh the default vagrant nodesets Ignore transient files from bundler Add a paragraph about adding a module to here Add simple travis check Remove editor specific formatting comment Add Apache-2.0 LICENSE file. add do not edit header to files Address pull request comments (maint) use proper env var for beaker-hostgenerator version (maint) Refactor Gemfile (maint) Use beaker-hostgenerator to create nodesets Require a fixed version of rspec-puppet Remove support for testing on ruby 1.8 Add facility for spec_helper to include local content without breaking template enable caching of gem bundles on travisci (maint) re-order travis.yml to run new versions first; alphabetise other lists (BKR-537) use a working rspec-core version depending on current ruby (maint) Use blacksmith for promotions (FM-3923) Add puppetlabs-motd module to modulesync ...
Now it is failing on the chocolatey module Syncing puppetlabs-chocolatey
Cloning repository fresh
Cloning from https://github.com/puppetlabs/puppetlabs-chocolatey.git
Not managing Rakefile in puppetlabs-chocolatey
Not managing spec/spec_helper.rb in puppetlabs-chocolatey
Using no-op. Files in puppetlabs-chocolatey may be changed but will not be committed.
Files changed:
/home/travis/build/puppetlabs/modulesync_configs/vendor/bundle/ruby/1.9.1/gems/git-1.3.0/lib/git/diff.rb:151:in `block in process_full_diff': undefined method `[]' for nil:NilClass (NoMethodError)
from /home/travis/build/puppetlabs/modulesync_configs/vendor/bundle/ruby/1.9.1/gems/git-1.3.0/lib/git/diff.rb:134:in `each'
from /home/travis/build/puppetlabs/modulesync_configs/vendor/bundle/ruby/1.9.1/gems/git-1.3.0/lib/git/diff.rb:134:in `process_full_diff' |
I added debugging to the git gem around the failing line and this is the
|
That means it's the gitattributes - have I ever mentioned how much I dislike gitattributes? |
An ugly situation to a terrible problem. Maybe we should also add a check to puppet-lint or similar, so that all those files are unix line-endings only? |
@DavidS sounds good. Enjoy your vacay |
@ferventcoder what does it need to get traction on this again? Should we regroup and start by merging easier subsets, or do you just need a bit of quality time scheduled to make this happen? |
Quality time likely. |
Ticket writing as a Service: https://tickets.puppetlabs.com/browse/MODULES-3631 |
I'd be happy to pitch in as well. |
@hunner can this be closed, it seems a tad out of date |
Closing this PR as it seems to be out of date. |
This merges all the changes from master to Windows in preparation for combining the branches.