gtristan commented on issue #1682: URL: https://github.com/apache/buildstream/issues/1682#issuecomment-1219124387
This is pretty non-trivial to change. If the problem is that bst-1 and bst-2 are sharing the same directories for their artifact caches, we should fix that with an error and ensure that bst-1 and bst-2 dont make any foolish attempts to access the same caches. We already require separate `buildstream.conf` files. > However there is something special about the artifact protos (other than the fact they are stored in a non-toplevel directory): they are stored as project/element-name/key and this is reflected in the UI (the bst artifact commands). Which is something that needs to be discussed. Do we really need all these? Can we somehow get the same UI? Yes we really need artifact names to be prefixed with human readable identifiable names rather than only with cache keys, as it forms the premise on which users can interact directly with artifacts. It is currently useful in: * Bash completion for any `bst artifact` commands * Glob patterns supported in `bst artifact` commands Some additional history, from the days of baserock, morph, YBD, we used to store artifacts as deterministically generated tarballs, and it was always important for the user to be able to _easily_ find the data they had recently generated, even though the tarballs were generated with their cache keys encoded into their names, the identifying names were used as directory prefixes such that users could easily obtain them, regardless of whether they still had access to the logs/terminal output which printed the cache key under which an artifact was generated. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
