5037d546e1
Also schedule a build to run at 06:30 in the morning, every Monday. This way, the JDK and Netty 5 snapshots will be updated in the build cache every week.
46 lines
1.4 KiB
YAML
46 lines
1.4 KiB
YAML
name: CI Build
|
|
|
|
# Controls when the action will run.
|
|
on:
|
|
# Triggers the workflow on push or pull request events but only for the main branch
|
|
push:
|
|
branches: [ main ]
|
|
pull_request:
|
|
branches: [ main ]
|
|
schedule:
|
|
- cron: '30 6 * * 1' # At 06:30 on Monday, every Monday.
|
|
|
|
# Allows you to run this workflow manually from the Actions tab
|
|
workflow_dispatch:
|
|
|
|
# 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 "build"
|
|
build:
|
|
# 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:
|
|
# http://man7.org/linux/man-pages/man1/date.1.html
|
|
- name: Create Cache Key
|
|
id: cache-key
|
|
run: |
|
|
echo "::set-output name=key::$(/bin/date -u "+%Y%U")"
|
|
shell: bash
|
|
|
|
# Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
|
|
- uses: actions/checkout@v2
|
|
|
|
# Enable caching of Docker layers
|
|
- uses: satackey/action-docker-layer-caching@v0.0.8
|
|
continue-on-error: true
|
|
with:
|
|
key: docker-cache-${{ steps.cache-key.outputs.key }}-{hash}
|
|
restore-keys: |
|
|
docker-cache-${{ steps.cache-key.outputs.key }}-
|
|
|
|
# Run the make script
|
|
- name: Make build
|
|
run: make build
|