[BUILD-875] Improve magnolia-mgmt-ui deployment Pipeline Created: 05/Aug/22  Updated: 23/Mar/23

Status: Open
Project: Build
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: Roberto Gomez Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
[ ]* Implement cache for node_modules
[ ]* Make and use custom docker image
[ ]* Bundle files with webpack
[ ]* Store zip files in a releases repository
Team: Foundation

 Description   

The current deployment pipeline for the magnolia-mgmt-project works, but some it might also take advantage of some improvements:

  • Great ammount of the deployment time is spent downloading node_modules.
    See if this can be speed up via pnpm.ioor any [other means|https://stackoverflow.com/questions/46870020/cache-npm-dependencies-on-jenkins-pipeline 
  • We are installing tools like amplify or aws cli each time, maybe we can make a custom docker image with all the necessary tooling installed.
  • Probably it's a good idea to bundle the deployment files using webpack.
  • It's a good idea to keep a zip file for each release. Currently we are storing those in the same bucket as the deployed files. See where is the best place to store the release zip file.

Generated at Sun Feb 11 23:46:01 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.