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 |
||
---|---|---|
.. | ||
application_helper_spec.rb | ||
auth_helper_spec.rb | ||
blob_helper_spec.rb | ||
broadcast_messages_helper_spec.rb | ||
ci_status_helper_spec.rb | ||
commits_helper_spec.rb | ||
diff_helper_spec.rb | ||
emails_helper_spec.rb | ||
events_helper_spec.rb | ||
form_helper_spec.rb | ||
gitlab_markdown_helper_spec.rb | ||
graph_helper_spec.rb | ||
groups_helper_spec.rb | ||
icons_helper_spec.rb | ||
import_helper_spec.rb | ||
issues_helper_spec.rb | ||
labels_helper_spec.rb | ||
merge_requests_helper_spec.rb | ||
nav_helper_spec.rb | ||
notifications_helper_spec.rb | ||
page_layout_helper_spec.rb | ||
preferences_helper_spec.rb | ||
projects_helper_spec.rb | ||
runners_helper_spec.rb | ||
search_helper_spec.rb | ||
submodule_helper_spec.rb | ||
tab_helper_spec.rb | ||
time_helper_spec.rb | ||
tree_helper_spec.rb | ||
visibility_level_helper_spec.rb |