Mirrors/inspec
2
0
Fork 0
mirror of https://github.com/inspec/inspec synced 2024-11-26 22:50:36 +00:00
Code Issues Projects Releases Packages Wiki Activity
inspec/.travis.yml

85 lines
4.3 KiB
YAML
Raw Normal View History

let travis do dockerized resource tests
2015-09-22 16:13:47 +00:00
sudo: required
Only test PRs and pushes to master Without this, Travis often ends up running 2 CI jobs for updates to a PR: 1 for the update to the PR, 1 for the push to the branch. By adding this bit of config, travis will still run a job for any update to a PR, but won't run a duplicate job for the push to the branch that the PR is based off of. We use this in chef/chef and chef/chef-server to reduce unnecessary use of TravisCI resource.
2016-08-02 10:55:06 +00:00
branches:
only:
- master
add travis config
2015-09-08 22:38:46 +00:00
language: ruby
let travis do dockerized resource tests
2015-09-22 16:13:47 +00:00
cache: bundler
using travis-ci's services:docker
2015-12-03 14:25:07 +00:00
dist: trusty
services:
release via travis + test via rubygems
2016-04-18 14:42:19 +00:00
- docker
move inquirer to deploy
2016-09-27 18:00:01 +00:00
bundler_args: "--without integration tools maintenance deploy"
workaround travis-ci's gem version
2015-12-03 13:53:40 +00:00
before_install:
drop ruby 1.9.3 Signed-off-by: Christoph Hartmann <chris@lollyrock.com>
2017-01-02 10:29:58 +00:00
- gem update --system
- gem update bundler
release via travis + test via rubygems
2016-04-18 14:42:19 +00:00
- gem --version
let travis do dockerized resource tests
2015-09-22 16:13:47 +00:00
matrix:
include:
drop ruby 1.9.3 Signed-off-by: Christoph Hartmann <chris@lollyrock.com>
2017-01-02 10:29:58 +00:00
- rvm: 2.2.6
update minimum ruby from 2.1 -> 2.2, add 2.4 (#2029) Signed-off-by: Dominik Richter <dominik.richter@gmail.com>
2017-07-24 15:19:53 +00:00
- rvm: 2.3.4
- rvm: 2.4.1
Set environment variables via Travis config Using the `env` feature of the matrix builds is a little hack so that one can quickly see what tests failed when looking at the build summary page. Signed-off-by: Steven Danna <steve@chef.io>
2016-08-04 08:27:17 +00:00
script: bundle exec rake $SUITE
restructure test suites in travis
2016-08-23 15:23:43 +00:00
env: SUITE="lint test test:functional"
update minimum ruby from 2.1 -> 2.2, add 2.4 (#2029) Signed-off-by: Dominik Richter <dominik.richter@gmail.com>
2017-07-24 15:19:53 +00:00
- rvm: 2.4.1
Set environment variables via Travis config Using the `env` feature of the matrix builds is a little hack so that one can quickly see what tests failed when looking at the build summary page. Signed-off-by: Steven Danna <steve@chef.io>
2016-08-04 08:27:17 +00:00
script: bundle exec rake $SUITE
restructure test suites in travis
2016-08-23 15:23:43 +00:00
env: SUITE="test:resources config=test/test.yaml" N=2
update minimum ruby from 2.1 -> 2.2, add 2.4 (#2029) Signed-off-by: Dominik Richter <dominik.richter@gmail.com>
2017-07-24 15:19:53 +00:00
- rvm: 2.4.1
restructure test suites in travis
2016-08-23 15:23:43 +00:00
script: bundle exec rake $SUITE
env: SUITE="test:resources config=test/test-extra.yaml" N=2
update minimum ruby from 2.1 -> 2.2, add 2.4 (#2029) Signed-off-by: Dominik Richter <dominik.richter@gmail.com>
2017-07-24 15:19:53 +00:00
- rvm: 2.4.1
run integration tests in docker
2016-05-10 17:23:11 +00:00
bundler_args: "--without guard tools"
Set environment variables via Travis config Using the `env` feature of the matrix builds is a little hack so that one can quickly see what tests failed when looking at the build summary page. Signed-off-by: Steven Danna <steve@chef.io>
2016-08-04 08:27:17 +00:00
script: bundle exec rake $SUITE
env: SUITE=test:integration OS=default-ubuntu-1204 DOCKER=true
update minimum ruby from 2.1 -> 2.2, add 2.4 (#2029) Signed-off-by: Dominik Richter <dominik.richter@gmail.com>
2017-07-24 15:19:53 +00:00
- rvm: 2.4.1
run integration tests in docker
2016-05-10 17:23:11 +00:00
bundler_args: "--without guard tools"
Set environment variables via Travis config Using the `env` feature of the matrix builds is a little hack so that one can quickly see what tests failed when looking at the build summary page. Signed-off-by: Steven Danna <steve@chef.io>
2016-08-04 08:27:17 +00:00
script: bundle exec rake $SUITE
env: SUITE=test:integration OS='default-ubuntu-1604' DOCKER=true
update minimum ruby from 2.1 -> 2.2, add 2.4 (#2029) Signed-off-by: Dominik Richter <dominik.richter@gmail.com>
2017-07-24 15:19:53 +00:00
- rvm: 2.4.1
update kitchen container, activate all in travis
2016-08-04 12:59:48 +00:00
bundler_args: "--without guard tools"
script: bundle exec rake $SUITE
env: SUITE=test:integration OS='default-centos-68' DOCKER=true
update minimum ruby from 2.1 -> 2.2, add 2.4 (#2029) Signed-off-by: Dominik Richter <dominik.richter@gmail.com>
2017-07-24 15:19:53 +00:00
- rvm: 2.4.1
update kitchen container, activate all in travis
2016-08-04 12:59:48 +00:00
bundler_args: "--without guard tools"
script: bundle exec rake $SUITE
env: SUITE=test:integration OS='default-centos-7' DOCKER=true
update minimum ruby from 2.1 -> 2.2, add 2.4 (#2029) Signed-off-by: Dominik Richter <dominik.richter@gmail.com>
2017-07-24 15:19:53 +00:00
- rvm: 2.4.1
update kitchen container, activate all in travis
2016-08-04 12:59:48 +00:00
bundler_args: "--without guard tools"
script: bundle exec rake $SUITE
env: SUITE=test:integration OS='default-debian-8' DOCKER=true
update minimum ruby from 2.1 -> 2.2, add 2.4 (#2029) Signed-off-by: Dominik Richter <dominik.richter@gmail.com>
2017-07-24 15:19:53 +00:00
- rvm: 2.4.1
update kitchen container, activate all in travis
2016-08-04 12:59:48 +00:00
bundler_args: "--without guard tools"
script: bundle exec rake $SUITE
env: SUITE=test:integration OS='default-oracle-72' DOCKER=true
update minimum ruby from 2.1 -> 2.2, add 2.4 (#2029) Signed-off-by: Dominik Richter <dominik.richter@gmail.com>
2017-07-24 15:19:53 +00:00
- rvm: 2.4.1
add fedora 23 & 24 to kitchen integration tests
2016-08-04 21:46:29 +00:00
bundler_args: "--without guard tools"
script: bundle exec rake $SUITE
env: SUITE=test:integration OS='default-fedora-24' DOCKER=true
[www] Adding a website acceptance environment If changes are detected in the docs or www directory, a website build will be generated that pushes up to Netlify. This will allow teams to validate web changes without requiring pulling down the branch and building locally. Signed-off-by: Adam Leff <adam@leff.co>
2017-04-05 22:30:00 +00:00
- rvm: 2.4.1
sudo: false
cache:
apt: true
bundle: true
addons:
apt:
packages:
- curl
- nodejs
env:
- AFFECTED_DIRS="www"
- secure: "jdzXUhP1o7RkfSikZLKgUcCIaKqLjqWa35dnxWnz7qAQ2draRKa7I7cXmUv76BZkW8HBUUH11dOi8YOVxPYPOzaqvcTCfqNqGVxsT9epgWa7rA8aXMXkECp548ry1rYJQpti9zpwsoe2GQyNPr9vNiWMiyj51CaABmZ6JzmFEEqlZc8vqpqWeqJvIqaibQGk7ByLKmi4R44fVwFKIG39RuxV+alc/G4nnQ2zmNTFuy8uFGs5EghQvRytzWY+s2AKtDiZ0YXYOII1Nl1unXNnNoQt9oI209ztlSm1+XOuTPelW6bEIx5i7OZFaSRPgJzWnkGN85C9nBE08L2az9Jz18/rYJF4fdVRttdGskueyYI21lh1FwlAg51ZG0RfLTYk2Pq+k4c+NO1cfmGcaXBwihfD5BWqrILU5HHkYszXCSmgl4hscC7/BS4Kgcq2z32JJwV8B+x4XngM0G4uzIn1Soia3lZXEKdnfVsxFDdMQ7FK60F3uQlq/44LRkZujRhqfAKOiz+0tsLexWzj7wK+DJY9Y00CUfh7xcxRxDxFNpOv1FWYFB9lUlaOt3HDHgUoksqbURiUzhOZZzTE/1MAtF2K6mbpME5CbN08J88L5JBlb+CX79XCzj30lNMeS0I/dCRQEmkygr2eJYxvRO2qsBNuphs4SWk8NZyS/llVZFI="
Move CI scripts directory Per PR feedback, moving the CI scripts directory from the repo root. Signed-off-by: Adam Leff <adam@leff.co>
2017-04-12 14:09:59 +00:00
before_install: ./support/ci/fast_pass.sh || exit 0
script: ./support/ci/deploy_website_to_acceptance.sh
update kitchen container, activate all in travis
2016-08-04 12:59:48 +00:00
Fix travis config for web acceptance environment I must've been dealing with some fun travis caching because after my last change was merged, this travis job disappeared. The .travis.yml config I used was wrong... this should do it. Signed-off-by: Adam Leff <adam@leff.co>
2017-05-04 21:35:11 +00:00
allow_failures:
- env: SUITE="test:resources config=test/test.yaml" N=2
- env: SUITE="test:resources config=test/test-extra.yaml" N=2
- env:
- AFFECTED_DIRS="www"
- secure: "jdzXUhP1o7RkfSikZLKgUcCIaKqLjqWa35dnxWnz7qAQ2draRKa7I7cXmUv76BZkW8HBUUH11dOi8YOVxPYPOzaqvcTCfqNqGVxsT9epgWa7rA8aXMXkECp548ry1rYJQpti9zpwsoe2GQyNPr9vNiWMiyj51CaABmZ6JzmFEEqlZc8vqpqWeqJvIqaibQGk7ByLKmi4R44fVwFKIG39RuxV+alc/G4nnQ2zmNTFuy8uFGs5EghQvRytzWY+s2AKtDiZ0YXYOII1Nl1unXNnNoQt9oI209ztlSm1+XOuTPelW6bEIx5i7OZFaSRPgJzWnkGN85C9nBE08L2az9Jz18/rYJF4fdVRttdGskueyYI21lh1FwlAg51ZG0RfLTYk2Pq+k4c+NO1cfmGcaXBwihfD5BWqrILU5HHkYszXCSmgl4hscC7/BS4Kgcq2z32JJwV8B+x4XngM0G4uzIn1Soia3lZXEKdnfVsxFDdMQ7FK60F3uQlq/44LRkZujRhqfAKOiz+0tsLexWzj7wK+DJY9Y00CUfh7xcxRxDxFNpOv1FWYFB9lUlaOt3HDHgUoksqbURiUzhOZZzTE/1MAtF2K6mbpME5CbN08J88L5JBlb+CX79XCzj30lNMeS0I/dCRQEmkygr2eJYxvRO2qsBNuphs4SWk8NZyS/llVZFI="
release via travis + test via rubygems
2016-04-18 14:42:19 +00:00
deploy:
provider: rubygems
on:
tags: true
api_key:
secure: uI2Zy3z4ljvOoG/6E4XPmSDg4QX5jmUfp6N9lzOfOosuZGjiGG6cWe4QMfidIz4/B5Ctp9X78bYCPxLkhCPmY9qcsR6eimQsC5AwGJhQF2Fz5fSX12LO+P4H7bis/A7cP+6QYNU8n9oXy6MYIdaw8aLJoEK4tKlNueWYhKG99O1taiF6qXsKkuNXZW7LT3B774IRCK0+BUknfW22ksAOeSpk10dkPXW5lEluXq/Q60L6+Cy01Yix1gLNav7ftMeOtE968mK3L1mzf0L3q8Tih3PLwEzYZRYQRTsd8f1J6XmNZtpdW5QiehvX08ZiFT28Dx15GMp5OKc7TnfU5avm8ryxFJB8xfdrkwNPf/UB3z1IVpHIJ6ZQlHDaiJBL429ZgYSCwrdk71IHWaAK4zSuOZyE+y9EmXbdgLLMgY6QIVrgoBLzzHLCQADXchrMaYR8LIkKI5euOfl3d96sSqXrIN/v1LSlPG/Z1LVO07cYarVGy3J/iM5aTghw3ixZcdlepGrU9DIxe7kRhmz7OLDGTZiPyRzXX1IRjaxSBMGmQSJVv6+r2UJRLmpC3W+1ysXY7nZtffzrFXHGacyvcIHxm8KSPvHgfloPvgFeebcTHcly50TOcZuBc4ZF9HZwWR5lEg/1OX5puBYE7IYfLyFm48+pqFk++tbn2glE742BhkY=
Reference in a new issue Copy permalink