delta/gitlab/gitlab-ce.git/lib/ci, branch 3870-commit-sorting-issue

Fix some typos

2016-04-22T20:08:38+00:00

Modify code formatting

2016-04-22T20:08:37+00:00

Simplify the GitlabCiYamlProcessor#initial_parsing method

2016-04-22T20:08:36+00:00

Add posibility to define a hidden job without 'script' in .gitlab-ci.yml

2016-04-22T20:08:34+00:00

Merge branch 'ci-commit-as-pipeline' into 'master'

2016-04-21T08:10:37+00:00


Ci::Commit becomes a Pipeline object

1. Ci::Commit receives context: ref, :tag.
1. One Ci::Commit describes a one Pipeline
1. Pipeline is created from `.gitlab-ci.yml`
1. Pipeline is a ordered group of builds
1. We test MR against Pipeline
1. Pipelines have a separate view (https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3703)
1. Pipeline can be triggered from UI (https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3703)
1. Later we change `Trigger -> TriggerRequest -> Build` to `Trigger -> Pipeline` (future)
1. We add a Pipeline Hook that will be triggered on Pipeline status change  (future)
1. We extend notifications to use `Pipeline Hook` to send summary on pipeline changes (future)

After merging that I'll prepare a separate MR that will unify naming, database columns, table names:
```
Ci::Commit -> Pipeline
Ci::Build -> Build
CommitStatus -> Job
GenericCommitStatus -> ExternalJob

ci_commits -> pipelines
ci_builds -> jobs
```

This MR implements first 5 points.

This is made to solve this issue https://gitlab.com/gitlab-org/gitlab-ce/issues/14149.

See merge request !3653

Fix Build#append_trace method usage when trace file doesn't exists yet

2016-04-20T09:54:06+00:00

Fix some typos in documentation

2016-04-20T09:54:06+00:00

[ci skip]

Add documentation of incremental trace update API

2016-04-20T09:54:05+00:00

[ci skip]

Make sure that appending is done on a valid length

2016-04-20T09:53:44+00:00

Add range checking

2016-04-20T09:53:43+00:00