adding automated testing github actions #1
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# 🏃♀️ Continuous Integration and Delivery: Automated Testing | ||
# ====================================================== | ||
--- | ||
name: Automated Testing | ||
# Driving Event | ||
# ------------- | ||
# | ||
# What event starts this workflow: a push to any branch other than main | ||
on: | ||
push: | ||
branches: | ||
- 'automated-testing' | ||
- '!main' | ||
workflow_dispatch: | ||
# What to Do | ||
# ---------- | ||
# | ||
# Test the software with mvn test | ||
jobs: | ||
automated-testing: | ||
name: Automated Testing | ||
runs-on: ubuntu-latest | ||
if: github.actor != 'pdsen-ci' | ||
strategy: | ||
matrix: | ||
java-version: [11, 17] | ||
steps: | ||
- | ||
name: 💳 Checkout | ||
uses: actions/checkout@v4 | ||
with: | ||
lfs: true | ||
fetch-depth: 0 | ||
token: ${{secrets.ADMIN_GITHUB_TOKEN}} | ||
- | ||
name: 💵 Maven Cache | ||
uses: actions/cache@v3 | ||
with: | ||
path: ~/.m2/repository | ||
# The "key" used to indicate a set of cached files is the operating system runner | ||
# plus "mvn" for Maven-specific builds, plus a hash of the `pom.xml` files, which | ||
# should uniquely identify the dependent jars; plus "pds" because we pds-prefix | ||
# everything with "pds" in PDS—even when the context is obvious! 😅 | ||
key: pds-${{runner.os}}-mvn-${{hashFiles('**/pom.xml')}} | ||
# To restore a set of files, we only need to match a prefix of the saved key. | ||
restore-keys: pds-${{runner.os}}-mvn- | ||
- | ||
name: ☕️ Set up OpenJDK | ||
uses: actions/setup-java@v3 | ||
with: | ||
distribution: 'adopt' | ||
java-version: ${{matrix.java-version}} | ||
- | ||
name: Test Software | ||
run: | | ||
echo "testing 123" | ||
... | ||
# -*- mode: yaml; indent: 4; fill-column: 120; coding: utf-8 -*- | ||