Removal of Firmware CI resources

[coderbyheart]

Continuous integration is the cornerstone of a success IoT product and that's why nRF Asset Tracker has implemented the necessary software and workflows to run end-to-end black box tests on real hardware using GitHub Actions self-hosted runners.

However, there is little evidence that this feature is used by our users (by the lack of {DevZone cases) and we are also not using this approach for other project that are built on top of nRF Asset Tracker. Quite frankly the effort to set up the pipeline and maintain it is too large for the kind of projects, nRF Asset Tracker is mostly used for.

Running unit tests can already get quite good confidence about the correctness of an application firmware, and since Nordic tests the SDK on real hardware already the ROI on setting up a hardware testing pipeline will not manifest for every project.

Therefore the features around this feature will no longer be available in the next release that is tagged alongside the nRF Connect SDK.

Archived projects

• https://github.com/NordicSemiconductor/cloud-aws-firmware-ci-runner-js/
• https://github.com/NordicSemiconductor/cloud-aws-firmware-ci-feature-runner-action/
• https://github.com/NordicSemiconductor/cloud-aws-firmware-ci-device-action/
• https://github.com/NordicSemiconductor/cloud-azure-firmware-ci-runner-js/
• https://github.com/NordicSemiconductor/cloud-azure-firmware-ci-device-action/
• https://github.com/NordicSemiconductor/cloud-azure-firmware-ci-feature-runner-action/

Renamed projects

• cloud-firmware-ci-device-helpers-js -> https://github.com/NordicSemiconductor/cloud-device-helpers-js (@nordicsemiconductor/firmware-ci-device-helpers -> @nordicsemiconductor/device-helpers)