feat: Incremental builds, with an in-memory read cache#49
Open
kevinrenskers wants to merge 2 commits intodevelopfrom
Open
feat: Incremental builds, with an in-memory read cache#49kevinrenskers wants to merge 2 commits intodevelopfrom
kevinrenskers wants to merge 2 commits intodevelopfrom
Conversation
…y file change, Saga is now kept alive and just reruns the pipeline, while caching the entire read step
kevinrenskers
force-pushed
the
feat/keep-running
branch
from
0a5b0d3 to
b2a8c60
Compare
kevinrenskers
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Instead of
saga devalways starting a brand new build on every file change, Saga is now kept alive and just reruns the pipeline, while caching the entire read step. If you only change a markdown file, only that one markdown file has to be read and processed, the rest comes from the cache. It makes things a LOT faster, also when working on CSS changes for example.When a Swift file is changed, the build is compiled and started again.
It does mean that simply putting code above or below your Saga pipeline now longer works; it now has to be part of the pipeline so it can be executed every cycle. For this the new
beforeReadandafterWritehooks are introduced.This feature will depend on a new release of saga-cli (see loopwerk/saga-cli#1), and will be a major version bump.