-
Notifications
You must be signed in to change notification settings - Fork 4
cicd: Adding a GitHub release workflow #103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
I don't really understand why we are usingMakefiles when similar actions was done by CircleCI; |
because you can run everything locally and you don't depend on the underlying CI/CD. |
Add Makefile so everyone can build and make releases easily. Added a CI/CD pipeline job to release to GitHub. Signed-off-by: Ronny Trommer <ronny@no42.org>
Describe the procedure how to create release. Signed-off-by: Ronny Trommer <ronny@no42.org>
Signed-off-by: Ronny Trommer <ronny@no42.org>
Signed-off-by: Ronny Trommer <ronny@no42.org>
Signed-off-by: Ronny Trommer <ronny@no42.org>
Signed-off-by: Ronny Trommer <ronny@no42.org>
... anything else? |
The plugin uses java 11, why do we want the CICD to use java 17? |
Signed-off-by: Ronny Trommer <ronny@no42.org>
See source/target. Nevertheless, this is outdated and can be replaced with release. See https://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-release.html |
Signed-off-by: Ronny Trommer <ronny@no42.org>
Allow users to build from source with a release workflow. Added a GitHub release job in CI/CD. I have also replaced the legacy container images for OpenJDK 11 and build with the latest Ubuntu 24 LTS. The OpenJDK build environment is upgraded from 11 to 17 because it isn't available in the Ubuntu machine images.
Resolve: #102