summaryrefslogtreecommitdiffstats
path: root/build/fetch_and_patch_charts.sh
AgeCommit message (Collapse)AuthorFilesLines
2019-02-28Rename casablanca patch fileMilan Verespej1-1/+1
Since there is no difference in patching between 3.0.0 and 3.0.1 release there name of patchfile that includes this tag is unnecessary and confusing. Issue-ID: OOM-1687 Change-Id: I751398f15c38dab83e36ed0b8f555533497291f8 Signed-off-by: Milan Verespej <m.verespej@partner.samsung.com>
2019-02-06Use git format of patchesMilan Verespej1-1/+2
To avoid dependency on patch utility and to have standardized look of patch file this change uses git-format and git-apply to patch charts. Change-Id: I1c63334619bf6091b5ab50a4eebfadb3c28a2616 Issue-ID: OOM-1634 Signed-off-by: Milan Verespej <m.verespej@partner.samsung.com>
2019-02-06Setting-up NPM registry for dgbuilderMichal Ptacek1-0/+69
This commit is showing-up how OOM patches must be handled in casablanca release. In Dublin we would like to avoid this completely OOM-1610 so here we are just reproducing the same logic which was already implemented in Beijing for bash offline installer. In general it works in a way that OOM charts are patched during offline platform build and values are configured in install time using pre-install application role/hook. Change-Id: I1a2425ef63edd6bc08dcecf0fcae7fd6e553d0ed Issue-ID: OOM-1616 Signed-off-by: Michal Ptacek <m.ptacek@partner.samsung.com>