| Summary: | Toaster must be able to create a build environment and launch the Bitbake server (remote use case) | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Toaster | Reporter: | Belen Barros Pena <belen.barros.pena> |
| Component: | toaster | Assignee: | Alexandru Damian <alexandru.damian> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | alexandru.damian, belen.barros.pena, bluelightning, cristiana.voicu, jessica.zhang, Yuan.Sun2 |
| Version: | unspecified | ||
| Target Milestone: | 1.7 M3 | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Belen Barros Pena
2014-04-25 10:45:47 UTC
(In reply to comment #0) > As a user, I want a remote instance of Toaster to transparently handle > creation of a build environment and starting of Bitbake server without any > direct interaction from me. Bitbake servers and the instance of Toaster are in different hosts, right? For example, user: hostA webserver: hostB bitbake server: hostC Users can login the web server of hostB. The web server of hostB can trigger a project build in hostC. Is it right? This scenario is correct. merged in master |