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

[FOLIO-3700] Develop the release Github Actions workflow for backend modules Created: 13/Feb/23  Updated: 13/Mar/23

Status: In QA
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: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to FOLIO-3185 Improve Docker Hub README generator t... Open
relates to FOLIO-3629 Pilot for a GA pipeline to build and ... Closed
relates to FOLIO-3701 Use Docker action provided by Github ... Closed
Sprint: DevOps Sprint 159, DevOps Sprint 160, DevOps Sprint 158
Development Team: FOLIO DevOps
Epic Link: Migrate FOLIO backend module builds to GitHub Actions
RCA Group: TBD

 Description   

Implement the CI workflow in Github Actions for the release pipelines of the backend modules.



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

I realise that not yet finished, but some initial feedback (similar to FOLIO-3629 Closed ):

  • 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.
  • The "name" property is malformed.
Generated at Thu Feb 08 23:30:03 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.