Skip to content
Snippets Groups Projects
Commit bc9dfd9b authored by Alberto Pianon's avatar Alberto Pianon
Browse files

specification on IP compliance pipeline migration

parent 19c20f51
No related branches found
No related tags found
1 merge request!22specification on IP compliance pipeline migration
......@@ -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 - that can be substantially the same as the one needed for Oniro-core and Oniro-blueprints; 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
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment