# Help with custom track repositories

**URL:** <https://discuss.elastic.co/t/help-with-custom-track-repositories/88110>\
**Category:** Elasticsearch\
**Tags:** rally\
**Created:** [June 2, 2017, 3:52pm UTC](https://discuss.elastic.co/t/help-with-custom-track-repositories/88110 "2017-06-02T15:52:16Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jspooner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jspooner/32/12984_2.png) [@jspooner](https://discuss.elastic.co/u/jspooner)\
**Post date:** [June 2, 2017, 3:52pm UTC](https://discuss.elastic.co/t/help-with-custom-track-repositories/88110/1 "2017-06-02T15:52:16Z")

</div>

I'm following the create [custom track repositories](https://esrally.readthedocs.io/en/latest/adding_tracks.html#custom-track-repositories) documentation and rally is throwing an error `fatal: 'origin' does not appear to be a git repository`.

I followed the directions but renamed the directory from private to verve.

```
cd ~/.rally/benchmarks/tracks
mkdir verve
cd verve
git init
# add your track now
git commit -a -m "Initial commit"

```

I created an new repo and added it to my **rally.ini**

```
[tracks]
default.url = https://github.com/elastic/rally-tracks
verve.url = https://github.com/FooBar/insights-rally-tracks

```

But when trying to list the tracks ( should be none at this time ) I'm getting this git error.

```
[jspooner]% esrally list tracks --track-repository=verve

    ________
   / __\____ _/ / /_ __
  / /_/ / __ `/ / / / / /
 / _, _/ /_/ / / / /_/ /
/_/ |_|\ __,_/_/_/\__ , /
                / ____ /

[INFO] Writing logs to /Users/jspooner/.rally/logs/rally_out_20170601T232552Z.log
Available tracks:

fatal: 'origin' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
[WARNING] Could not update tracks. Continuing with your locally available state.
error: pathspec 'master' did not match any file(s) known to git.
[ERROR] Cannot list. Cannot update track data in [/Users/jspooner/.rally/benchmarks/tracks/verve].

Getting further help:
*********************
* Check the log files in /Users/jspooner/.rally/logs for errors.
* Read the documentation at https://esrally.readthedocs.io/en/0.5.3/
* Ask a question in the forum at https://discuss.elastic.co/c/elasticsearch/rally
* Raise an issue at https://github.com/elastic/rally/issues and include the log files in /Users/jspooner/.rally/logs.

-------------------------------
[INFO] FAILURE (took 1 seconds)
-------------------------------
```

---

<div class="post-metadata">

**Author:** ![jspooner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jspooner/32/12984_2.png) [@jspooner](https://discuss.elastic.co/u/jspooner)\
**Post date:** [June 2, 2017, 4:15pm UTC](https://discuss.elastic.co/t/help-with-custom-track-repositories/88110/2 "2017-06-02T16:15:15Z")

</div>

Ok the documentation should note that you need to add the remote to that directory before updating the **rally.ini** file.

```
git remote add origin git@github.com:FooBar/insights-rally-tracks.git
git push -u origin master
```

---

<div class="post-metadata">

**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\
**Post date:** [June 19, 2017, 7:10am UTC](https://discuss.elastic.co/t/help-with-custom-track-repositories/88110/3 "2017-06-19T07:10:59Z")

</div>

Hi @jspooner,

I've opened [#288](https://github.com/elastic/rally/issues/288) to fix this.

Daniel

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 17, 2017, 7:11am UTC](https://discuss.elastic.co/t/help-with-custom-track-repositories/88110/4 "2017-07-17T07:11:03Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.