summaryrefslogtreecommitdiff
path: root/.travis.yml
AgeCommit message (Collapse)Author
2015-04-08Update Travis CI job from current modulesync_configsDavid Schmitt
2015-01-07(MODULES-1473) Deprecate type() function for new parserHunter Haugen
The `type()` function will cease to work on the new parser because 'type' is a reserved keyword. The `type3x()` function may be used to continue similar functionality, but will be deprecated in favor of the built-in typing system. The `type_of()` function has been included to introspect types in the new parser.
2014-12-08Update .travis.yml, Gemfile, Rakefile, and CONTRIBUTING.mdColleen Murphy
2014-06-27Synchronize .travis.ymlColleen Murphy
2014-01-23Enable fast finish in TravisGarrett Honeycutt
http://blog.travis-ci.com/2013-11-27-fast-finishing-builds/
2013-11-30Add rake tasks to validate and lint files and check with TravisGarrett Honeycutt
This patch adds the ability to validate syntax of manifests, templates, and ruby files in lib/ via `rake validate` and the linting of manifests with puppet-lint via `rake lint`. These two commands are chained with running the spec tests in Travis to ensure there are no syntax or style issues.
2013-02-25Merge branch '4.x'Jeff McCune
* 4.x: (maint) Add Ruby 2.0.0 to Travis build matrix Conflicts: .gitignore .travis.yml Gemfile
2013-02-25(maint) Add Ruby 2.0.0 to Travis build matrixJeff McCune
Without this patch we're not testing against Ruby 2.0.0 which has recently been released. This is a problem because we'd like a way to be notified if a change set breaks compatibility with future supported versions of Ruby. This patch should not be taken as an indication that we fully support Ruby 2.0, just as an indication that we plan to in the future. This patch also tightens up the specifications of the build matrix. In addition to testing against the specific Puppet dependency versions, we're also testing against the latest 2.7.x release and the latest release.
2013-01-07(maint) Update puppet version in Travis configurationJeff McCune
Without this patch we'll test against all Puppet 3.0 versions, but not 4. This is a problem because the travis configuration should be relatively future proof to minimize surprises. This patch addresses the problem by using >= instead of ~> in the dependency specification. The patch also combines two different notification sections into a single entry.
2013-01-07Tell Travis CI to notify the PDC WebHookJeff McCune
Without this patch the so-called "puppet development community" hook service isn't being notified when Travis CI accepts jobs. This is a problem because we want the ability for Travis Bot to comment on pull requests as a result of CI build results. For example, if the build fails, then Gepetto Bot could make some helpful suggestions on how to re-run the build by amending a commit and force-pushing the branch. This patch uses the notifications section of the travis.yml configuration file, as documented at: http://about.travis-ci.org/docs/user/notifications/#Webhook-notification
2013-01-05Fix typo in travis configurationJeff McCune
The exclude keyword was accidentally specified twice.
2013-01-05Future proof travis build matrixJeff McCune
Without this patch we're not building against ruby head. This is a problem because we need to know if standard lib works with the latest version of MRI. This patch builds against ruby head but also allows the build to pass if there are failures with ruby-head.
2013-01-05(maint) Add Travis CI SupportJeff McCune
Without this patch stdlib has Travis CI configuration files, but they don't seem to completely specify the dependency versions and the build matrix. This patch addresses the problem by putting the dependency information in the conventional Gemfile location. This patch should coincide with enabling Travis CI support for pull requests. A build status image is also included in the project README.
2012-05-29Update for new gem version of puppetlabs_spec_helperBranan Purvine-Riley
This updates the Rakefile and spec_helper to use the common versions available in the puppetlabs_spec_helper rubygem branch. This mostly just removes a bunch of duplicated code, but it also gives us more flexibility in how the module is tested in the future.