Contents

## Project Sets

You need to define a set of projects so omnitest can run tasks or tests across them. This is defined in the `omnitest.yaml` file (or a file passed with the `-f` or `--file` option to commands).

The omnitest project set defines:
- The names of the projects
- The location where projects are stored locally
- (Optionally) The version control information for the project

### Simple Project Set

A simple project set without version control information looks like this:

<%= file_snippet 'samples/omnitest_simple.yaml' %>

You can use this setup if you already have a copy of the projects or if some other tools is managing the version control. However if you include version control information in the project set than omnitest can automatically fetch, update and check the status of each project.

## Getting the projects

Omnitest needs to have a local copy of the project before it can run any tasks or tests. If you have included version control information in the omnitest file then you can use the `omnitest clone` command to fetch the projects.

Here is an example project set that defines version control information for git repos:

<%= file_snippet 'samples/omnitest.yaml' %>

Now, you can use commands like `omnitest clone` to fetch the projects. See `omnitest help` for other available version control commands.

```
$ bundle exec omnitest clone
<%= scenario_output_snippet 'omnitest', 'clone', include_command: false, format: :raw %>
```

Version data entries

2 entries across 2 versions & 1 rubygems

Version	Path
omnitest-0.2.2	doc-src/project_sets.md.tt
omnitest-0.2.1	doc-src/project_sets.md.tt