Merge branch 'master' into feature/573_update_deprecated_ruby_version

This commit is contained in:
Andy McKay
2020-07-15 11:01:05 -07:00
committed by GitHub
34 changed files with 146 additions and 103 deletions
+1 -1
View File
@@ -22,7 +22,7 @@ In the workflow and properties files:
- [ ] Use sentence case for the names of workflows and steps, for example "Run tests".
- [ ] The name of CI workflows should only be the name of the language or platform: for example "Go" (not "Go CI" or "Go Build")
- [ ] Include comments in the workflow for any parts that are not obvious or could use clarification.
- [ ] CI workflows should run on `push` to `branches: [ master ]` and `pull_request` to `branches: [ master ]`.
- [ ] CI workflows should run on `push` to `branches: [ $default-branch ]` and `pull_request` to `branches: [ $default-branch ]`.
- [ ] Packaging workflows should run on `release` with `types: [ created ]`.
Some general notes:
+1 -1
View File
@@ -3,7 +3,7 @@
#
# To use this workflow, you will need to set up a .github/labeler.yml
# file with configuration. For more information, see:
# https://github.com/actions/labeler/blob/master/README.md
# https://github.com/actions/labeler
name: Labeler
on: [pull_request]
+30
View File
@@ -0,0 +1,30 @@
# This is a basic workflow that is manually triggered
name: Manual workflow
# Controls when the action will run. Workflow runs when manually triggered using the UI
# or API.
on:
workflow_dispatch:
# Inputs the workflow accepts.
inputs:
name:
# Friendly description to be shown in the UI instead of 'name'
description: 'Person to greet'
# Default value if no value is explicitly provided
default: 'World'
# Input has to be provided for the workflow to run
required: true
# A workflow run is made up of one or more jobs that can run sequentially or in parallel
jobs:
# This workflow contains a single job called "greet"
greet:
# The type of runner that the job will run on
runs-on: ubuntu-latest
# Steps represent a sequence of tasks that will be executed as part of the job
steps:
# Runs a single command using the runners shell
- name: Send greeting
run: echo "Hello ${{ github.event.inputs.name }}"
@@ -0,0 +1,6 @@
{
"name": "Manual workflow",
"description": "Simple workflow that is manually triggered.",
"iconName": "blank",
"categories": ["Automation"]
}
+2 -2
View File
@@ -2,9 +2,9 @@ name: Android CI
on:
push:
branches: [ master ]
branches: [ $default-branch ]
pull_request:
branches: [ master ]
branches: [ $default-branch ]
jobs:
build:
+2 -2
View File
@@ -5,9 +5,9 @@ name: Java CI
on:
push:
branches: [ master ]
branches: [ $default-branch ]
pull_request:
branches: [ master ]
branches: [ $default-branch ]
jobs:
build:
+3 -3
View File
@@ -3,12 +3,12 @@
name: CI
# Controls when the action will run. Triggers the workflow on push or pull request
# events but only for the master branch
# events but only for the $default-branch branch
on:
push:
branches: [ master ]
branches: [ $default-branch ]
pull_request:
branches: [ master ]
branches: [ $default-branch ]
# A workflow run is made up of one or more jobs that can run sequentially or in parallel
jobs:
+2 -2
View File
@@ -2,9 +2,9 @@ name: C/C++ CI
on:
push:
branches: [ master ]
branches: [ $default-branch ]
pull_request:
branches: [ master ]
branches: [ $default-branch ]
jobs:
build:
+2 -2
View File
@@ -2,9 +2,9 @@ name: Clojure CI
on:
push:
branches: [ master ]
branches: [ $default-branch ]
pull_request:
branches: [ master ]
branches: [ $default-branch ]
jobs:
build:
+2 -2
View File
@@ -2,9 +2,9 @@ name: Crystal CI
on:
push:
branches: [ master ]
branches: [ $default-branch ]
pull_request:
branches: [ master ]
branches: [ $default-branch ]
jobs:
build:
+2 -2
View File
@@ -2,9 +2,9 @@ name: Dart CI
on:
push:
branches: [ master ]
branches: [ $default-branch ]
pull_request:
branches: [ master ]
branches: [ $default-branch ]
jobs:
build:
+2 -2
View File
@@ -2,9 +2,9 @@ name: Django CI
on:
push:
branches: [ master ]
branches: [ $default-branch ]
pull_request:
branches: [ master ]
branches: [ $default-branch ]
jobs:
build:
+2 -2
View File
@@ -2,9 +2,9 @@ name: Docker Image CI
on:
push:
branches: [ master ]
branches: [ $default-branch ]
pull_request:
branches: [ master ]
branches: [ $default-branch ]
jobs:
+4 -4
View File
@@ -2,9 +2,9 @@ name: Docker
on:
push:
# Publish `master` as Docker `latest` image.
# Publish `$default-branch` as Docker `latest` image.
branches:
- master
- $default-branch
# Publish `v1.2.3` tags as releases.
tags:
@@ -56,7 +56,7 @@ jobs:
- name: Push image
run: |
IMAGE_ID=docker.pkg.github.com/${{ github.repository }}/$IMAGE_NAME
# Change all uppercase to lowercase
IMAGE_ID=$(echo $IMAGE_ID | tr '[A-Z]' '[a-z]')
@@ -67,7 +67,7 @@ jobs:
[[ "${{ github.ref }}" == "refs/tags/"* ]] && VERSION=$(echo $VERSION | sed -e 's/^v//')
# Use Docker `latest` tag convention
[ "$VERSION" == "master" ] && VERSION=latest
[ "$VERSION" == "$default-branch" ] && VERSION=latest
echo IMAGE_ID=$IMAGE_ID
echo VERSION=$VERSION
+8 -8
View File
@@ -11,22 +11,22 @@
# To configure this workflow:
#
# 1. Configure environment variables
# GitHub sets default environment variables for every workflow run.
# GitHub sets default environment variables for every workflow run.
# Replace the variables relative to your project in the "env" section below.
#
#
# 2. Signing
# Generate a signing certificate in the Windows Application
# Generate a signing certificate in the Windows Application
# Packaging Project or add an existing signing certificate to the project.
# Next, use PowerShell to encode the .pfx file using Base64 encoding
# by running the following Powershell script to generate the output string:
#
#
# $pfx_cert = Get-Content '.\SigningCertificate.pfx' -Encoding Byte
# [System.Convert]::ToBase64String($pfx_cert) | Out-File 'SigningCertificate_Encoded.txt'
#
# Open the output file, SigningCertificate_Encoded.txt, and copy the
# string inside. Then, add the string to the repo as a GitHub secret
# and name it "Base64_Encoded_Pfx."
# For more information on how to configure your signing certificate for
# For more information on how to configure your signing certificate for
# this workflow, refer to https://github.com/microsoft/github-actions-for-desktop-apps#signing
#
# Finally, add the signing certificate password to the repo as a secret and name it "Pfx_Key".
@@ -40,9 +40,9 @@ name: .NET Core Desktop
on:
push:
branches: [ master ]
branches: [ $default-branch ]
pull_request:
branches: [ master ]
branches: [ $default-branch ]
jobs:
@@ -52,7 +52,7 @@ jobs:
matrix:
configuration: [Debug, Release]
runs-on: windows-latest # For a list of available runner types, refer to
runs-on: windows-latest # For a list of available runner types, refer to
# https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on
env:
+2 -2
View File
@@ -2,9 +2,9 @@ name: .NET Core
on:
push:
branches: [ master ]
branches: [ $default-branch ]
pull_request:
branches: [ master ]
branches: [ $default-branch ]
jobs:
build:
+31 -24
View File
@@ -1,24 +1,31 @@
name: Elixir CI
on:
push:
branches: [ master ]
pull_request:
branches: [ master ]
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: Set up Elixir
uses: actions/setup-elixir@v1
with:
elixir-version: '1.9.4' # Define the elixir version [required]
otp-version: '22.2' # Define the OTP version [required]
- name: Install dependencies
run: mix deps.get
- name: Run tests
run: mix test
name: Elixir CI
on:
push:
branches: [ $default-branch ]
pull_request:
branches: [ $default-branch ]
jobs:
build:
name: Build and test
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: Set up Elixir
uses: actions/setup-elixir@v1
with:
elixir-version: '1.10.3' # Define the elixir version [required]
otp-version: '22.3' # Define the OTP version [required]
- name: Restore dependencies cache
uses: actions/cache@v2
with:
path: deps
key: ${{ runner.os }}-mix-${{ hashFiles('**/mix.lock') }}
restore-keys: ${{ runner.os }}-mix-
- name: Install dependencies
run: mix deps.get
- name: Run tests
run: mix test
+2 -2
View File
@@ -2,9 +2,9 @@ name: Erlang CI
on:
push:
branches: [ master ]
branches: [ $default-branch ]
pull_request:
branches: [ master ]
branches: [ $default-branch ]
jobs:
+6 -6
View File
@@ -2,9 +2,9 @@ name: Ruby Gem
on:
push:
branches: [ master ]
branches: [ $default-branch ]
pull_request:
branches: [ master ]
branches: [ $default-branch ]
jobs:
build:
@@ -23,12 +23,12 @@ jobs:
mkdir -p $HOME/.gem
touch $HOME/.gem/credentials
chmod 0600 $HOME/.gem/credentials
printf -- "---\n:github: Bearer ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
printf -- "---\n:github: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
gem build *.gemspec
gem push --KEY github --host https://rubygems.pkg.github.com/${OWNER} *.gem
env:
GEM_HOST_API_KEY: ${{secrets.GPR_AUTH_TOKEN}}
OWNER: username
GEM_HOST_API_KEY: "Bearer ${{secrets.GITHUB_TOKEN}}"
OWNER: ${{ github.repository_owner }}
- name: Publish to RubyGems
run: |
@@ -39,4 +39,4 @@ jobs:
gem build *.gemspec
gem push *.gem
env:
GEM_HOST_API_KEY: ${{secrets.RUBYGEMS_AUTH_TOKEN}}
GEM_HOST_API_KEY: "Bearer ${{secrets.RUBYGEMS_AUTH_TOKEN}}"
+2 -2
View File
@@ -2,9 +2,9 @@ name: Go
on:
push:
branches: [ master ]
branches: [ $default-branch ]
pull_request:
branches: [ master ]
branches: [ $default-branch ]
jobs:
+2 -2
View File
@@ -5,9 +5,9 @@ name: Java CI with Gradle
on:
push:
branches: [ master ]
branches: [ $default-branch ]
pull_request:
branches: [ master ]
branches: [ $default-branch ]
jobs:
build:
+2 -2
View File
@@ -2,9 +2,9 @@ name: Haskell CI
on:
push:
branches: [ master ]
branches: [ $default-branch ]
pull_request:
branches: [ master ]
branches: [ $default-branch ]
jobs:
build:
+2 -2
View File
@@ -2,9 +2,9 @@ name: Jekyll site CI
on:
push:
branches: [ master ]
branches: [ $default-branch ]
pull_request:
branches: [ master ]
branches: [ $default-branch ]
jobs:
build:
+3 -3
View File
@@ -2,15 +2,15 @@ name: Laravel
on:
push:
branches: [ master ]
branches: [ $default-branch ]
pull_request:
branches: [ master ]
branches: [ $default-branch ]
jobs:
laravel-tests:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: Copy .env
+2 -2
View File
@@ -5,9 +5,9 @@ name: Java CI with Maven
on:
push:
branches: [ master ]
branches: [ $default-branch ]
pull_request:
branches: [ master ]
branches: [ $default-branch ]
jobs:
build:
+2 -2
View File
@@ -5,9 +5,9 @@ name: Node.js CI
on:
push:
branches: [ master ]
branches: [ $default-branch ]
pull_request:
branches: [ master ]
branches: [ $default-branch ]
jobs:
build:
+3 -3
View File
@@ -2,9 +2,9 @@ name: PHP Composer
on:
push:
branches: [ master ]
branches: [ $default-branch ]
pull_request:
branches: [ master ]
branches: [ $default-branch ]
jobs:
build:
@@ -16,7 +16,7 @@ jobs:
- name: Validate composer.json and composer.lock
run: composer validate
- name: Cache Composer packages
id: composer-cache
uses: actions/cache@v2
+2 -2
View File
@@ -5,9 +5,9 @@ name: Python application
on:
push:
branches: [ master ]
branches: [ $default-branch ]
pull_request:
branches: [ master ]
branches: [ $default-branch ]
jobs:
build:
+2 -2
View File
@@ -5,9 +5,9 @@ name: Python package
on:
push:
branches: [ master ]
branches: [ $default-branch ]
pull_request:
branches: [ master ]
branches: [ $default-branch ]
jobs:
build:
+2 -2
View File
@@ -9,9 +9,9 @@ name: Ruby
on:
push:
branches: [ master ]
branches: [ $default-branch ]
pull_request:
branches: [ master ]
branches: [ $default-branch ]
jobs:
test:
+2 -2
View File
@@ -2,9 +2,9 @@ name: Rust
on:
push:
branches: [ master ]
branches: [ $default-branch ]
pull_request:
branches: [ master ]
branches: [ $default-branch ]
env:
CARGO_TERM_COLOR: always
+2 -2
View File
@@ -2,9 +2,9 @@ name: Scala CI
on:
push:
branches: [ master ]
branches: [ $default-branch ]
pull_request:
branches: [ master ]
branches: [ $default-branch ]
jobs:
build:
+2 -2
View File
@@ -2,9 +2,9 @@ name: Swift
on:
push:
branches: [ master ]
branches: [ $default-branch ]
pull_request:
branches: [ master ]
branches: [ $default-branch ]
jobs:
build:
+6 -6
View File
@@ -1,7 +1,7 @@
# This workflow installs the latest version of Terraform CLI and configures the Terraform CLI configuration file
# with an API token for Terraform Cloud (app.terraform.io). On pull request events, this workflow will run
# `terraform init`, `terraform fmt`, and `terraform plan` (speculative plan via Terraform Cloud). On push events
# to the master branch, `terraform apply` will be executed.
# to the $default-branch branch, `terraform apply` will be executed.
#
# Documentation for `hashicorp/setup-terraform` is located here: https://github.com/hashicorp/setup-terraform
#
@@ -47,7 +47,7 @@ name: 'Terraform'
on:
push:
branches:
- master
- $default-branch
pull_request:
jobs:
@@ -65,7 +65,7 @@ jobs:
- name: Checkout
uses: actions/checkout@v2
# Install the latest version of Terraform CLI and configure the Terraform CLI configuration file with a Terraform Cloud user API token
# Install the latest version of Terraform CLI and configure the Terraform CLI configuration file with a Terraform Cloud user API token
- name: Setup Terraform
uses: hashicorp/setup-terraform@v1
with:
@@ -82,9 +82,9 @@ jobs:
# Generates an execution plan for Terraform
- name: Terraform Plan
run: terraform plan
# On push to master, build or change infrastructure according to Terraform configuration files
# On push to $default-branch, build or change infrastructure according to Terraform configuration files
# Note: It is recommended to set up a required "strict" status check in your repository for "Terraform Cloud". See the documentation on "strict" required status checks for more information: https://help.github.com/en/github/administering-a-repository/types-of-required-status-checks
- name: Terraform Apply
if: github.ref == 'refs/heads/master' && github.event_name == 'push'
if: github.ref == 'refs/heads/$default-branch' && github.event_name == 'push'
run: terraform apply -auto-approve