Feature #10879
closed
Support an option (environment variable) to provide specific places for build bases
Added by Evgeny Novikov almost 3 years ago.
Updated over 2 years ago.
Description
In some use cases, e.g. for CI, it has sense to refer build bases stored in particular places rather than in the standard one. At the moment it is implemented in a cheat way. If one does not specify build bases at the initial deployment, they are automatically searched for inside a repository, in subdirectory "build bases". This is not great at all, since even after users install build bases in a normal way, they could not be found. Moreover, searching in one particular place is not flexible, since it may be more convenient to use build bases stored in other places.
- Subject changed from Support an option (evironment variable) to provide specific places for build bases to Support an option (environment variable) to provide specific places for build bases
- Assignee changed from Ilya Shchepetkov to Evgeny Novikov
Ilya is overloaded, so, I will do this myself. Moreover, this change will make it possible to improve the workflow of CI that I responsible for.
- Status changed from New to Closed
I did this in branch opt-for-data-dir and tested that the new command-line option --data-directory does allow to provide a path to directory that will be searched for build bases. The branch was merged to master in b13b5c187.
BTW, the situation was a bit worse than it was described. Those users who did not provide some list of build bases for initial deployment (this is a bit unusual since the default deployment configuration file enumerates 3 simple build bases) were implicitly switched to using directory "build bases" as the Klever data directory forever. So even after adding some build bases to the deployment configuration file and updating Klever, they were not found by Klever even though they were successfully installed. The reason was that the search directory was changed at the installation.
Also available in: Atom
PDF