You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We like to add support to lage for external build scheduler.
I'm using this issue as an overview and will create
There are larger build systems that can embed other build systems like BuildXL.
Modern build systems provide great features like sandboxing to ensure dependencies and outputs are declared to what actually happens. With reliable inputs and outputs one can distribute and cache builds reliably to increaes performance.
I want to extend Lage to allow for the specification.
I believe this can be done through a few updates / extensions to Lage.
I have another proposal for you - as I was working to integrate a certain kind of "background job / breakaway process w/ buildxl", I realized that this transferred the responsibility of tracking inputs/outputs back to lage. There is a noticeable issue where we shifted this heavy burden towards something that doesn't do sandboxing (lage). It would be amazing to augment lage with this natively so we don't have to solely rely on hard coded input / output globs.
Okay, so I'll come up with a new definition for JS to create a build graph. I'll just work directy with BuildXL folks on this and then we can consider writing an adapter. I'll abandon this effort for now.
Overview
We like to add support to lage for external build scheduler.
I'm using this issue as an overview and will create
There are larger build systems that can embed other build systems like BuildXL.
Modern build systems provide great features like sandboxing to ensure dependencies and outputs are declared to what actually happens. With reliable inputs and outputs one can distribute and cache builds reliably to increaes performance.
I want to extend Lage to allow for the specification.
I believe this can be done through a few updates / extensions to Lage.
These are the proposals in-order to consume:
PR: Add extra info to lage info for #815 #836
PR: Add support to include pipeline configuraiton in pacakge.json files #817 #837
PR: Add merge logic for targetConfig #816 #838
And a few bugfixes
The text was updated successfully, but these errors were encountered: