Skip to content
This repository has been archived by the owner on May 17, 2022. It is now read-only.

Rename the top-level master.cfg to production.cfg #164

Open
kou opened this issue Aug 16, 2019 · 2 comments
Open

Rename the top-level master.cfg to production.cfg #164

kou opened this issue Aug 16, 2019 · 2 comments

Comments

@kou
Copy link
Collaborator

kou commented Aug 16, 2019

I follow the "Install ursabot and the CLI" section https://github.com/ursa-labs/ursabot/blob/2d70547ab38a252b2f037642cc28ee6f75c8ff16/README.md#install-ursabot-and-the-cli and run ursabot desc as described. Then I got the following error:

$ ursabot desc
Configuration Errors:
 - directory /home/kou/.ursalabs-pass does not exist

How to initialize this?

It's not recommended that I use master.cfg in the repository?

@kszucs
Copy link
Contributor

kszucs commented Aug 17, 2019

@kou The top-level master.cfg is the production config for ci.ursalabs.org (it includes two project configurations from the projects directory). You should use the one under projects/arrow/master.cfg which doesn't define any secret provider or production related services.

So cd to projects/arrow then the Ursabot command will pick up the master.cfg from the current directory:

$ cd projects/arrow
$ ursabot -v desc
$ ursabot -v project build <builder-name>

@kszucs kszucs changed the title How to initialize secrets? Rename the top-level master.cfg to production.cfg Aug 17, 2019
@kou
Copy link
Collaborator Author

kou commented Aug 17, 2019

Thanks!
I'll use projects/arrow.

We should improve the "Install ursabot and the CLI" section for the next first time users. :-)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants