| <!-- |
| Licensed to the Apache Software Foundation (ASF) under one or more |
| contributor license agreements. See the NOTICE file distributed with |
| this work for additional information regarding copyright ownership. |
| The ASF licenses this file to You under the Apache License, Version 2.0 |
| (the "License"); you may not use this file except in compliance with |
| the License. You may obtain a copy of the License at |
| |
| http://www.apache.org/licenses/LICENSE-2.0 |
| |
| Unless required by applicable law or agreed to in writing, software |
| distributed under the License is distributed on an "AS IS" BASIS, |
| WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. |
| See the License for the specific language governing permissions and |
| limitations under the License. |
| --> |
| # Concepts |
| |
| ## Pipeline |
| |
| A `pipeline` is the historical execution for a specific commit, each time you push a new commit to trigger an execution produces a new `pipeline` accordingly. |
| |
| ## Workflow |
| |
| A `pipeline` could have multiple `workflows`, A `workflow` orchestrates a set of `jobs`, it is a historical execution record. |
| |
| ## Job |
| |
| A `workflow` could have multiple `jobs`, A `job` could have multiple `steps`, and it is a historical execution record as well. |
| |
| ## Step |
| |
| Not important at the moment |
| |
| |
| # Domain Layer Conversion |
| |
| Based on the above concept, we need to convert the `workflow` and `job` to the Domain Layer as `cicd_pipeline` and `cicd_task`. |
| As for the CircleCI `pipeline`, it should be mapped to `cicd_pipeline_commit` because it contains the `commit sha`. |
| |
| It may look weird at first glance, but it is correct since Domain Layer presumes a Pipeline could have multiple repos while CircleCI has only one repo. |
