Skip to content
Snippets Groups Projects

Compare revisions

Changes are shown as if the source revision was being merged into the target revision. Learn more about comparing revisions.

Source

Select target project
No results found

Target

Select target project
  • eclipse-wg/oniro-wg/products-services-oniro-wg/it-services-oniro-wg/coordination-it-services-oniro-wg
  • heurtemattes/coordination-it-services-oniro-wg
2 results
Show changes
Commits on Source (3)
......@@ -43,8 +43,9 @@ In the current infrastructure Oniro projects provide and publish docker images i
Pipeline migration will be focus on the following oniro projects:
* Oniro-core
* Oniro-blueprints
* Oniro-compliancetoolchain (limited to standard CI pipelines)
Oniro-compliance-toolchain will be migrated/adapted separately given its special nature. Please check the corresponding section on this document.
Oniro-compliancetoolchain uses two completely different kinds of CI pipelines: on the one hand, there are some standard pipelines for python testing (pytype, python unittests), REUSE lint checks, and creation and publication of docker images, which require just a standard infrastructure to execute (a standard gitlab runner and a docker registry) that can be substantially the same as the one needed for Oniro-core and Oniro-blueprints (such pipelines are defined [here](https://gitlab.eclipse.org/eclipse/oniro-compliancetoolchain/toolchain/aliens4friends/-/blob/master/.gitlab-ci.yml)); on the other hand, there are custom CI pipelines, which do *not* run on the project's code repositories but on mirrors of the project repositories to be scanned (i.e. Oniro-core and possibly others) and which require a custom setup and a dedicated infrastructure. Only the first type may be migrated together with the pipelines of the other projects, while the second one will be migrated/adapted separately given its special nature. Please check the corresponding section on this document.
#### 2.1.2 Chat
......