Skip to content
This repository has been archived by the owner on May 4, 2021. It is now read-only.

Model stages as topological sorted tree instead of list #280

Open
yiranwang52 opened this issue Oct 14, 2019 · 0 comments
Open

Model stages as topological sorted tree instead of list #280

yiranwang52 opened this issue Oct 14, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@yiranwang52
Copy link
Contributor

yiranwang52 commented Oct 14, 2019

Is your feature request related to a problem? Please describe.
Currently stages are treated as a list.
They should be modeled as a tree to handle cache ID and --target (#262) correctly.

Describe the solution you'd like
Model stages as a tree. Most changes should be in builder/build_plan.go

Tree is better for calculating cache IDs.
Currently stages inherit cache ID from last step of previous stage - which is not necessary if no files are copied between them.

Also in theory it's possible to execute some stages without "RUN" in parallel, and ignore those that not parent of "target" stage

@yiranwang52 yiranwang52 added the enhancement New feature or request label Oct 14, 2019
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant