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
4c32936367
SongodaCore/.github/workflows/build.yml

97 lines
3.4 KiB
YAML
Raw Normal View History

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: Build
on:
push:
GitHub Actions: Remove listening for pushes to development-v3 branch The branch does not longer exist and has been merged
2023-05-07 18:25:34 +02:00
branches: [ master, development ]
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
tags:
- 'v*'
pull_request:
types: [ opened, synchronize, reopened ]
permissions: read-all
env:
DEPLOYMENT_POM_PATH: ./Core/dependency-reduced-pom.xml
DEPLOYMENT_ARTIFACT_DIR: ./Core/target
GitHub Actions: Updates some mentions of Songoda to represent rename
2023-06-11 00:41:05 +02:00
DEPLOYMENT_ARTIFACT_SELECTOR: CraftaroCore-*.jar
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
jobs:
Tests:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: Prepare Workspace
uses: ./.github/actions/setup_project_workspace
- name: Run tests
run: mvn -B clean test
Build:
name: Build + Deploy
runs-on: ubuntu-latest
needs: [ Tests ]
steps:
GitHub Actions: Updates actions/checkout from v2 to v3 Somehow Dependabot errors out when trying to check for updates
2023-05-07 18:40:23 +02:00
- uses: actions/checkout@v3
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
uses: ./.github/actions/setup_project_workspace
with:
GitHub Actions: Updates the names of some secrets/variables in use
2023-05-23 20:06:39 +02:00
maven_username: ${{ secrets.PLUGINS_MAVEN_REPO_USERNAME }}
maven_password: ${{ secrets.PLUGINS_MAVEN_REPO_PASSWORD }}
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: Set project version
GitHub Actions: Updates some mentions of Songoda to represent rename
2023-06-11 00:41:05 +02:00
uses: craftaro/GH-Commons/.github/actions/maven_set_project_version@master
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
with:
append_snapshot: ${{ github.ref_type == 'tag' && 'false' || 'true' }}
version: ${{ github.ref_type == 'tag' && github.ref_name || '' }}
GitHub Actions: Set increment_version to patch outside of tags When we release v.2.20.1 and add a commit, v2.20.1-SNAPSHOT is published, which is not the correct version. patch-level isn't right either always, but I think that's a good compromise for now.
2023-05-07 14:58:39 +02:00
increment_version: ${{ github.ref_type == 'tag' && '' || 'patch' }}
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: Build with Maven
run: mvn -B -Duser.name="GitHub Actions on $GITHUB_REPOSITORY (id=$GITHUB_RUN_ID)" -DskipTests clean package
- name: Sign jar archives
GitHub Actions: Updates some mentions of Songoda to represent rename
2023-06-11 00:41:05 +02:00
uses: craftaro/GH-Commons/.github/actions/sign_jars@master
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
with:
jar_file_selector: ${{ env.DEPLOYMENT_ARTIFACT_DIR }}/${{ env.DEPLOYMENT_ARTIFACT_SELECTOR }}
GitHub Actions: Updates the names of some secrets/variables in use
2023-05-23 20:49:30 +02:00
keystore_gpg_encrypted: ${{ secrets.PLUGINS_JARSIGNER_KEYSTORE_GPG }}
keystore_gpg_password: ${{ secrets.PLUGINS_JARSIGNER_KEYSTORE_GPG_PASSWORD }}
keystore_password: ${{ secrets.PLUGINS_JARSIGNER_KEYSTORE_PASSWORD }}
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: 'Upload Build Artifacts'
uses: actions/upload-artifact@v3
with:
name: ${{ github.event.repository.name }}
path: ${{ env.DEPLOYMENT_ARTIFACT_DIR }}/${{ env.DEPLOYMENT_ARTIFACT_SELECTOR }}
- name: Deploy to Maven repo
GitHub Actions: Only deploy to maven repo on push event and not PRs
2023-05-07 18:25:00 +02:00
if: ${{ github.event_name == 'push' }}
GitHub Actions: Updates some mentions of Songoda to represent rename
2023-06-11 00:41:05 +02:00
uses: craftaro/GH-Commons/.github/actions/maven_deploy@master
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
with:
GitHub Actions: Updates the names of some secrets/variables in use
2023-05-23 20:06:39 +02:00
repository_url: ${{ vars.PLUGINS_MAVEN_REPO_URL_RELEASE }}
repository_url_snapshots: ${{ vars.PLUGINS_MAVEN_REPO_URL_SNAPSHOT }}
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
maven_pom_path: ${{ env.DEPLOYMENT_POM_PATH }}
maven_out_dir: ${{ env.DEPLOYMENT_ARTIFACT_DIR }}
- name: Deploy parent pom.xml to Maven repo
GitHub Actions: Only deploy to maven repo on push event and not PRs
2023-05-07 18:25:00 +02:00
if: ${{ github.event_name == 'push' }}
GitHub Actions: Updates some mentions of Songoda to represent rename
2023-06-11 00:41:05 +02:00
uses: craftaro/GH-Commons/.github/actions/maven_deploy@master
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
with:
GitHub Actions: Updates the names of some secrets/variables in use
2023-05-23 20:06:39 +02:00
repository_url: ${{ vars.PLUGINS_MAVEN_REPO_URL_RELEASE }}
repository_url_snapshots: ${{ vars.PLUGINS_MAVEN_REPO_URL_SNAPSHOT }}
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
only_deploy_pom: true
maven_out_dir: ${{ env.DEPLOYMENT_ARTIFACT_DIR }}
discord_webhook:
name: Send Discord Webhook
runs-on: ubuntu-latest
needs: [ Tests, Build ]
if: ${{ always() && (github.ref == 'refs/heads/master' || github.ref == 'refs/heads/development' || github.ref_type == 'tag') }}
steps:
GitHub Actions: Updates actions/checkout from v2 to v3 Somehow Dependabot errors out when trying to check for updates
2023-05-07 18:40:23 +02:00
- uses: actions/checkout@v3
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: Notify Webhook
GitHub Actions: Updates some mentions of Songoda to represent rename
2023-06-11 00:41:05 +02:00
uses: craftaro/GH-Commons/.github/actions/discord_send_job_results@master
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
with:
github_token: ${{ secrets.GITHUB_TOKEN }}
GitHub-Actions: Fix Discord webhook URL used
2022-08-19 10:52:49 +02:00
webhook_url: ${{ secrets.DISCORD_BUILD_STATUS_WEBHOOK }}
Reference in New Issue Copy Permalink