Hi Tristan, Le lun. 10 janv. 2022 à 06:23, Tristan Van Berkom <[email protected]> a écrit : > > I'd add to the list > > https://github.com/apache/buildstream/issues/1263 > > I think this is potentially (Caching buildtrees only works with > > BuildElement) > > This, I think what we're really talking about here is script elements, > or similar concoctions, and we probably don't want to cache anything > for a variety of elements (like compose or filter elements).
As is probably clear from my message, I pressed send without finishing my sentence. The issue isn't really about caching buildtrees, it's about running a shell in a failed sandbox. As such elements that don't have a sandbox (BST_RUN_COMMANDS = False) like compose or filter are not concerned by this at all. Indeed, this is mainly about the script element and possibly other custom elements (whether implemented using ScriptElement or not). The issue is currently that this core functionality that works fine with bst 1 simply doesn't work with anything that isn't a BuildElement, which would be a regression. I'm not advocating for supporting build trees for more elements, but rather to have an alternative for elements that don't have a build tree to still be able to shell into a failed sandbox, especially for local builds. Cheers, Abderrahim
