Skip to content

commons-logging-1.3.2 has same PGP key as commons-logging-1.3.1 #365

commons-logging-1.3.2 has same PGP key as commons-logging-1.3.1

commons-logging-1.3.2 has same PGP key as commons-logging-1.3.1 #365

Workflow file for this run

name: Build
on:
push:
branches:
- master
pull_request:
types: [opened, synchronize, reopened]
jobs:
build:
name: Build
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
with:
fetch-depth: 0 # Shallow clones should be disabled for a better relevancy of analysis
- name: Set up JDK 21
uses: actions/setup-java@v3
with:
# Matches Jenkinsfile:deployJdk
java-version: 21
distribution: 'oracle'
- name: Setup Maven
uses: stCarolas/setup-maven@v.4.5
with:
maven-version: '3.9.6'
- name: Cache SonarCloud packages
uses: actions/cache@v3
with:
path: ~/.sonar/cache
key: ${{ runner.os }}-sonar
restore-keys: ${{ runner.os }}-sonar
- name: Cache Maven packages
uses: actions/cache@v3
with:
path: ~/.m2
key: ${{ runner.os }}-m2-${{ hashFiles('**/pom.xml') }}
restore-keys: ${{ runner.os }}-m2
- name: Build and analyze
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} # Needed to get PR information, if any
SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
run: mvn -N -Pcoverage,POST-SNAPSHOT -Dgpg.skip -Dpgpverify.skip --update-snapshots -B verify sonar:sonar