@@ -41,7 +41,7 @@ As a result you won't be able to run any pipeline as long as don't have any trac
Go in your local copy of the [tools/tracking](https://gitlab.com/to-be-continuous/tools/tracking) project, and manually click
the last `docker-publish` job that should be pending (if it's not the case, manually start a fresh new pipeline, then click the `docker-publish` job when it's pending). It may happen that the publish job fails the first time: simply retry it.
We'll see later [how to configure the tracking project](../advanced/#setup-tracking) to collect statistics about template jobs execution.
We'll see later [how to configure the tracking project](advanced.md#setup-tracking) to collect statistics about template jobs execution.
For now it is unconfigured, and will not track anything.
## Sync. your local copy of tbc
@@ -64,7 +64,7 @@ All other required variables shall be retrieved from [GitLab CI predefined varia
If you need to modify template code, you'll have 2 options depending on your case:
* if it's a general enhancement/fix: make a contribution to the Open Source [to be continuous project](https://gitlab.com/to-be-continuous/) and get the change through the synchronization task,
* if it's a change specific to your company: see [advanced usage](../advanced.md)
* if it's a change specific to your company: see [advanced usage](advanced.md)
By the way, you can manually trigger a pipeline in your [tools/gitlab-sync](https://gitlab.com/to-be-continuous/tools/gitlab-sync) project
anytime to synchronize your _to be continuous_ copy.