Merge pull request #164 from chef/testing

Migrate to Buildkite

.expeditor/config.yml

@@ -1,8 +1,11 @@
 # Documentation available at https://expeditor.chef.io/docs/getting-started/
 ---
+
 # Slack channel in Chef Software slack to send notifications about build failures, etc
 slack:
-  notify_channel: sustaining-notify
+  notify_channel:
+    - sustaining-notify
+    - chef-ws-notify
 
 # This publish is triggered by the `built_in:publish_rubygems` artifact_action.
 rubygems:
@@ -42,3 +45,8 @@ promote:
   actions:
     - built_in:rollover_changelog
     - built_in:publish_rubygems
+
+pipelines:
+  - verify:
+      description: Pull Request validation tests
+      public: true

.expeditor/run_linux_tests.sh

@@ -0,0 +1,53 @@
+#!/bin/bash
+#
+# This script runs a passed in command, but first setups up the bundler caching on the repo
+
+set -ue
+
+export USER="root"
+
+echo "--- dependencies"
+export LANG=C.UTF-8 LANGUAGE=C.UTF-8
+S3_URL="s3://public-cd-buildkite-cache/${BUILDKITE_PIPELINE_SLUG}/${BUILDKITE_LABEL}"
+
+pull_s3_file() {
+    aws s3 cp "${S3_URL}/$1" "$1" || echo "Could not pull $1 from S3"
+}
+
+push_s3_file() {
+    if [ -f "$1" ]; then
+        aws s3 cp "$1" "${S3_URL}/$1" || echo "Could not push $1 to S3 for caching."
+    fi
+}
+
+apt-get update -y
+apt-get install awscli -y
+
+echo "--- bundle install"
+pull_s3_file "bundle.tar.gz"
+pull_s3_file "bundle.sha256"
+
+if [ -f bundle.tar.gz ]; then
+  tar -xzf bundle.tar.gz
+fi
+
+if [ -n "${RESET_BUNDLE_CACHE:-}" ]; then
+    rm bundle.sha256
+fi
+
+bundle config --local path vendor/bundle
+bundle install --jobs=7 --retry=3
+
+echo "--- bundle cache"
+if test -f bundle.sha256 && shasum --check bundle.sha256 --status; then
+    echo "Bundled gems have not changed. Skipping upload to s3"
+else
+    echo "Bundled gems have changed. Uploading to s3"
+    shasum -a 256 Gemfile.lock > bundle.sha256
+    tar -czf bundle.tar.gz vendor/
+    push_s3_file bundle.tar.gz
+    push_s3_file bundle.sha256
+fi
+
+echo "+++ bundle exec task"
+bundle exec $1

.expeditor/verify.pipeline.yml

@@ -0,0 +1,32 @@
+---
+
+steps:
+
+- label: run-specs-ruby-2.4
+  command:
+    - .expeditor/run_linux_tests.sh rake
+  expeditor:
+    executor:
+      docker:
+        image: ruby:2.4-buster
+- label: run-specs-ruby-2.5
+  command:
+    - .expeditor/run_linux_tests.sh rake
+  expeditor:
+    executor:
+      docker:
+        image: ruby:2.5-buster
+- label: run-specs-ruby-2.6
+  command:
+    - .expeditor/run_linux_tests.sh rake
+  expeditor:
+    executor:
+      docker:
+        image: ruby:2.6-buster
+- label: run-specs-ruby-2.7-rc
+  command:
+    - .expeditor/run_linux_tests.sh rake
+  expeditor:
+    executor:
+      docker:
+        image: ruby:2.7-rc-buster

.github/CODEOWNERS

@@ -1,7 +1,5 @@
 # Order is important. The last matching pattern has the most precedence.
 
-*                          @chef/msys-developers
-.expeditor/**              @chef/jex-team
-README.md                  @chef/docs-team
-RELEASE_NOTES.md           @chef/docs-team
-.github/ISSUE_TEMPLATE/**  @chef/docs-team
+*                 @chef/msys-developers
+.expeditor/       @chef/jex-team
+*.md              @chef/docs-team

.github/ISSUE_TEMPLATE/BUG_TEMPLATE.md

@@ -1,7 +1,7 @@
 ---
 name: � Bug Report
 about: If something isn't working as expected �.
-labels: "Status: Untriaged"
+labels: "Status: Untriaged, Type: Bug"
 ---
 
 # Version:

.github/ISSUE_TEMPLATE/DESIGN_PROPOSAL.md

@@ -1,7 +1,7 @@
 ---
 name: Design Proposal
 about: I have a significant change I would like to propose and discuss before starting
-labels: "Status: Untriaged"
+labels: "Status: Untriaged, Type: Design Proposal"
 ---
 
 ### When a Change Needs a Design Proposal

.github/ISSUE_TEMPLATE/ENHANCEMENT_REQUEST_TEMPLATE.md

@@ -4,14 +4,14 @@ about: I have a suggestion (and may want to implement it 🙂)!
 labels: "Status: Untriaged"
 ---
 
-### Describe the Enhancement:
+### Describe the Enhancement
 <!---  What you are trying to achieve that you can't? -->
 
-### Describe the Need:
+### Describe the Need
 <!---  What kind of user do you believe would utilize this enhancement, and how many users might want this functionality -->
 
 ### Current Alternative
 <!--- Is there a current alternative that you can utilize to workaround the lack of this enhancement -->
 
-### Can We Help You Implement This?:
+### Can We Help You Implement This?
 <!---  The best way to ensure your enhancement is built is to help implement the enhancement yourself. If you're interested in helping out we'd love to give you a hand to make this possible. Let us know if there's something you need. -->

.github/ISSUE_TEMPLATE/SUPPORT_QUESTION.md

@@ -5,8 +5,7 @@ about: If you have a question 💬, please check out our Slack!
 
 We use GitHub issues to track bugs and feature requests. If you need help please post to our Mailing List or join the Chef Community Slack.
 
- * Chef Community Slack at http://community-slack.chef.io/.
- * Chef Mailing List https://discourse.chef.io/
-
+* Chef Community Slack at <http://community-slack.chef.io/.>
+* Chef Mailing List <https://discourse.chef.io/>
 
  Support issues opened here will be closed and redirected to Slack or Discourse.

Gemfile

@@ -12,7 +12,13 @@ group :test do
   gem "chefstyle"
   gem "rspec", "~> 3.1"
   gem "rake"
-  gem "chef", ">= 15.0"
+
+  # make sure we can still test on Ruby 2.4
+  if RUBY_VERSION.match?(/2\.4/)
+    gem "chef", "~> 14"
+  else
+    gem "chef"
+  end
 end
 
 group :development do