[FOLIO-1740] tweak renovate configuration for platform-core Created: 25/Jan/19  Updated: 03/Jun/20  Resolved: 15/Apr/19

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

Type: Task Priority: P3
Reporter: Jakub Skoczen Assignee: John Malconian
Resolution: Done Votes: 0
Labels: platform-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks FOLIO-1577 Automated builds for FOLIO 'release' Closed
Sprint: Core: Platform - Sprint 61
Story Points: 2
Development Team: Core: Platform

 Description   

Configure renovate to issue a PR whenever a ui- module version has changed, including all major, minor and bugfix releases.



 Comments   
Comment by John Malconian [ 24/Mar/19 ]

After having enabled and observed Renovate for platform-core for a few months now, I do not believe it a good solution for any of the stripes platform repositories for a couple of reasons -

  • 9 out of 10 Renovate PRs fail. The stripes platform's package.json requires careful curation by a developer who understands FOLIO interdependencies.
  • This will cause of a flood of PRs that will trigger a lot of AWS ec2 resources to be used ( FOLIO-1739 Closed ).

I propose that we disable Renovate on platform-core and close this issue as 'Won't fix'.

Comment by John Malconian [ 03/Apr/19 ]

After thinking about this a bit more, we may want to go ahead and attempt to implement this with a more fine-tuned Renovate config.

Comment by John Malconian [ 15/Apr/19 ]

I've got the config working for two branches each - 'master' and 'q1-2019' on platform-core and platform-complete. The config specifies that only @folio patch revisions should be updated on the q1-2019 branch and @folio patch and minor revisions should be updated on the master branch. I ended up pinning most @folio deps so that when patches are released, Renovate will automatically trigger the PR. With '~', we'd have to trigger a PR manually in order to trigger a test build and generate new *.json/yarn.lock files.

Generated at Thu Feb 08 23:15:34 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.