Improved email templates

Fixes https://dev.gitlab.org/gitlab/gitlab-ci/issues/215

See merge request !95

Add user permissions matrix

https://dev.gitlab.org/gitlab/gitlab-ci/issues/127

# Users Permissions

GitLab CI relies on user's role on the GitLab. There are three permissions levels on GitLab CI: admin, master, developer, other.

Admin user can perform any actions on GitLab CI in scope of instance and project. Also user with admin permission can use admin interface.

| Action                                | Guest, Reporter | Developer   | Master   | Admin  |
|---------------------------------------|-----------------|-------------|----------|--------|
| See commits and builds                | ✓               | ✓           | ✓        | ✓      |
| Retry or cancel build                 |                 | ✓           | ✓        | ✓      |
| Remove project                        |                 |             | ✓        | ✓      |
| Create project                        |                 |             | ✓        | ✓      |
| Change project configuration          |                 |             | ✓        | ✓      |
| Add specific runners                  |                 |             | ✓        | ✓      |
| Add shared runners                    |                 |             |          | ✓      |
| See events in the system              |                 |             |          | ✓      |
| Admin interface                       |                 |             |          | ✓      |

See merge request !93

Remove redundant header

https://dev.gitlab.org/gitlab/gitlab-ci/issues/193

See merge request !94

Update the build script example used by GitLab B.V. to support both docker and shell executors.

Updated build examples for GitLab CE to be able to used with either Docker or regular shell executors.

See merge request !92

Remove project IDs from dashboard

https://dev.gitlab.org/gitlab/gitlab-ci/issues/225

See merge request !91

Clean up project advanced settings. Migrate from gitlab_url to path

https://dev.gitlab.org/gitlab/gitlab-ci/issues/218

See merge request !90

Update guide from 7.9 -> 7.10

See merge request !89

Add HipChat Notification Service

My company is looking for a secure, private, stable and hopefully less-expensive alternative to our existing GitHub & Jenkins setup, and is currently focused on GitLab and GitLab CI after trying a number of other solutions. The biggest hurdle is integrations.

I saw that GitLab CI was lacking a service to notify HipChat of builds, and in my search to see if there was a workaround I saw [someone ask about it](http://feedback.gitlab.com/forums/176466-general/suggestions/5350117-gitlab-ci-should-push-notifications-to-configured), and figured it just hadn't been done yet. So, I did it.

* Move existing Slack service spec into a subdir, mirroring /app
* Wire up HipChat service to the project and services controller.
* Split the message building into own class.
* 'namespace' room and token variables.
* Enforce v2 client (bug in HipChat gem v1.5.0. fixed in 1.5.1). Note
  that I'm using the same version string as GitLab-CE, for shared
  installations. This does prevent 'old' room tokens from being reused.
  'v1' is more compatible, but there is rumblings about finally deprecating
  it and moving to v2 only on their GitHub issue tracker for this gem.
* Defer execution to a notifier worker, like the Slack service.
* Ensure passing specs (basically a Slack service spec copy, fwiw)
* Added change to the CHANGELOG

I'm not sure exactly how your feedback's "Accepting Merge Requests" tag is supposed to work, but I'm happy to learn and change my contribution procedure if anything is wrong here. Thanks!

![Screen_Shot_2015-04-26_at_8.48.19_AM](https://gitlab.com/uxp/gitlab-ci/uploads/296e9d86e369dd33ba99e44acbc8ea78/Screen_Shot_2015-04-26_at_8.48.19_AM.png)

See merge request !83

adding specs for HipChatMessage exposed some issues with the way I was
building the matrix-commit style notification message, so it ended up being
quite a bit more changes than I expected.

The save call from the service configure form submits an empty string as
the server URL if left blank, which I've indicated to do in order to use
the default server, but Hash#merge will happily overwrite a full string with
a blank string if asked, so we need to break that out, along with the worker
options which get mutated into string hash keys, of which the HipChat client
seems to not understand. Additionally, add another spec to make sure we call
the Sidekiq worker with expected arguments.

    * Move existing Slack service spec into a subdir, mirroring /app
    * Wire up HipChat service to the project and services controller.
    * Split the message building into own class.
    * 'namespace' room and token variables.
    * Enforce v2 client (bug in HipChat gem v1.5.0. fixed in 1.5.1). Note
      that I'm using the same version string as GitLab-CE, for shared
      installations.
    * Defer execution to a notifier worker, like the Slack service.
    * Ensure passing specs (basically a Slack service spec copy, fwiw)
    * Added change to the CHANGELOG

Fix 'ci skip' tag

https://dev.gitlab.org/gitlab/gitlab-ci/issues/206

See merge request !88

API refactoring && better test coverage

See merge request !87

Make Network class to follow HTTP RFC

https://gitlab.com/gitlab-org/gitlab-ci/issues/144

See merge request !86

Fix migration 7.8 and older to 7.10

https://github.com/gitlabhq/gitlab-ci/issues/586

See merge request !85

Make migration reversible

See merge request !84

Resolve situation with concurent runners registration

https://dev.gitlab.org/gitlab/gitlab-ci/issues/209

https://github.com/gitlabhq/gitlab-ci/issues/458

See merge request !82

Pending and Running tabs on admin builds page

https://dev.gitlab.org/gitlab/gitlab-ci/issues/212

See merge request !81

grammar fix to readme

See merge request !80

Refactoring network related code

https://dev.gitlab.org/gitlab/gitlab-ci/issues/139

See merge request !74