Upstream/SongodaCore
1
0
Fork 0
mirror of https://github.com/songoda/SongodaCore.git synced 2024-11-27 12:35:12 +01:00
Code Issues Projects Releases Wiki Activity
72c96bc09a
SongodaCore/.github/dependabot.yml

17 lines
444 B
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
# Please see the documentation for all configuration options:
# https://help.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
version: 2
updates:
- package-ecosystem: "maven"
directory: "/"
Dependabot: Configure the target branch to be `development`
2022-08-19 10:53:17 +02:00
target-branch: "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
schedule:
interval: "monthly"
- package-ecosystem: "github-actions"
directory: "/"
Dependabot: Configure the target branch to be `development`
2022-08-19 10:53:17 +02:00
target-branch: "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
schedule:
interval: "monthly"
Reference in New Issue Copy Permalink