ha-operating-system/.gitignore

# OS generated files
.DS_Store

# Build output dirs
/release
output*/

# Certificates
*.pem

# vscode generated files
.vscode*
Add comments, ignore vscode* (#2152) 2022-09-24 08:25:44 +02:00			`# OS generated files`
add .DS_Store to .gitignore (#934) 2020-10-27 09:26:03 +01:00			`.DS_Store`
Add comments, ignore vscode* (#2152) 2022-09-24 08:25:44 +02:00
			`# Build output dirs`
Create OTA updater (#34) * Create OTA updater * Create .gitignore * Update build-all.sh * Update hdd-image.sh * Update ota.sh * Update ota.sh * Update ota.sh * Update ota.sh * Update post-image.sh * Create name.sh * Update name.sh * Update post-build.sh * Update name.sh * Update post-image.sh * Update ota.sh * Update hdd-image.sh * Update post-image.sh * Update name.sh * Update ota.sh * Update post-image.sh * Update hdd-image.sh * Update hdd-image.sh * Update hdd-image.sh * Update post-image.sh * Update post-image.sh * Update hdd-image.sh * Update hdd-image.sh * Update post-image.sh * Update post-image.sh * Update post-image.sh * Update info * Update info * Update info * Update info * Update info * Update info * Rename buildroot-external/board/raspberrypi/uboot-boot64.sh to buildroot-external/board/raspberrypi/rpi3-64/uboot-boot.sh * Update rpi3_64_defconfig * Update hdd-image.sh * Update ota.sh * Update post-image.sh * Update post-image.sh * Fix building Signed-off-by: Pascal Vizeli <pvizeli@syshack.ch> * Fix building v2 Signed-off-by: Pascal Vizeli <pvizeli@syshack.ch> 2018-06-24 00:11:54 +02:00			`/release`
Ignore build output directory (#1453) Avoid Docker sending the complete build output directory when trying to build the builder image. 2021-07-09 16:16:34 +02:00			`output*/`
Add comments, ignore vscode* (#2152) 2022-09-24 08:25:44 +02:00
			`# Certificates`
			`*.pem`

			`# vscode generated files`
Create foundation for Labgrid-based OS tests (#2812) * Create foundation for Labgrid-based OS tests Add foundation for Labgrid-based tests of OS builds. Currently uses just the QEMU driver, which starts a virtual machine with pristine OS, and generates few log reports which are saved as build artifacts. Workflow is currently triggered either manually by specifying an OS version, or by OS build job, which now saves an artifact of the OVA image. This allows for some modularity. If we eventually add the possibility to run builds on PRs, we could also add the workflow_call trigger and turn the workflow into a reusable one. TBD (in future PRs): some meaningful tests and possibility to test on real hardware (either local or distributed). * Apply suggestions from @agners Co-authored-by: Stefan Agner <stefan@agner.ch> * Wrap test command in a script, create venv for local tests * Make shellcheck happy --------- Co-authored-by: Stefan Agner <stefan@agner.ch> 2023-10-17 18:23:29 +02:00			`.vscode*`