Setup Automation for testing all old linaro releases
Setup automation to build all major board variant image files for all old linaro releases in jenkins continuously with lmc.
Establish process: Integrate checking that all builds go green for a commit we plan to release and document that as part of the release announce.
Bug triggering this: https:/
Blueprint information
- Status:
- Complete
- Approver:
- Fathi Boudra
- Priority:
- High
- Drafter:
- Deepti B. Kalakeri
- Direction:
- Approved
- Assignee:
- James Tunnicliffe
- Definition:
- Approved
- Series goal:
- Accepted for trunk
- Implementation:
-
Implemented
- Milestone target:
-
2012.10
- Started by
- David Zinman
- Completed by
- Данило Шеган
Related branches
Related bugs
Sprints
Whiteboard
Meta:
Roadmap id: VIRT_PLAT_
Headline: linaro-image-tools is not continuously validating that all releases still work and the release process includes having all releases work a requirement.
Acceptance: jenkins job testing all old releass on all main boards are running; release process includes taking the jenkins job input as validation data.
[dooferlad 2012-10-08] Plan is to fix up the Linaro Fetch Image database so we can use that and the fetch image tools to download and build images. This should only involve updating the fetch image indexer to match the latest layout of snapshots and releases.
[deepti 2012-10-16] Attaching the build split up diagram that is deployed on ci*
https:/
[deepti 2012-10-18] Link to the wiki detailing all the information related to the Linaro Image Tools Regression setup and other details is present @ https:/
[danilo 2012-10-23] This has been completed according to acceptance criteria - one thing we might want to ensure happens is that all new Linaro releases get appropriate jobs created.
Work Items
Work items for 2012.10:
[dooferlad] Fix up fetch image indexer: DONE
[dooferlad] Make sure fetch image CLI works with new builds: DONE
[deepti] Get list of of released builds which needs to be validated to work with latest lit tools: DONE
[dooferlad] Discuss the set of release builds and board types for which we need to setup jobs : DONE
[deepti] : Setup job for verifying ubuntu build works with latest l-m-c for beagle/
[deepti] : Setup job for verifying ubuntu build works with latest l-m-c for beagle/
[deepti] : Setup job for verifying ubuntu build works with latest l-m-c for beagle/
[deepti] : Setup job for verifying ubuntu build works with latest l-m-c for beagle/
[deepti] : Setup job for verifying android build works with latest l-a-m-c for beagle/
[dooferlad] : Ensure all the releases are tested before rolling out new l-i-t release for nano: DONE
[deepti] : Ensure all the releases are tested before rolling out new l-i-t release for nano and android images: DONE
