Migrate FOLIO backend module builds to GitHub Actions (FOLIO-3692)

[FOLIO-3629] Pilot for a GA pipeline to build and publish backend modules Created: 07/Nov/22  Updated: 26/Mar/23  Resolved: 13/Feb/23

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None
Parent: Migrate FOLIO backend module builds to GitHub Actions

Type: Task Priority: TBD
Reporter: Ankita Sen Assignee: Ankita Sen
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to FOLIO-3678 Ensure API-related GitHub Workflows a... Closed
relates to MODUSERS-349 build-mvn.yml and build-mvn-release.y... Closed
relates to FOLIO-3185 Improve Docker Hub README generator t... Open
relates to FOLIO-3349 Include exception in GH Actions workf... Closed
relates to FOLIO-3700 Develop the release Github Actions wo... In QA
Sprint: DevOps Sprint 152, DevOps Sprint 154, DevOps Sprint 155, DevOps Sprint 157, DevOps Sprint 158
Development Team: FOLIO DevOps
Epic Link: Migrate FOLIO backend module builds to GitHub Actions
RCA Group: TBD

 Description   

Add the buildMvn GitHub Action workflow to the backend repositories to replace the Jenkins pipeline and deprecate use of Jenkinsfile.



 Comments   
Comment by David Crossley [ 14/Feb/23 ]

Some initial feedback:

  • Using old versions of actions dependencies, e.g.
    • actions/checkout@v2 needs to be checkout@v3
    • actions/setup-java@v1 needs to be setup-java@v3
  • Using head of master with fjogeleit/http-request-action could be problematic. Should be v1
  • Consider using "cache" with actions/setup-java
  • At "Check for Module Descriptor" consider swapping the exclamation marks to the "not found" case.
  • Jenkinsfile at mod-users branch should be removed
  • Differences with mod-users (whitespace and final newline and SQ_HOST)
  • Should be using the FOLIO-3349 Closed Include exception in GH Actions workflows to skip markdown-only edits
Generated at Thu Feb 08 23:29:32 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.