Upstream/SongodaCore
1
0
Fork 0
mirror of https://github.com/songoda/SongodaCore.git synced 2024-11-30 14:03:23 +01:00
Code Issues Projects Releases Wiki Activity
0906cbf9c8
SongodaCore/.github/workflows/sonarcloud.yml

45 lines
1.0 KiB
YAML
Raw Normal View History

Adds SonarCloud (static analysis tool)
2021-10-30 15:22:23 +02:00
name: SonarCloud
on:
push:
GitHub Actions: Enable build and sonarcloud workflow for v3-dev-branch
2022-11-26 00:01:00 +01:00
branches: [ master, development, development-v3 ]
Adds SonarCloud (static analysis tool)
2021-10-30 15:22:23 +02:00
pull_request:
types: [ opened, synchronize, reopened ]
Introduce new CI/CD pipeline using GitHub Actions A lot is happening in this release! tl;dr: GitHub Actions runs tests, compiles the project, signs the jar files, deploys them to the Maven repo; Pushing a git tag issues a release instead of snapshot deployment; -SNAPSHOT is always added to the version otherwise; Core Version is now injected by maven instead of manually updating it in one of the classes We now use GitHub Actions to run automated tests, compile the project, sign the resulting jar files, and always deploy a version to the Maven repo. By default, a snapshot release is published but by creating a git tag, a release deploy can be triggered. Additionally the Core version is not manually updated in one of the classes but injected after compiling it. I think I found the most stable and easiest way to do this in maven, although I'd have wished for it to be easier and maybe not after the class file has already been created.
2022-08-07 19:33:38 +02:00
permissions: read-all
env:
SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
SONAR_PROJECT_KEY: songoda_SongodaCore
Adds SonarCloud (static analysis tool)
2021-10-30 15:22:23 +02:00
jobs:
Introduce new CI/CD pipeline using GitHub Actions A lot is happening in this release! tl;dr: GitHub Actions runs tests, compiles the project, signs the jar files, deploys them to the Maven repo; Pushing a git tag issues a release instead of snapshot deployment; -SNAPSHOT is always added to the version otherwise; Core Version is now injected by maven instead of manually updating it in one of the classes We now use GitHub Actions to run automated tests, compile the project, sign the resulting jar files, and always deploy a version to the Maven repo. By default, a snapshot release is published but by creating a git tag, a release deploy can be triggered. Additionally the Core version is not manually updated in one of the classes but injected after compiling it. I think I found the most stable and easiest way to do this in maven, although I'd have wished for it to be easier and maybe not after the class file has already been created.
2022-08-07 19:33:38 +02:00
Analyze:
Adds SonarCloud (static analysis tool)
2021-10-30 15:22:23 +02:00
runs-on: ubuntu-latest
Update required snakeyaml version from 1.26 to 1.30 (#41) We probably want to take a look at what Spigot 1.8 comes with and if we are compatible or if we want to shade the lib into the Core instead. Maybe we can have some kind of automatic legacy system that downloads an addional jar automatically when an unsupported Spigot version is detected... Lets see what time brings
2022-04-27 21:42:15 +02:00
Adds SonarCloud (static analysis tool)
2021-10-30 15:22:23 +02:00
steps:
Introduce new CI/CD pipeline using GitHub Actions A lot is happening in this release! tl;dr: GitHub Actions runs tests, compiles the project, signs the jar files, deploys them to the Maven repo; Pushing a git tag issues a release instead of snapshot deployment; -SNAPSHOT is always added to the version otherwise; Core Version is now injected by maven instead of manually updating it in one of the classes We now use GitHub Actions to run automated tests, compile the project, sign the resulting jar files, and always deploy a version to the Maven repo. By default, a snapshot release is published but by creating a git tag, a release deploy can be triggered. Additionally the Core version is not manually updated in one of the classes but injected after compiling it. I think I found the most stable and easiest way to do this in maven, although I'd have wished for it to be easier and maybe not after the class file has already been created.
2022-08-07 19:33:38 +02:00
- uses: actions/checkout@v3
GitHub-Actions: Only run SonarCloud when token is set Pull Requests often don't have the token (e.g. somebody outside of Songoda created it)
2022-01-02 22:50:31 +01:00
if: ${{ env.SONAR_TOKEN != null }}
Adds SonarCloud (static analysis tool)
2021-10-30 15:22:23 +02:00
with:
Introduce new CI/CD pipeline using GitHub Actions A lot is happening in this release! tl;dr: GitHub Actions runs tests, compiles the project, signs the jar files, deploys them to the Maven repo; Pushing a git tag issues a release instead of snapshot deployment; -SNAPSHOT is always added to the version otherwise; Core Version is now injected by maven instead of manually updating it in one of the classes We now use GitHub Actions to run automated tests, compile the project, sign the resulting jar files, and always deploy a version to the Maven repo. By default, a snapshot release is published but by creating a git tag, a release deploy can be triggered. Additionally the Core version is not manually updated in one of the classes but injected after compiling it. I think I found the most stable and easiest way to do this in maven, although I'd have wished for it to be easier and maybe not after the class file has already been created.
2022-08-07 19:33:38 +02:00
fetch-depth: 0
Adds SonarCloud (static analysis tool)
2021-10-30 15:22:23 +02:00
Introduce new CI/CD pipeline using GitHub Actions A lot is happening in this release! tl;dr: GitHub Actions runs tests, compiles the project, signs the jar files, deploys them to the Maven repo; Pushing a git tag issues a release instead of snapshot deployment; -SNAPSHOT is always added to the version otherwise; Core Version is now injected by maven instead of manually updating it in one of the classes We now use GitHub Actions to run automated tests, compile the project, sign the resulting jar files, and always deploy a version to the Maven repo. By default, a snapshot release is published but by creating a git tag, a release deploy can be triggered. Additionally the Core version is not manually updated in one of the classes but injected after compiling it. I think I found the most stable and easiest way to do this in maven, although I'd have wished for it to be easier and maybe not after the class file has already been created.
2022-08-07 19:33:38 +02:00
- name: Prepare Workspace
GitHub-Actions: Only run SonarCloud when token is set Pull Requests often don't have the token (e.g. somebody outside of Songoda created it)
2022-01-02 22:50:31 +01:00
if: ${{ env.SONAR_TOKEN != null }}
Introduce new CI/CD pipeline using GitHub Actions A lot is happening in this release! tl;dr: GitHub Actions runs tests, compiles the project, signs the jar files, deploys them to the Maven repo; Pushing a git tag issues a release instead of snapshot deployment; -SNAPSHOT is always added to the version otherwise; Core Version is now injected by maven instead of manually updating it in one of the classes We now use GitHub Actions to run automated tests, compile the project, sign the resulting jar files, and always deploy a version to the Maven repo. By default, a snapshot release is published but by creating a git tag, a release deploy can be triggered. Additionally the Core version is not manually updated in one of the classes but injected after compiling it. I think I found the most stable and easiest way to do this in maven, although I'd have wished for it to be easier and maybe not after the class file has already been created.
2022-08-07 19:33:38 +02:00
uses: ./.github/actions/setup_project_workspace
Adds Minecraft 1.18.2 support
2022-03-18 14:32:20 +01:00
Adds SonarCloud (static analysis tool)
2021-10-30 15:22:23 +02:00
- name: 'Cache: SonarCloud'
Adds Minecraft 1.18.2 support
2022-03-18 14:32:20 +01:00
if: ${{ env.SONAR_TOKEN != null }}
Introduce new CI/CD pipeline using GitHub Actions A lot is happening in this release! tl;dr: GitHub Actions runs tests, compiles the project, signs the jar files, deploys them to the Maven repo; Pushing a git tag issues a release instead of snapshot deployment; -SNAPSHOT is always added to the version otherwise; Core Version is now injected by maven instead of manually updating it in one of the classes We now use GitHub Actions to run automated tests, compile the project, sign the resulting jar files, and always deploy a version to the Maven repo. By default, a snapshot release is published but by creating a git tag, a release deploy can be triggered. Additionally the Core version is not manually updated in one of the classes but injected after compiling it. I think I found the most stable and easiest way to do this in maven, although I'd have wished for it to be easier and maybe not after the class file has already been created.
2022-08-07 19:33:38 +02:00
uses: actions/cache@v3
Adds SonarCloud (static analysis tool)
2021-10-30 15:22:23 +02:00
with:
path: ~/.sonar/cache
key: ${{ runner.os }}-sonar
GitHub Actions: Adds missing empty line between steps in sonarcloud.yml
2022-11-26 20:26:01 +01:00
Adds SonarCloud (static analysis tool)
2021-10-30 15:22:23 +02:00
- name: Analyze project
GitHub-Actions: Only run SonarCloud when token is set Pull Requests often don't have the token (e.g. somebody outside of Songoda created it)
2022-01-02 22:50:31 +01:00
if: ${{ env.SONAR_TOKEN != null }}
Introduce new CI/CD pipeline using GitHub Actions A lot is happening in this release! tl;dr: GitHub Actions runs tests, compiles the project, signs the jar files, deploys them to the Maven repo; Pushing a git tag issues a release instead of snapshot deployment; -SNAPSHOT is always added to the version otherwise; Core Version is now injected by maven instead of manually updating it in one of the classes We now use GitHub Actions to run automated tests, compile the project, sign the resulting jar files, and always deploy a version to the Maven repo. By default, a snapshot release is published but by creating a git tag, a release deploy can be triggered. Additionally the Core version is not manually updated in one of the classes but injected after compiling it. I think I found the most stable and easiest way to do this in maven, although I'd have wished for it to be easier and maybe not after the class file has already been created.
2022-08-07 19:33:38 +02:00
run: >
Revert "GitHub Actions: Skip automated tests when running SonarCloud" This reverts commit 59f4adfc6fb0277608f9f4004dba42dafffffb4e. We need the tests to generate the test coverage report. Didn't think of that.
2022-11-26 15:36:29 +01:00
mvn -B \
Introduce new CI/CD pipeline using GitHub Actions A lot is happening in this release! tl;dr: GitHub Actions runs tests, compiles the project, signs the jar files, deploys them to the Maven repo; Pushing a git tag issues a release instead of snapshot deployment; -SNAPSHOT is always added to the version otherwise; Core Version is now injected by maven instead of manually updating it in one of the classes We now use GitHub Actions to run automated tests, compile the project, sign the resulting jar files, and always deploy a version to the Maven repo. By default, a snapshot release is published but by creating a git tag, a release deploy can be triggered. Additionally the Core version is not manually updated in one of the classes but injected after compiling it. I think I found the most stable and easiest way to do this in maven, although I'd have wished for it to be easier and maybe not after the class file has already been created.
2022-08-07 19:33:38 +02:00
verify \
org.sonarsource.scanner.maven:sonar-maven-plugin:sonar \
"-Dsonar.projectKey=$SONAR_PROJECT_KEY"
Adds SonarCloud (static analysis tool)
2021-10-30 15:22:23 +02:00
env:
Introduce new CI/CD pipeline using GitHub Actions A lot is happening in this release! tl;dr: GitHub Actions runs tests, compiles the project, signs the jar files, deploys them to the Maven repo; Pushing a git tag issues a release instead of snapshot deployment; -SNAPSHOT is always added to the version otherwise; Core Version is now injected by maven instead of manually updating it in one of the classes We now use GitHub Actions to run automated tests, compile the project, sign the resulting jar files, and always deploy a version to the Maven repo. By default, a snapshot release is published but by creating a git tag, a release deploy can be triggered. Additionally the Core version is not manually updated in one of the classes but injected after compiling it. I think I found the most stable and easiest way to do this in maven, although I'd have wished for it to be easier and maybe not after the class file has already been created.
2022-08-07 19:33:38 +02:00
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
Reference in New Issue Copy Permalink