add maven release

[hupling]

Description

Short description or comments

Reference

Issues it-at-m/.github#43

Summary by CodeRabbit

• New Features
  • Introduced a new automated workflow for releasing Maven applications, including building Docker images and creating GitHub releases.
  • Users can manually trigger the release process with specified version inputs and application paths.

[hupling]

@it-at-m/sps zur Info

[hupling]

@ejcsid has the same opinion as me

[hupling]

@devtobi I would do the wrapper in a separate issue because you have in other workflows the same problem https://github.com/it-at-m/refarch-templates/blob/43-actions-to-create-releases/.github/workflows/maven-node-build.yaml#L23

I would do all together. so this mr is ready to merge

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes introduce a new GitHub Actions workflow file named release-maven-image.yaml. This workflow automates the release process for a Maven-based application, triggered manually with specific inputs for release and development versions, as well as the application path. It consists of three main jobs: release-maven, which handles the Maven release; build-image, which builds a Docker image; and create-github-release, which creates a GitHub release based on the Maven artifact.

Changes

File	Change Summary
.github/workflows/release-maven-image.yaml	New workflow file added to automate Maven release, Docker image build, and GitHub release creation.

Possibly related PRs

• add maven release #513: This PR introduces the same GitHub Actions workflow file release-maven-image.yaml and contains identical changes, indicating a direct match with the main PR.

Poem

In the meadow where the code does play,
A new workflow hops in, brightening the day.
With Maven and Docker, it dances in line,
Creating releases, oh how they shine! 🐇✨
A joyful release, let the bunnies cheer,
For automation's here, bringing us near!

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE

📥 Commits

Reviewing files that changed from the base of the PR and between 9968215 and 5dfe001.

📒 Files selected for processing (1)

• .github/workflows/release-maven-image.yaml (1 hunks)

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

seperate issue

[coderabbitai]

Actionable comments posted: 5

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE

📥 Commits

Reviewing files that changed from the base of the PR and between 7166150 and 9968215.

📒 Files selected for processing (1)

• .github/workflows/release-maven-image.yaml (1 hunks)

🧰 Additional context used

🪛 yamllint (1.35.1)

.github/workflows/release-maven-image.yaml

[warning] 3-3: truthy value should be one of [false, true]

(truthy)

---

[warning] 29-29: too few spaces before comment

(comments)

---

[error] 63-63: wrong indentation: expected 10 but found 9

(indentation)

🔇 Additional comments (1)

.github/workflows/release-maven-image.yaml (1)

32-40: Verify secrets availability

The Maven release step requires several sensitive credentials.

[DanielOber]

LGTM for now, further improvements and ideas will be resolved in separate issues

[hupling]

it-at-m/.github#82 hier das separate issue