civilinfrastructureplatform:ciptesting:centalisedtesting
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
civilinfrastructureplatform:ciptesting:centalisedtesting [2020/03/03 14:52] patersonc [Target Control] Added the new LAVA workers |
civilinfrastructureplatform:ciptesting:centalisedtesting [2021/10/14 09:54] patersonc [CIP Centralised Testing] |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| The second goal for CIP testing was to centralise testing so that developers can run tests without having local access to a platform. This is becoming more and more useful for CIP as the list of [[civilinfrastructureplatform:ciptesting:cipreferencehardware|reference platforms]] grows. It also means that tests can be triggered and run automatically 24/7. | The second goal for CIP testing was to centralise testing so that developers can run tests without having local access to a platform. This is becoming more and more useful for CIP as the list of [[civilinfrastructureplatform:ciptesting:cipreferencehardware|reference platforms]] grows. It also means that tests can be triggered and run automatically 24/7. | ||
| - | The third goal for CIP testing is to set up Continuous Integration (CI) testing to automatically test CIP software on CIP hardware. See the [[civilinfrastructureplatform:ciptesting:centalisedtesting:cioverview|Continuous Integration testing overview]] page for more details. | + | The third goal for CIP testing was to set up Continuous Integration (CI) testing to automatically test CIP software on CIP hardware. See the [[civilinfrastructureplatform:ciptesting:centalisedtesting:cioverview|Continuous Integration testing overview]] page for more details. |
| + | |||
| + | The fourth goal for CIP testing is to integrate with the [[https://kernelci.org/|KernelCI project]]. This work is underway and the latest results can be viewed at [[https://kernelci.ciplatform.org/|kernelci.ciplatform.org]]. | ||
| ===== CIP Testing Architecture ===== | ===== CIP Testing Architecture ===== | ||
| The block diagram below provides an overview of CIP's centralised test infrastructure. | The block diagram below provides an overview of CIP's centralised test infrastructure. | ||
| Line 58: | Line 60: | ||
| KernelCI is a widely used project that aims to unify all upstream Linux kernel testing efforts in order to provide a single place where to store, view, compare and track these results. | KernelCI is a widely used project that aims to unify all upstream Linux kernel testing efforts in order to provide a single place where to store, view, compare and track these results. | ||
| - | At the moment CIP has their own instance of the [[https://kernelci.ciplatform.org/|KernelCI website]] where test results can be tracked. | + | CIP plans to submit our test results to kernelci.org so that they can be viewed by all. |
| == Mailing list == | == Mailing list == | ||
civilinfrastructureplatform/ciptesting/centalisedtesting.txt · Last modified: 2023/12/19 08:55 by swvanbuuren
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
