Felipe Lalanne 578de7bcd4 Process livepush build logs inline ... When using livepush, the CLI parses the build logs to obtain the stage image ids, which are necessary for properly running livepush. This process used to store the full log output in memory before parsing the logs for obtaining the stage ids. We have seen this cause issues before because of the excessive memory usage and it is one the suspects of #2165, which is blocking the update to Node 14 Change-type: patch		2023-01-03 12:29:54 -03:00
..
device	Process livepush build logs inline	2023-01-03 12:29:54 -03:00
docker.spec.ts	build: Ensure HTTPS is used with dockerPort 2376 or with ca/cert/key	2022-04-07 00:14:03 +01:00
eol-conversion.spec.ts	Build: switch from using inline-source via gulp to using it directly	2022-01-04 15:03:05 +00:00
helpers.spec.ts	Update 'balena-lint' and apply new prettier rules	2020-06-15 23:53:07 +01:00
normalization.spec.ts	Convert tags, tag set, tag rm to oclif.	2020-05-28 19:49:23 +02:00
qemu.spec.ts	Switch to balena-compose	2022-07-14 13:05:21 +00:00
tarDirectory.spec.ts	build/deploy/push: Remove deprecated '--[no]gitignore' option	2021-12-23 15:34:08 +00:00
update.spec.ts	Include link to Wiki release notes in version update notifications	2022-03-08 18:25:08 +00:00
validation.spec.ts	Rename applications to fleets (stage 1). See: https://git.io/JRuZr	2021-08-09 12:12:03 +01:00