| Summary: | Create autobuilder-controller container | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] CROPS | Reporter: | Tim Orling <tim.orling> |
| Component: | crops-default | Assignee: | Unassigned <unassigned> |
| Status: | NEW --- | QA Contact: | Toaster default assignee <toaster> |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | konrad.scherer, randy.macleod, tvgamblin |
| Version: | 3.1 | ||
| Target Milestone: | Future | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Tim Orling
2019-11-22 21:05:41 UTC
Very raw command line (ignoring yocto-autobuilder-helper for now): $ docker network create autobuilder $ docker run -it -e BUILDBOT_CONFIG_URL=http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder2/snapshot/yocto-autobuilder2-master.tar.gz -e BUILDBOT_CONFIG_DIR=yoctoabb -p 8010:8010 -p 9989:9989 --network autobuilder --name autobuilder-controller buildbot/buildbot-master:v2.7.0 I'll definitely help out with this - I had actually given myself the task of containerizing the autobuilder on our internal tracker last week! I think we will also need containers for the janitor, and also a hash equivalency server, correct? The latter should be pretty simple. Nice idea, but not something I have time to work on. Bulk move from 4.99 or 0.00 to 5.99 Ideas here are probably still valid for future design considerations. Moving to future. |