[FOLIO-3625] Configure platform-minimal similar to platform-complete Created: 02/Nov/22  Updated: 08/Nov/22  Resolved: 08/Nov/22

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: TBD
Reporter: John Malconian Assignee: John Malconian
Resolution: Done Votes: 0
Labels: platform-minimal
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks FOLIO-1730 Create folio/minimal Vagrant box Open
Sprint: DevOps Sprint 152
Development Team: FOLIO DevOps
RCA Group: TBD

 Description   

Set up the platform-minimal repository similar to platform-complete in terms of branches and CI. There should at least be protected main and snapshot branches and install.json files that are updated by Jenkins regularly.



 Comments   
Comment by Steve Ellis [ 02/Nov/22 ]

Platform minimal is mod-users, mod-permissions, mod-login, mod-authtoken, mod-configuration, mod-users-bl and mod-password-validator.

Another way to determine this to look at mod-users-bl's requires array in it's mod descriptor.

Comment by John Malconian [ 08/Nov/22 ]

platform-minimal is now configured similar to platform-complete. Specifically, in the following ways.

  • There are two, protected branches - 'master' and 'snapshot'. Master is a releases only branch. Snasphot consists of snapshots.
  • There is an Automation/build-platform-minimal-snapshot Jenkins job that runs hourly and updates the install.json, okapi-install.json, stripes-install.json, and yarn.lock files on the snapshot branch. The CI pipeline is the same as it is for platform-complete.
  • There is a Renovate configuration, renovate.json, that is responsible for opening PRs for updates to the master branch which is currently the in-progress Nolana release. When the release goes GA, a release branch can be also be created if needed/wanted.
Generated at Thu Feb 08 23:29:30 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.