d240666800
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 |
||
|---|---|---|
| .. | ||
| badges | ||
| builds | ||
| commits | ||
| issues | ||
| merge_requests | ||
| source | ||
| active_tab.rb | ||
| archived.rb | ||
| create.rb | ||
| deploy_keys.rb | ||
| fork.rb | ||
| forked_merge_requests.rb | ||
| graph.rb | ||
| hooks.rb | ||
| labels.rb | ||
| merge_requests.rb | ||
| network_graph.rb | ||
| project.rb | ||
| project_find_file.rb | ||
| project_group_links.rb | ||
| project_milestone.rb | ||
| project_shortcuts.rb | ||
| redirects.rb | ||
| services.rb | ||
| snippets.rb | ||
| star.rb | ||
| team_management.rb | ||
| wiki.rb | ||