Commits on Source 20
-
Jim MacArthur authored
There is nothing in ArtifactCacheSpec that's actually specific to artifacts, so I've made it a CAS class so we can use the same spec for remote execution.
-
Jim MacArthur authored
Since the artifact cache and remote execution share the same local CAS store, they should share the same CASCache object. Moving this into context allows us to do this.
-
Jim MacArthur authored
Uses the new config options introduced earlier to specify remote exec storage and execution service.
-
Jim MacArthur authored
-
Jim MacArthur authored
Tests that we get a sensible error message when we specify incomplete or wrong information in the configuration for remote execution.
-
Jim MacArthur authored
-
Jim MacArthur authored
The port number must come after the hostname and before the path. The path is ignored by CASCache anyway, so including it is misleading.
-
Jim MacArthur authored
Split remote execution from artifact cache Closes #750 See merge request !946
-
Jonathan Maw authored
i.e. with a given directory and filename, check parent directories until either a directory with the filename is found, or you reach the root of the filesystem.
-
Jonathan Maw authored
WorkspaceProject contains all the information needed to refer back to a project from its workspace (currently this is the project path and the element used to create this workspace) This is stored within a WorkspaceProjectCache object, which keeps WorkspaceProjects around so they don't need to be loaded from disk repeatedly.
-
Jonathan Maw authored
-
Jonathan Maw authored
-
Jonathan Maw authored
Searching for the workspace file is preferred to searching for the project file for the moment, because it avoids the circumstance of the workspaces being inside a directory where a higher-level directory may have project.conf (but may not be a buildstream project).
-
Jonathan Maw authored
-
Jonathan Maw authored
-
Jonathan Maw authored
-
Jonathan Maw authored
-
Jonathan Maw authored
cli: Interactively warn if the user is trying to close the workspace they're using to load the project This involves changes in: * _stream.py: * Add the helper Stream.workspace_is_required() * userconfig.yaml: * Add a default value for prompt.really-workspace-close-project-inaccessible * _context.py: * Load the prompt 'really-workspace-close-project-inaccessible' from user config. * cli.py: * If buildstream is invoked interactively, prompt the user to confirm that they want to close the workspace they're using to load this project. -
Jonathan Maw authored
-
Jonathan Maw authored