Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API/UI/Documentation - How to I specify the path to an inventory in a repository #1950

Open
mikaelparkefelt opened this issue Apr 18, 2024 · 3 comments

Comments

@mikaelparkefelt
Copy link

mikaelparkefelt commented Apr 18, 2024

image
image
image

I have configured the container to have the root path for SEMAPHORE_PLAYBOOK_PATH to be /playbooks.

But where are repositories located?

I need to specify a inventory YML file from a repository..... How do I do this?

I can't find any documentation and nothing in the UI that gives me the hint on how to do it.

What path is repositories clone to and how should i specify a path the an inventory file that is located in repository Rxxx and the inventory YML file is /path/to/inventory.yml in the repository?

Right now I need to know the path to the inventory file in Rxxx.

Please add documentation and make it simple to select a file from a repository.

@bodzio4749
Copy link

bodzio4749 commented Apr 18, 2024

From what I have managed to discover the repositories used during the task runs are located by the runner(s) inside /tmp/semaphore directory. This directory is also considered as "HOME" during runs.
Update: I did not answer the questions about repositories, so... Inside the /tmp/semaphore directories runners save multiple inventories (refreshed for each tasks) and the project directories (downloaded from each specified repository) are saved in subdirectory names like repository_n_n (example repository_1_1).

@mikaelparkefelt
Copy link
Author

Is n a sequence number so _1_1, _2_2, _3_3 etc?

@bodzio4749
Copy link

Is n a sequence number so _1_1, _2_2, _3_3 etc?

yes.

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

No branches or pull requests

2 participants