feat: add maven production release

[kunal0137]

Description

add maven production release github action

Changes Made

yaml args in .gitlab file

[github-actions]

@CodiumAI-Agent /describe

[QodoAI-Agent]

Title

feat: add maven production release

---

User description

Description

add maven production release github action

Changes Made

yaml args in .gitlab file

---

PR Type

• Enhancement

---

Description

• Add new CI job for production release.

• Configure pnpm build and Maven deployment.

• Install dependencies and required tools.

• Include cleanup step to remove Maven cache.

---

Changes walkthrough 📝

	Relevant files
Enhancement	ci-pnpm-maven.yml Add CI job for Maven production deployment.                            .github/workflows/ci-pnpm-maven.yml Introduced new job pnpm_build_release. Set conditional execution for release branch. Added steps for code checkout, dependency installation, build, deploy, and cleanup. +36/-0

---

Need help?

Type /help how to ... in the comments thread for any questions about PR-Agent usage.

Check out the documentation for more information.

[github-actions]

@CodiumAI-Agent /review

[github-actions]

@CodiumAI-Agent /improve

[QodoAI-Agent]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 3 🔵🔵🔵⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Configuration Review the conditional triggers and environment variable usage to ensure that the workflow safely and reliably initiates production deployments. Confirm that the self-hosted runner and container image fulfill production and security requirements. pnpm_build_release: runs-on: self-hosted if: ${{ vars.RELEASE == 'TRUE' && github.event_name == 'workflow_dispatch' && (github.ref_name == 'main' || github.ref_name == 'dev') }} container: image: node:18.16.1-bullseye steps: - name: Checkout code uses: actions/checkout@v4 - name: Install dependencies run: | echo "Event Name: ${{ github.event_name }}" echo "Release: ${{ vars.RELEASE }}" apt-get update apt-get install -y maven gnupg2 echo "${{ secrets.GPG_PRIVATE_KEY }}" | gpg2 --batch --import echo "keyserver keyserver.ubuntu.com" > ~/.gnupg/gpg.conf gpg2 --refresh-key npm install -g pnpm@8 pnpm install - name: Build env: NX_REJECT_UNKNOWN_LOCAL_CACHE: 0 run: npx nx run-many -t build -p @semoss/client @semoss/legacy --verbose - name: Deploy with Maven shell: bash run: | mvn $MAVEN_CLI_OPTS deploy -P deploy -Dci.version=${{ vars.VERSION }} env: GITHUB_REF: ${{ github.ref }} - name: Remove cache to save space run: rm -rf .m2/repository/org/semoss

[QodoAI-Agent]

PR Code Suggestions ✨

Category	Suggestion	Impact
Possible issue	Fail fast on errors Prepend a "set -e" to the bash script so that the deployment step fails immediately upon error. .github/workflows/ci-pnpm-maven.yml [194-197] - name: Deploy with Maven shell: bash run: | + set -e mvn $MAVEN_CLI_OPTS deploy -P deploy -Dci.version=${{ vars.VERSION }} Suggestion importance[1-10]: 8 __ Why: The suggestion correctly addresses error handling in the deployment step by adding "set -e" to the bash script, which improves reliability in case of failure.	Medium
	Apply batch mode for GPG Append the "--batch" flag to the gpg2 refresh-key command to avoid interactive prompts. .github/workflows/ci-pnpm-maven.yml [183-185] echo "${{ secrets.GPG_PRIVATE_KEY }}" | gpg2 --batch --import echo "keyserver keyserver.ubuntu.com" > ~/.gnupg/gpg.conf -gpg2 --refresh-key +gpg2 --batch --refresh-key Suggestion importance[1-10]: 6 __ Why: The suggestion adds the "--batch" flag to the gpg2 refresh-key command to prevent interactive prompts, which is a useful improvement in a CI environment.	Low

[github-actions]

@CodiumAI-Agent /update_changelog