Skip to content

Lighter deployment artifacts #599

Open
@kanej

Description

@kanej

We should make our deployment artifacts lighter and friendlier for version control.

There are two things obvious paths forward here:

  1. Make the BuildInfo files lighter. This can be done by not saving their output information.
  2. Journal pruning: We should consider "compressing" the journal by pruning it after successful runs. For example, if a deployment future is executed successfully, we can replace all of its messages with a single one.

Metadata

Metadata

Assignees

No one assigned

    Labels

    status:readyThis issue is ready to be worked ontype:epicA bigger effort that involves multiple issues and PRs

    Type

    No type

    Projects

    Status

    No status

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions