Do not ship Angular build cache in release tarballs

Bug #2048907 reported by Galen Charlton
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Medium
Unassigned
3.11
Fix Released
Medium
Unassigned

Bug Description

As of Angular v13, its build cache is now persistent by default. That cache lives in Open-ILS/src/eg2/.angular/cache, but is needed only when (re)building the Angular app. Consequently, it does not need to be included in the release tarballs, and excluding it will save a significant amount of space.

Revision history for this message
Galen Charlton (gmc) wrote :

Patch is available in the working branch user/gmcharlt/lp2048907_exclude_angular_build_cache_from_tarball / https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/gmcharlt/lp2048907_exclude_angular_build_cache_from_tarball

tags: added: pullrequest
Changed in evergreen:
importance: Undecided → Medium
tags: added: release-process
Revision history for this message
Jane Sandberg (sandbergja) wrote :

Good catch, Galen! Thanks for this patch.

I tried creating simple tarballs with `build/tools/make_release -i -n -x -v 3.12.1 -F 3.12.0 -f origin/tags/rel_3_12_0 -c`. Without this patch, the tarball was 124 GB! With the patch, it's only 85 GB.

I went through the installation steps (https://evergreen-ils.org/documentation/install/README_3_12.html) using the tarball I made with this patch. The angular client still worked just fine.

Pushed to rel_3_11 and above.

Changed in evergreen:
status: New → Fix Committed
milestone: none → 3.12.1
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.