... | @@ -5,6 +5,10 @@ commits pushed to OTB repository. When commits are pushed, either on the main |
... | @@ -5,6 +5,10 @@ commits pushed to OTB repository. When commits are pushed, either on the main |
|
repository or on a fork, the platform triggers a pipeline with several jobs to
|
|
repository or on a fork, the platform triggers a pipeline with several jobs to
|
|
build and test OTB on different configurations.
|
|
build and test OTB on different configurations.
|
|
|
|
|
|
|
|
Here is a figure describing the overall architecture of the CI platform.
|
|
|
|
|
|
|
|
![archi_pic_2](uploads/0349836a74d8770a4b5fb69d40951cf0/archi_pic_2.png)
|
|
|
|
|
|
Depending on where your commit was pushed, different pipelines are created:
|
|
Depending on where your commit was pushed, different pipelines are created:
|
|
|
|
|
|
* push on a feature branch -> `wip` pipeline
|
|
* push on a feature branch -> `wip` pipeline
|
... | @@ -36,6 +40,11 @@ When a pipeline ends, there are two cases: |
... | @@ -36,6 +40,11 @@ When a pipeline ends, there are two cases: |
|
|
|
|
|
Failed jobs can be retried if you think the failure was not bound to your commit.
|
|
Failed jobs can be retried if you think the failure was not bound to your commit.
|
|
|
|
|
|
|
|
## Q: What can I find in the job artifacts?
|
|
|
|
|
|
|
|
Most of the jobs will produce artifacts. They are often log files, but some of them have more value for the developer:
|
|
|
|
|
|
|
|
|
|
## Q: Why some features are disabled when I push from my OTB fork?
|
|
## Q: Why some features are disabled when I push from my OTB fork?
|
|
|
|
|
|
First, you need an access to the Runners from main repository. You
|
|
First, you need an access to the Runners from main repository. You
|
... | | ... | |